On this page
If Search Console says Google found your URLs but they never appear for “plumber Westlands” or “clinic Nairobi,” you are dealing with indexation problems Kenya businesses hit every week — especially after redesigns, plugin updates, or staging copies pushed live. Indexation is not the same as ranking: first Google must keep the page in the index; only then can content and links help it climb.
This guide explains what indexation means, how to diagnose coverage states, the most common blockers on Kenyan SME sites, and a recovery checklist you can run this week. For the wider technical stack, see technical SEO Kenya. For crawl file basics, read robots.txt and sitemap guide for Kenya websites.
Quick answer: what “indexation problems” means
Crawl = Googlebot can fetch the URL.
Index = Google stores the URL as a candidate for search results.
Rank = Google chooses to show that URL for a query.
Most Kenyan owners mix these up. A page that loads fine in Chrome can still be:
- Blocked by
noindex - Treated as a duplicate of another URL
- Soft-404’d by a thin template
- Discovered but not selected (“Crawled – currently not indexed”)
Start with a free website audit, then open Search Console Pages coverage before you rewrite content.
How to diagnose indexation in Google Search Console
- Indexing → Pages — note Excluded vs Indexed counts and the top reasons.
- URL Inspection on each money page (home, services, city pages).
- Check robots.txt and sitemap status under Indexing.
- Compare live HTML for
noindex, canonical tags, and unexpected redirects.
Useful companion reads: Google Search Console guide for Kenyan businesses and how to check if your website has SEO problems.
Coverage states that matter most
| GSC status | What it usually means | First fix |
|---|---|---|
| Indexed | In the index — good baseline | Improve content / links if rankings are weak |
| Discovered – currently not indexed | Known but not crawled yet | Sitemap, internal links, hosting stability |
| Crawled – currently not indexed | Fetched but not kept | Quality, duplicates, soft 404s |
| Excluded by ‘noindex’ | Explicit block | Remove noindex on production |
| Blocked by robots.txt | Crawl blocked | Fix Disallow rules |
| Soft 404 | Looks empty / error to Google | Real content + correct status codes |
| Duplicate / alternate | Canonical conflict | One clear canonical per page |
Common indexation problems on Kenyan websites
1. Staging noindex left on production
Agencies and freelancers often ship with meta name="robots" content="noindex" still on. The site looks perfect to humans and invisible to Google.
2. robots.txt Disallow from staging
Disallow: / on a live .co.ke domain is still common after a host migration. Googlebot will not crawl — recovery needs a correct allow list plus Search Console rechecks. See the robots.txt / sitemap guide.
3. Canonical tags pointing at the wrong URL
HTTP→HTTPS, www vs non-www, trailing slash, and parameter URLs fight each other. Google keeps one version; the others look “duplicate.”
4. Soft 404s and thin service templates
One generic “Our Services” template with the city name swapped often gets treated as low value — especially for multi-location Kenyan businesses.
5. Redirect chains after redesigns
Old blog and service URLs that hop 301→301→200 burn crawl budget and confuse which URL should be indexed. Flatten to a single hop.
6. Server errors and timeout crawls
Unstable shared hosting that returns intermittent 5xx during Googlebot visits leaves pages stuck in discovered/not indexed loops.
7. Orphan pages with no internal links
New landing pages that only exist in ads or WhatsApp links may be discovered slowly and deprioritised. Link them from the hub and related guides.
Kenya-specific recovery checklist
- Remove production
noindex/nofollowmistakes. - Fix
robots.txt— neverDisallow: /on live. - Confirm HTTPS + one preferred host in Search Console.
- Set one self-referencing or intentional canonical per money URL.
- Rebuild thin location/service pages with unique copy.
- Submit an accurate XML sitemap; remove dead URLs.
- Request indexing on the top 10 revenue URLs first.
- Add internal links from SEO services Kenya cluster pages, blogs, and the homepage where relevant.
- Re-crawl after hosting or CDN changes.
- Monitor Pages coverage weekly for two to four weeks.
If you need implementation help beyond DIY, compare packages on pricing or book SEO audit Kenya / technical SEO Kenya. Questions? Contact or WhatsApp.
Illustrative Example: redesign that deleted a third of the index
Illustrative Example (not a named client): a Nairobi service business redesigned on a new CMS. Impressions flatlined for eight weeks. Search Console showed many money URLs as Excluded / duplicate, and several still carried staging noindex.
Fixes in the first month: removed noindex, corrected canonicals, rebuilt the XML sitemap, flattened redirect chains, and requested indexing on priority service pages.
Outcome pattern: indexed URL count normalised and impressions began recovering within weeks — before any new blog content was published. Indexation had to be healthy before on-page or local SEO could work.
DIY vs hiring for indexation problems
| DIY is enough when… | Hire when… |
|---|---|
| You can read Search Console Pages | Hundreds of unclear exclusions |
| One site, few templates | Multi-location or ecommerce catalogue |
| Issue is an obvious noindex / robots block | Post-migration mess or soft 404 at scale |
| You only need a diagnosis | You need developers + SEO to ship fixes |
Run the free audit first. If coverage is chaotic, a scoped technical fix cycle usually beats guessing for months.
Related reading
Ready to get your Kenya business found on Google?
Start with a free website audit — PageSpeed, SEO gaps, and quick wins.