Good content cannot rank if the site gets in its way.
Technical SEO ensures search engines can crawl, render, index and understand every page. Haryes fixes indexation waste, implements a connected schema graph resolving to one Organization entity, and holds pages to the Core Web Vitals thresholds.
Most technical SEO problems are invisible from the front end.
The site looks fine. It loads, the pages are there, the content reads well. Meanwhile Google is spending its crawl on filter URLs, indexing two versions of every page and rendering a template it cannot resolve to any clear business.
These are the ones we find most often on Kenyan sites.
- Hundreds of near-identical URLs from filters, sort orders and session parameters.
- The same page reachable at four addresses, with no canonical telling Google which counts.
- Content that only appears after JavaScript runs, on a page that is crawled before it does.
- Schema fragments on separate pages that never connect to one organisation.
- A mobile page weight that no Kenyan data connection can load quickly.
How a technical engagement runs
Diagnose first, fix in order of what the traffic is worth.
Crawl the site as a machine sees it
A full crawl plus log and Search Console data, so we work from what is actually indexed rather than what should be.
The real index, not the sitemap.
Separate waste from loss
Indexation waste costs crawl budget. Blocked or broken pages cost traffic directly. They are not the same emergency.
A list ordered by what it is costing you.
Fix structure and canonicals
One address per page, parameters controlled, redirects collapsed to a single hop, pagination handled deliberately.
A site that resolves cleanly.
Rebuild the schema graph
Organization, WebSite, Service, LocalBusiness and Article nodes that reference each other and resolve to one entity rather than sitting in isolation.
A description machines can follow.
Hold the performance budget
Core Web Vitals measured on a mid-tier Android over a Kenyan mobile connection, not on a laptop on fibre.
Numbers from the conditions your users have.
The thresholds we work to
Measured in the field, on the hardware and connections your visitors actually use.
- Largest Contentful Paint
- <2s
The main content is on screen in under two seconds.
- Page weight
- <800KB
Everything the page downloads, images included.
- JavaScript
- <150KB
Script shipped to the browser, per page.
The performance budget on every Haryes build and technical engagement
Crawlable
Every page worth having is reachable in a few clicks and returns the status code it should.
No orphans, no dead ends.
Indexable on purpose
Pages that should be in the index are, and the ones that should not are explicitly excluded.
The index matches the intent.
Renderable
The content a search engine needs is present without waiting on client-side JavaScript.
Nothing important hides behind a script.
Understandable
A connected schema graph resolving to one Organization, so engines know which business this is.
Legible to AI answer engines too.
What you get
Technical work runs either as a fixed audit or inside a monthly SEO plan.
A prioritised findings document
Ordered by impact, not by severity label.
- What it costs you, in traffic terms
- What it takes to fix
- Who has to do it
Implementation
We fix it, or your developers do.
- Changes made directly where we hold access
- Written specifications where another team implements
- Verification after deployment
Schema graph
Connected, not scattered.
- One Organization entity everything resolves to
- Service, Article and LocalBusiness nodes linked
- Validated against the live pages
Monitoring
So it does not drift back.
- Index coverage watched monthly
- Core Web Vitals tracked in the field
- Regressions caught after deployments
Questions clients ask before they commit
What does a technical SEO audit cost?
A full audit is KES 85,000, delivered as a prioritised document with implementation specifications. Ongoing technical work is included in the monthly SEO plans.
Can our own developers do the fixes?
Yes, and often that is faster. We write the specifications precisely enough that a developer who has never met us can implement them, then we verify after deployment.
Is technical SEO a one-off?
The big clean-up is. Keeping it clean is not: every redesign, migration and new template is a chance to reintroduce the same problems, which is why monitoring is part of the plans.
Do Core Web Vitals really affect rankings?
They are a small factor in ranking and a large factor in whether anyone waits for your page on a Kenyan mobile connection. We treat the second as the reason and the first as a bonus.
Audit, or ongoing?
Traffic fell, pages vanished from the index, or a migration went badly.
A fixed-price audit tells you what happened and what to do, in order.
See the auditThe site is fine and you want it to stay that way.
Technical work runs monthly alongside content and local SEO.
See SEO pricingTechnical SEO is mostly removing obstacles. The content was often fine all along.
