Technical SEO Consultant, Kenya

Where your site is hosted, and why Kenyan visitors notice

Many Kenyan business websites sit on servers in Europe or North America, often on low-cost shared plans chosen when the site was first built. Every request then makes a long round trip before the first byte arrives, and shared servers can slow down or fail when neighboring sites are busy. Search engines notice too: repeated server errors or timeouts lead crawlers to request fewer pages, and new content takes longer to be discovered.

I measure the hosting side directly:

• Server response times for visitors in Kenya, compared with tests from elsewhere
• Server error and timeout patterns in Search Console crawl statistics
• Whether pages are cached, or rebuilt from the database on every request
• Whether a CDN is in place, and whether it has edge locations in or near East Africa
• Uptime history, where the host or a monitoring tool records it

Moving hosts is not always the answer. Page caching and a well-configured CDN often fix most of the delay without a migration. Where a move is justified, local or regional data centers are worth comparing against international providers on reliability, support and backup, and Kenya's data protection law may shape where personal data from forms and accounts should live. Your legal advisor should confirm that part. I set out the options and trade-offs; the decision and contract stay with you.

Entry-level phones, data saver modes and heavy JavaScript

Page weight is only half the mobile problem. The other half is processing power. Many Kenyans browse on affordable Android phones with modest processors, and a page built with a visual page builder, several sliders, animation libraries and multiple tracking tags can keep that processor busy long after the data has arrived. The visitor taps a menu and nothing happens. That delay is what the responsiveness metric in Core Web Vitals captures.

I test key templates under throttled conditions that resemble an entry-level phone on a mobile network, then trace what blocks the main thread:

• Page-builder markup that nests elements many levels deep
• JavaScript bundles loaded on every page for features used on one
• Third-party chat, social and ad scripts running before the content
• Fonts and icons loaded from several sources

Some visitors also use browsers or data saver modes that compress pages or limit scripts. If your navigation, prices or contact buttons depend on JavaScript, those visitors may see a broken page, and some crawlers will see an empty one. Serving core content and links in the initial HTML protects both. The fixes are usually removal and deferral rather than a rebuild. The JavaScript SEO page explains the rendering side in more detail.

WordPress clean-up and sites that have been compromised

A WordPress site built quickly by a freelancer or agency and then left to run collects problems over time: two SEO plugins writing conflicting tags, tag and author archives indexed as thin pages, attachment pages for every image, and themes or plugins that have not been updated in a long time.

Outdated components are also a security risk, and compromised sites are a real search problem. Attackers inject pages selling pharmaceuticals, gambling or counterfeit goods under your domain, add hidden links or redirect mobile visitors to spam while showing the owner a normal site. Search engines may label the site, drop pages or show spam titles in results.

When I suspect a compromise, I look for evidence in several places:

• The security issues and manual actions reports in Search Console
• Search results for your domain that show unfamiliar titles or languages
• Server logs with requests for URLs you never created
• Sitemaps or pages added without anyone on your side knowing

Clean-up itself belongs to your developer and host: removing malicious code, updating everything, changing credentials and restoring from a clean backup if needed. I then make sure spam URLs return a gone status, sitemaps are correct and reconsideration or review requests are filed where appropriate. An update and backup routine afterwards stops the same thing happening again.

Catalogs, checkouts and structured data for Kenyan addresses

Kenyan distributors, retailers and manufacturers increasingly connect their online catalog to an ERP such as Odoo, ERPNext or Business Central. That brings consistent product data, and it also brings technical choices. Items deactivated in the ERP need a redirect or a proper not-found status rather than an empty page. Product markup should take shilling prices and stock status from the very field the visible page displays.

Checkout and payment flows, including M-Pesa steps, cart pages and order confirmations, should be kept out of the index and out of the sitemap. They also tend to load payment scripts that should run only on those pages, not across the whole site.

Local business markup needs particular care in Kenya, where addresses are often described by building, floor, road and nearby landmark rather than a street number. I recommend:

• A streetAddress that reads the way customers give directions, consistent with your Google Business Profile
• Geo coordinates that match the pin on the map, checked on the ground by your team
• One LocalBusiness block per branch page, with its own phone number and opening hours
• An Organization block with your registered name and profiles listed consistently

Markup that matches what customers see helps search engines and AI assistants describe your locations accurately. The model behind this is described under schema markup consulting, and catalog integration under ERP integration.

Regional hub sites, migrations and working with your developer

Nairobi is a base for many companies, NGOs and service firms working across East Africa, and their websites often grow country sections for Uganda, Tanzania, Rwanda and beyond. Technically, those sections tend to share templates and text, which leads to near-duplicate pages, canonicals that point every country to the Kenyan page and language versions that fall back to English silently. I check how each section is built and write rules so each version is distinct and correctly annotated. Which countries deserve a section, and in which language, is covered on my international SEO page for Kenya.

Domain moves are common too, for example consolidating a .co.ke site and a .com, or rebuilding a site on a new platform. Each needs a redirect map, staging checks and launch-day verification, set out on the SEO migration page.

Server logs are not always available on shared hosting, but CDN logs or a short export from the host usually are, and they show which URLs crawlers actually request.

Many Kenyan businesses rely on a freelance developer or a small agency. I work alongside them, remotely and in English, during hours that overlap comfortably with the Kenyan working day. Content and local search are on my Kenya SEO consultant page, and the Kenya hub lists my ERP and growth services. Get in touch to arrange an audit.