Service 01
Technical SEO
Most South African sites do not have a content problem. They have a crawl budget quietly being spent on faceted URLs, a hydration path that hides half the copy from Googlebot, and a CDN that never learned to cache.
What we audit
We start in the server logs, not in a third-party crawler. Real Googlebot behaviour tells you which templates earn attention and which are being ignored, a distinction no simulated crawl can make.
- Log-file segmentation by template, status code and bot type
- Render-path diff: raw HTML against the rendered DOM
- Index bloat, parameter handling and canonical conflicts
- Core Web Vitals traced to the specific component causing them
- Internal link graph modelled as a directed graph, not a sitemap
What you receive
A prioritised engineering backlog written for developers, ticket-shaped, with reproduction steps, the expected delta and a way to verify the fix shipped correctly.
- Findings ranked by traffic-at-risk, not by severity colour
- Jira- or Linear-ready tickets with acceptance criteria
- A regression suite so fixes do not silently revert at the next deploy
Also part of the programme
What this connects to.
Next step
Start with technical seo.
The diagnostic covers this discipline in full and tells you where it sits in the priority order against everything else.