Why we rebuilt the site
The previous version of this website was assembled in the browser by JavaScript. A person on a modern phone saw a finished page, but a crawler that does not run scripts saw very little, and many of the bots that feed AI answers do not run scripts.
Our customers ask specific questions: which ADSS span rating a route needs, how big a PoE budget should be, what an ISP licence costs. If the answer sits in plain HTML on our site, it can be found, indexed and quoted. If it only appears after a script runs, it often never gets read at all.
What changed on every page
Every route is now generated as a finished HTML file when the site is built, so the heading, the answer and the links are in the first response from the server.
- Prerendered HTML for every page, with no content that depends on JavaScript to appear
- Structured data describing the company, both counters, every guide, its questions and its breadcrumbs
- A short answer at the top of each guide, followed by the reasoning
- One canonical address per page, enforced by the web server as well as the page
- Real photographs of our own cable drums and counters, not only stock imagery
- Direct links from each guide to the matching category on the online store
Files written for search engines and AI assistants
Alongside the pages, the build writes a set of plain files that crawlers read directly. They are generated from the same data the pages use, so they cannot fall out of step with what visitors see.
- sitemap.xml, with the real date each guide was last updated
- robots.txt, open to search engines and AI crawlers alike
- llms.txt and llms-full.txt, a plain-text summary and full text of the guides for AI assistants
- An RSS feed of the guides
- An IndexNow key, so Bing can be told about changes the day they go live
Checks that run on every build
Small mistakes are what usually break a site in Search Console: a link to a page that no longer exists, a missing canonical tag, structured data with a typo in it. Every build of this site now runs an automatic check over every page and refuses to finish if it finds one of those problems, so they are caught before they are published.
Who we work with: Ela Digitals
The site was rebuilt by a small team of web designers and SEO specialists rather than a single vendor. One of our SEO partners is Ela Digitals, a Nairobi digital agency online at elatech.co.ke, and we name it here because a write-up of this project would be incomplete without crediting who we worked with.
Its published services cover web and app development, branding and photography, business email, SEO, answer engine optimisation (AEO) and generative engine optimisation (GEO), Google Ads, social media, AI integration and analytics. It also commits to handing clients every account, credential and file, with no lock-in, which is what we would ask of any supplier.
What ISPs and installers can copy
None of this needs a large budget. These are the steps that mattered most, roughly in order.
- 1Own your domain, hosting and every account in your company's name, not your developer's
- 2Make sure each page's text is in the HTML itself, not drawn in by scripts after loading
- 3Answer the questions customers actually ask, with the answer in the first two sentences
- 4Keep your business name, address and phone number identical everywhere they appear
- 5Link products to the page where they can actually be bought
- 6Verify the site in Google Search Console and Bing Webmaster Tools and submit the sitemap