Technical SEO Audit Guide Kenya: What Actually Breaks Your Visibility

A car dealership in Industrial Area spent four months paying an agency KES 20,000 a month for "SEO," and the phone still was not ringing from Google. When someone finally pulled up Search Console, the reason was almost boring: the sitemap pointed to a staging subdomain nobody had switched off after the last redesign, and half the site's service pages had never been crawled at all. No algorithm mystery. No penalty. Just a technical mess nobody looked under the bonnet for.

This happens constantly. A business owner in Kilimani searches technical SEO audit guide Kenya after a marketing agency quotes them for content and ads, and nobody has explained that if Google cannot crawl and index the site correctly, none of that content will ever show up. This guide walks through what a technical SEO audit actually checks, how Kenyans search for and vet this kind of help, the technical failure modes that are specific to how Kenyan sites are hosted and built, and a rollout sequence you can run yourself before paying anyone.

Quick answer: what a technical SEO audit actually checks

A technical SEO audit is a structured review of whether Google can crawl your site, index the right pages, and understand what those pages are about — separate from your content or your backlinks. At minimum, it should check: robots.txt rules, XML sitemap accuracy, indexing status in Search Console, canonical tags, redirects, mobile usability, page speed, and structured data. If an "audit" skips Search Console entirely, it is a surface scan, not a technical audit — more on that under red flags below.

For the ongoing service version of this work, see technical SEO in Kenya. If you want a single, structured review rather than a monthly retainer, that is what an SEO audit is for. Pair this guide with the shorter technical SEO audit checklist for Kenya when you want a printable pass list.

The lead that never showed up: a scene most Kenyan businesses recognise

Picture a plumbing business in South B. The owner built a WordPress site two years ago, added a WhatsApp button, and pays for a Safaricom data bundle to check it from his phone most mornings. Business is steady from referrals and Google Maps, but organic search — someone typing "emergency plumber Nairobi" and finding the website itself, not the Maps pack — has never worked. He assumes the content just needs rewriting.

What he does not know is that his site's robots.txt file, left over from a plugin default, is quietly blocking /wp-content/uploads/, which means every image alt tag and every schema markup file referencing those images is invisible to Google. His sitemap has not been resubmitted since the redesign, so Search Console is still crawling old URLs that 404. None of this shows up by looking at the website in a browser. It only shows up when someone opens Search Console and reads the actual crawl and index reports.

This is the gap between a website that looks fine and a website that is technically sound. Kenyan SMEs lose leads to this gap constantly, because the symptoms — "we don't rank," "traffic is flat," "Google Ads costs more than it should" — look like content or marketing problems, when the root cause is structural.

How Kenyan buyers find and vet technical SEO audit help

Search behaviour for this topic in Kenya rarely goes straight to a purchase. It usually runs through several stops:

Google search → Maps pack check → website visit. Someone searches "SEO audit Kenya" or "technical SEO audit Kenya," glances at the top three organic results, then often cross-checks the business on Google Maps before trusting it — reviews, photos, whether the listing looks active. A provider with a thin or unclaimed Google Business Profile loses credibility here even if their website copy is strong.

WhatsApp, not contact forms, is the default enquiry channel. Kenyan business owners are used to clicking straight into WhatsApp from a Maps listing or a website button rather than filling in a long form and waiting for an email reply. If a provider's site funnels every enquiry into a form with no WhatsApp option, a chunk of serious buyers will simply leave. Use the on-page WhatsApp button, or head to contact, if you would rather talk through a specific problem before running anything yourself.

Mobile data cost shapes patience. Someone checking a provider's site on a Safaricom or Airtel bundle in traffic on Thika Road is not going to wait for a bloated homepage to load, and they definitely are not going to download a 40-page PDF "SEO report" template over mobile data. This matters twice: it is a reason technical SEO matters for your own site, and it is a filter buyers apply to anyone claiming to fix it for them — a provider whose own site is slow is a bad sign.

Price is compared in KES, not vaguely. Kenyan buyers expect a shilling figure, not "contact us for a custom quote" as the only option. Technical audit pricing locally tends to sit in bands rather than one flat number — a quick automated pass might cost nothing, a full manual technical review for a small service site typically runs somewhere in the low tens of thousands of shillings, and a large e-commerce or multi-location site costs more because there is simply more to crawl and more URL patterns to check. Retainers for ongoing technical + SEO work at KevCodePulse start from KES 15,000/month; a standalone audit is priced separately depending on site size. For exact current pricing, see pricing and what a technical SEO audit costs in Kenya.

What actually breaks visibility for Kenyan websites

This is the core of any real technical audit — the specific things that quietly stop Google from crawling, indexing, or trusting a page. Most guides on this stop at "check your sitemap." Here is the fuller list, including the checks that are consistently skipped.

Crawl access. Open yourdomain.co.ke/robots.txt directly in a browser. A stray Disallow: / — often left by a developer during a staging build and never removed — blocks the entire site from Google. This is more common than it should be with Kenyan sites handed over by freelancers who built on a staging subdomain first.

Indexing status, read properly in Search Console. This is the step almost every free tool and most "SEO checklist" articles skip, because it needs a connected GSC property, not a public scanner. Under Indexing → Pages, four statuses matter and each means something different:

• Indexed — the page is live in Google's index. Good.
• Crawled — currently not indexed — Google visited the page but chose not to index it, usually because the content is thin, duplicate, or the page was not considered useful enough. This is a content and structure problem, not a crawl problem.
• Discovered — currently not indexed — Google knows the URL exists (often from a sitemap or a link) but has not crawled it yet, frequently because of a crawl budget or server response issue. On smaller Kenyan sites this often means slow server response times are quietly capping how much Google is willing to crawl.
• Not found (404) — old URLs still submitted in a sitemap that no longer resolve, wasting crawl attention on dead pages.

Confusing these four is the single most common reason business owners misdiagnose "why we don't rank." A page stuck in "Discovered — currently not indexed" for months needs a different fix than one Google crawled and rejected as thin. For the deeper indexation walkthrough, see indexation problems Kenya.

Sitemap accuracy. The XML sitemap at /sitemap.xml should list only canonical, indexable URLs — not old redesign URLs, not admin pages, not every filtered product variation on an online shop. A sitemap padded with junk URLs signals a messy site to Google and dilutes crawl attention away from the pages that matter.

Canonical tags. Every page should point to one clear canonical version of itself. Kenyan sites running on shared hosting with both http:// and https://, or both www and non-www versions still technically reachable, often split ranking signals across duplicate versions of the same page without anyone noticing.

Noindex tags left on by accident. WordPress's "discourage search engines from indexing this site" setting, ticked during development and never unticked at launch, is a recurring, entirely avoidable cause of a Kenyan SME site being completely invisible to Google for months.

Soft 404s, thin pages, and duplicate content. Auto-generated location or service pages with near-identical text (a common shortcut when someone tries to rank for five Nairobi suburbs by copy-pasting one page five times) get treated by Google as duplicate or thin, and often quietly drop out of the index rather than ranking.

Redirects. Long redirect chains — URL A to B to C to D — waste crawl budget and slow page load. This is common after a site has been rebuilt two or three times over several years without anyone cleaning up the redirect map.

Mobile experience and speed on real Kenyan connections. Google indexes the mobile version of your site first. Test on an actual phone on mobile data — not just office WiFi on a laptop — because a page that loads acceptably on fibre in Westlands can be unusable on a 4G connection with a weaker signal upcountry. Heavy, uncompressed images are the most common Kenyan-hosting-specific speed killer, closely followed by server response time on budget shared hosting with no local or regional edge caching. See also page speed and SEO in Kenya.

Structured data. Schema markup (Organization, LocalBusiness, FAQPage, Article, depending on the page) helps Google understand what a page is, and it is frequently missing entirely on Kenyan SME sites, or copied wholesale from a theme template with the wrong business details still in it.

The Kenya-only technical layer

Beyond the standard technical SEO checklist, a handful of checks are specific to how Kenyan businesses actually operate online, and competitor guides on this topic tend to skip them entirely.

Phone number formatting and NAP consistency. Google Business Profile, your website footer, and any directory listings should all use the same phone format — consistently +254 or consistently 0 prefixed, not a mix. A business listed as +254712345678 on Maps and 0712 345 678 on the website looks like a minor inconsistency to a human, but it can weaken the trust signal search engines use to confirm a business is who it says it is.

Google Business Profile video verification. Since Google shifted many Kenyan GBP verifications to a video-recording step rather than a postcard, businesses that skipped this or let verification lapse after an address change often find their listing suppressed — which then affects how confidently Google associates the website with a real, verified local business. This is worth checking even during a purely "technical SEO" audit, because local trust signals and organic indexing are not as separate as people assume.

M-Pesa and checkout technical signals, for e-commerce. If a site takes payment via M-Pesa STK push or Paybill, the checkout flow needs to be crawlable and fast — a checkout page that times out on mobile data does not just lose a sale; a persistently slow, error-prone section of the site can drag down Google's overall quality assessment of the domain.

Local hosting latency. A site hosted on a US or EU server with no CDN adds real, measurable delay for a Kenyan visitor and a Kenyan crawl — Google's crawler experiences the same distance penalty a user does. A CDN with an African or at least a nearby edge node (Cloudflare's setup is the common, affordable option) closes most of that gap without needing to migrate hosting entirely.

Bilingual and Kiswahili search behaviour

This is a genuine blind spot in most technical SEO content aimed at Kenya — including every competitor page reviewed for this guide. Kenyan search behaviour is not purely English. Depending on the industry, meaningful volume comes through mixed-language queries: a Kiswahili verb or noun combined with an English service term, or a fully Kiswahili phrase for a local service.

Technically, this affects an audit in three ways. First, check whether your <html lang=""> attribute and any hreflang setup (if you run separate language content) are set correctly — a mismatched lang tag can confuse how Google associates content with a language and region. Second, check your site search and internal search logs, if you have them, for Kiswahili or Sheng terms customers are already typing — these are free keyword research that most audits never look at, because they are checking crawl data, not query data. Third, if your business genuinely serves Kiswahili-first customers, thin or absent Kiswahili content is a content gap a technical audit should flag even though it is not purely "technical" — an audit that only looks at code and ignores who is actually searching misses half the picture.

A practical audit rollout you can run this week

Once you understand what to look for, running a first-pass audit yourself takes a few hours, not a few weeks. This is not a numbered checklist to clone from elsewhere — it is the order that actually surfaces the highest-impact issues first, so you are not polishing a schema tag while a robots.txt block is hiding the whole site.

Start by confirming Google can find the site at all: check robots.txt for accidental blocks, confirm the sitemap exists and is submitted in Search Console, and scan for any leftover "discourage search engines" setting. This single pass catches the most catastrophic, easiest-to-miss errors — the ones that make everything downstream irrelevant until they are fixed.

Next, read the indexing report properly. Sort pages by status and pay specific attention to anything sitting in "Discovered — currently not indexed" for more than a few weeks, since that usually points to a crawl budget or server speed issue rather than a content one. Cross-reference against your actual page list — if your 40 service and location pages do not roughly match what Search Console has indexed, you have a structural gap worth investigating before writing another word of content.

Then check duplication and canonicals: search a distinctive sentence from your homepage in quotes to see whether it is appearing on both www and non-www, or http and https, versions of your domain. Fix at the server level with a single 301 rule rather than patching individual pages.

After that, test speed and mobile usability on an actual phone, on mobile data, not just a desktop tool — run the URL through PageSpeed Insights for the numbers, but also physically load it on a phone in a low-signal spot if you can, because that is closer to how a meaningful share of your customers experience it.

Finally, check structured data and metadata — confirm your title tags and meta descriptions are unique per page (not the theme default repeated everywhere), and that any schema markup on the page reflects your real business details, not placeholder text from a template.

Log everything you find in a simple spreadsheet with three columns: issue, likely impact, and effort to fix. Fix the site-wide blockers first — robots.txt, sitemap, noindex, canonical duplication — because those affect every page at once. Content-level issues like thin location pages come after the foundation is sound.

If this turns up more than you want to fix alone, or the Search Console data does not make sense once you are looking at it, that is the point where a second pair of eyes is worth it — either a one-off review through SEO audit, or a longer conversation about what a scoped fix would look like via contact. For service options, see choosing SEO audit services in Kenya.

Red flags: telling a real technical audit from a checklist PDF

A genuine technical SEO audit engages with your actual Search Console data — indexing status, query performance, coverage issues specific to your domain. If a provider quotes you a price before ever asking for GSC access, or without asking a single question about your site's history (redesigns, migrations, recent traffic changes), what you are likely buying is a generic tool export with your logo added, not an audit of your website.

Be cautious of a report that lists forty "issues" with no priority order. A long list without a clear critical-versus-cosmetic split is not more thorough — it is often a sign the person compiling it does not understand which findings actually matter, and it will send you chasing low-impact fixes while the real blocker sits untouched. A useful audit tells you what to fix first and why, not just what an automated scanner flagged.

Also be wary of guaranteed outcomes. Nobody, including us, can guarantee a specific Google ranking position — the algorithm and your competitors both move. What a credible technical audit can promise is a clear, prioritised account of what is currently blocking your site, and a realistic view of what fixing it should improve.

Related reading: local SEO audit checklist for Kenya · Google Search Console guide for Kenyan businesses · SEO services Kenya