Technical SEO
Crawlability, indexation, sitemaps, canonical rules and site architecture, so the pages that matter can be reached and the ones that do not stop consuming crawl budget.
Service 04
Search foundations are the technical health that makes a site fit to be crawled, understood, cited and ranked. Everything upstream depends on it: a page nobody can fetch cannot be optimised, and a result nobody can measure cannot be improved.
Every other pillar depends on a site that machines can crawl, render and interpret, and that people can use without friction. Foundations are where visibility work either compounds or leaks.
Slow templates, unreliable measurement and unclear journeys quietly tax every visit the other pillars earn. This work removes the tax.
Visibility you cannot crawl, measure or convert is visibility wasted.
Crawlability, indexation, sitemaps, canonical rules and site architecture, so the pages that matter can be reached and the ones that do not stop consuming crawl budget.
Planning and executing redirect maps, canonical handling and post-launch validation for replatforms, redesigns and domain moves. Also repairing migrations that were done without them.
Implementing and validating Schema.org markup for organisations, products, articles, locations and FAQs, so search engines can show rich results and AI systems have unambiguous facts to work from.
Core Web Vitals diagnosis and clean, performant front-end code that makes a site quick, accessible and easy for both humans and machines to read.
Verifying that GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot and Google-Extended reach the site without being challenged by the CDN or firewall, and publishing an accurate llms.txt that points them at what matters.
Google Business Profile optimisation, NAP consistency and local schema for physical and service-area businesses, plus hreflang and market targeting where a site sells across languages or countries.
Search Console and GA4 configuration, conversion and event tracking, and plain-English reporting that shows which signals are working, which content is gaining traction, and where visibility is moving over time.
Designing site experiences that are intuitive, fast and structured to build confidence, then reducing the friction between arriving and getting in touch so the same traffic produces more enquiries.
How we work
This pillar covers the machine layer: whether a page can be reached, rendered, understood, measured and acted on. The work follows a crawler's route through the site, fixes what breaks along it, then proves the fix held.
We follow the route a machine takes: reach, render, index, understand, measure. That covers crawlability, sitemaps, canonicals, redirects, structured data, page speed and whether AI crawlers are being challenged before they ever see the content.
Findings are ordered by how much they limit the other pillars. A sitemap that will not fetch or a firewall blocking GPTBot outranks a slow image, because nothing downstream works until they are cleared.
Fixes are shipped, then checked against acceptance tests: pages fetch as expected, schema validates, Core Web Vitals move in field data, and analytics record the actions that matter. Verification is evidence, not an assurance that the work was done.
In practice
The audit follows the same route a crawler does: reach the page, render it, understand it, then prove what happened next. Anything that breaks along that path caps everything upstream.
One broken stage caps everything upstream of it.
What you receive
The output is a working foundation with clear ownership, not a long technical document left between teams.
Priorities across crawlability, indexation, sitemaps, canonical rules and site architecture, with the crawl waste identified and costed.
Planned URL changes, redirect rules and post-launch validation for replatforms and redesigns, or the repair plan where a migration already went ahead without them.
Validated Schema.org markup for the organisation, its pages, products, locations and FAQs, tested against Rich Results.
Core Web Vitals diagnosis plus clean, accessible implementation across the templates and components the plan requires.
Verification that GPTBot, ClaudeBot, PerplexityBot and Google-Extended can fetch the site, with CDN or firewall rules corrected and an accurate llms.txt published.
Google Business Profile, NAP consistency and local schema where the business trades in a place, plus hreflang and market targeting where it trades in several.
Search Console and GA4 configuration, reliable events, conversion definitions and plain-English reporting tied to meaningful customer actions.
A foundation does not create demand by itself. It prevents valuable visibility from being weakened by poor access, unreliable data, unclear journeys or slow implementation.
Fit
Supporting insight
These guides explain the strategy, evidence and decisions behind this service, with practical detail for teams assessing what to do next.
Service questions
A diagnostic conversation, not a pitch. We reply within two UK working days.