Technical SEO consulting
What is technical SEO?
Technical SEO is the work that makes a site easy for search engines and answer engines to crawl, render, index, and trust. It covers site architecture, crawl and indexation control, structured data, Core Web Vitals, and rendering. Get the foundation wrong and even excellent content never ranks.
Your content is good. Your rankings are not. More often than the writing, the cause is technical: the site is hard for Google and answer engines to crawl, render, or trust.
A technical audit finds the crawl, render, indexation, and architecture issues holding the whole domain back, then sequences the fixes by return so the cheap, high-impact ones ship first.
What technical SEO actually covers
Not a checklist for its own sake. The work that decides whether a search engine, or an answer engine, can reach your pages, understand them, and trust them enough to rank.
- Crawl and indexation. log analysis, crawl-budget waste, orphan pages, the robots and canonical rules that quietly keep your best pages out of the index.
- Site architecture. how depth, internal links, and URL structure tell search engines what the site is about and which pages matter most.
- Rendering. whether your content exists in the HTML a crawler sees, or only after JavaScript a crawler may never run.
- Structured data. the JSON-LD that lets Google and LLMs read what a page is, reconciled so there is one clean version, not three conflicting ones.
- Core Web Vitals. the loading, interaction, and stability signals that are a real ranking input and a real conversion input, fixed where the cost is low.
- Migrations and recovery. the audit before a replatform, and the diagnosis after a traffic drop, so you know what is recoverable instead of guessing.
How a technical engagement runs
Diagnosis first, always. The cheapest wins are usually the ones that need no new content, so I find those before anyone writes a word.
- Audit. a full technical, crawl, and schema read on the live site and the GSC data, scored by impact and effort, not severity theatre.
- Sequence. a prioritised plan: the template-level fixes that lift many pages at once go first, the long tail goes later.
- Ship. fixes implemented with your developers, or specced precisely enough that your team ships them without me in the loop.
- Hand over. a playbook and the internal-linking and schema rules baked into your templates, so the foundation holds after the engagement ends.
When technical SEO is the right call
A site whose organic channel has stalled or quietly declined while the content kept coming. A replatform on the calendar that you do not want to tank traffic. A team that can execute against a clear brief and wants to own the result, not rent it.
It is the wrong call if the real problem is that the content does not answer what people search. In that case I will tell you that, and we start with topic clusters or AEO instead. The point is the highest-return work first, not the work that bills the most.
Common questions
- How is this different from a generic SEO audit?
- A generic audit hands you a 200-row spreadsheet sorted by a tool severity score. This sorts by return on your specific site: which fixes lift the most pages for the least effort, sequenced so you ship the cheap, high-impact ones first.
- Do you implement the fixes or just recommend them?
- Both are on the table. I implement directly with your developers, or I spec the fixes precisely enough that your team ships them without me. The goal is a foundation your team owns, not a dependency on me.
- Does technical SEO help with AI answer engines too?
- Yes. The same crawlability, rendering, and structured-data work that helps Google is what lets ChatGPT, Perplexity, and Google AI Overviews read and cite your pages. Technical SEO and AEO share most of the plumbing.
What you get back
- Foundation firstthe highest-return fixes shipped before any new content
- A playbookthe rules baked into your templates, so your team holds the gains