Technical SEO starts with the decision you need to make
A crawler can produce thousands of observations. That does not make all of them important. The useful work is establishing which conditions affect discovery, understanding or performance, how confident we are in that diagnosis, and what the team should do next.
I scope the investigation around the business question. That could be why valuable pages are not being indexed, whether a rendering approach creates search risk, how templates distribute internal authority, or which parts of a technical backlog deserve engineering time.
What I investigate
The exact work depends on the site, but the investigation can span crawlability, indexation, rendering, information architecture, internal linking, canonicalisation, structured data, faceted navigation, international targeting and performance.
- Google Search Console, analytics and server evidence alongside crawl data
- Templates and page types rather than isolated URLs
- JavaScript rendering and differences between source, rendered HTML and indexed output
- Hreflang, canonical and international-site relationships
- Duplicate, thin and unintentionally generated URL populations
- Structured data that accurately represents visible content
- Internal linking, crawl paths and information architecture
- Measurement plans for changes that cannot be evaluated immediately
Recommendations designed to survive implementation
A recommendation is only useful if a team can implement and verify it. Findings are translated into the level of detail needed by developers, product owners and stakeholders. Important requirements include the intended behaviour, examples, acceptance criteria, dependencies and a way to test the result.
Where the same issue recurs, I can help turn the solution into documentation, reusable checks or lightweight automation so the team does not need to rediscover it during every release.
A senior consultant without an open-ended production queue
Most engagements are defined investigations, advisory periods or support around a particular programme of work. I can stay involved through implementation and validation, but the objective is to leave the team with clarity and capability rather than permanent dependency.
What you receive
- A clearly defined investigation rather than an indiscriminate list of checks
- Evidence from crawling, indexation, templates, rendering and performance data
- Prioritised recommendations connected to risk and commercial value
- Developer-ready requirements, acceptance criteria and QA checks
- A walkthrough for the people who will implement the work
- Follow-up validation after important changes are released
What the work is designed to change
- A shared explanation of what is limiting search performance
- Fewer low-value tickets and clearer engineering priorities
- Greater confidence before committing to architectural change
- A repeatable way to verify that fixes worked
Common questions
What does a technical SEO consultant do?+
A technical SEO consultant investigates how a website is crawled, rendered, indexed and understood. The work connects technical evidence to priorities, implementation requirements and measurable outcomes rather than stopping at a list of tool warnings.
Can you work directly with developers?+
Yes. I regularly translate findings into tickets, examples, acceptance criteria, documentation and QA checks, then work with engineering and product teams through implementation.
Do you provide one-off technical SEO audits?+
Yes. A focused audit or diagnostic sprint is often the right format when there is a defined problem. Broader advisory support is available when the work spans multiple teams or releases.
Do you work remotely?+
Yes. My consultancy is designed for remote delivery across the UK and internationally, including workshops, stakeholder sessions and developer collaboration.