Crawl and compare
Pull crawl data, index coverage, logs where available, templates, sitemap entries and ranking pages into one view.
Updated
Technical SEO Crawl, render, index
Technical SEO Consultant UK
I find the technical issues that stop useful pages being crawled, indexed and trusted. Then I turn them into clear fixes your developers can ship. No 80-page audit theatre. No "everything is priority one". Just the work that protects rankings and revenue.
technical_seo.json
"service""Technical SEO consultancy"
"checks"[
"crawl waste",
"indexation gaps",
"JavaScript rendering",
"Core Web Vitals",
"schema graph",
"migration risk"
]
"output""Fix list with acceptance criteria"
// what I check
The technical layer decides whether good pages get a chance.
Most technical audits list symptoms. I separate noise from blockers, then show the smallest set of changes likely to move search performance.
Start with the crawl, not the opinions.
I compare crawl data, indexed URLs, server responses, templates, canonicals and internal links. If Google is spending effort on duplicate URLs while commercial pages sit two clicks too deep, that is the work. If the technical layer is clean, I say that and move budget to content or authority.
Crawl wasteFacets, parameter URLs, thin templates, redirects and dead ends that soak up crawl attention.
IndexationNoindex drift, canonical conflicts, sitemap bloat and pages Google knows about but will not keep indexed.
RenderingJavaScript paths where content, links, metadata or schema arrive too late or inconsistently.
PerformanceLCP, INP and CLS issues traced to the templates and resources causing the problem.
// technical SEO audit
What a technical SEO audit should answer.
The audit should tell you which search systems are failing, what that failure costs, and what your developers need to change first.
What is a technical SEO audit?
A technical SEO audit checks whether search engines can crawl, render, index and trust the pages that matter. It should identify blockers, estimate business impact and turn fixes into developer-ready tickets.
The useful checks are not just crawler warnings. They include live rendering, canonical logic, sitemap hygiene, internal links, structured data and whether AI crawlers can access the same content as Google.
For quick checks, start with the AI Schema Validator and the AI Bot robots.txt Tester. For revenue pages, I still run the manual diagnosis.
| Area | What gets checked | Useful output |
|---|---|---|
| Crawlability | Blocked paths, redirect chains, dead ends, crawl traps and parameter URLs. | Rules for what should be crawled, blocked, redirected or removed. |
| Indexation | Noindex drift, canonical conflicts, duplicate templates and sitemap mismatch. | A clean indexable URL set with priority pages protected. |
| Rendering | Whether links, copy, metadata and schema exist before and after JavaScript renders. | Template fixes your developers can test in rendered HTML. |
| Structured data | Organization, Person, Service, FAQ, Article and breadcrumb graph links. | A clearer entity graph for Google, AI Overviews and answer engines. |
| Internal links | Orphan pages, weak anchors, deep pages and missing links between related services. | Contextual links that help users and pass authority to priority pages. |
// process
How the work turns into fixes.
You get decisions, not a data dump. Every recommendation needs a clear reason, a priority and a way to check whether it worked.
Find the blockers
Separate cosmetic warnings from issues that stop discovery, indexing, ranking or conversion.
Write the tickets
Turn the fixes into developer-ready notes with acceptance criteria and before and after checks.
Verify in the data
Check the fix landed in crawl output, rendered HTML, Search Console data and live templates.
// useful when
Good fit if the site has technical drag.
This is usually the right page when the problem lives in templates, crawl paths, rendering, migrations or platform setup.
Bring me in for
- A migration that cannot afford ranking loss.
- An ecommerce site with crawl waste and duplicate URL patterns.
- A SaaS or app site where JavaScript hides key content from search engines.
- A Core Web Vitals problem your dev team needs scoped properly.
- A schema graph that exists but does not connect the brand, author, services and pages.
Outputs you can use
- Prioritised fix list with business impact and implementation notes.
- Developer tickets with acceptance criteria.
- Redirect and canonical rules for migrations or clean-ups.
- Template-level recommendations for internal links, metadata and schema.
- Retest notes showing what changed after fixes ship.
// FAQ
Technical SEO questions I get asked.
What does a technical SEO consultant fix?
I fix crawl waste, indexation gaps, JavaScript rendering problems, canonical conflicts, Core Web Vitals issues, broken internal links, schema errors and migration risks. The work ends in tickets developers can ship.
What is a technical SEO audit?
A technical SEO audit checks whether search engines can crawl, render, index and trust the pages that matter. It should turn blockers into fixes your developers can ship.
Do you work with developers?
Yes. I write the technical notes, acceptance criteria and before and after checks so developers know exactly what to change.
Is this different from a normal SEO audit?
Yes. A normal audit often lists every issue. Technical SEO consultancy prioritises the fixes that block crawling, indexing, ranking or conversion.
Can you help with migrations?
Yes. I review redirects, URL mapping, canonical logic, staging blocks, metadata parity, internal links, XML sitemaps and post-launch indexation.
Can you check JavaScript rendering?
Yes. I test what Google can access before and after rendering, then check whether metadata, links, content and schema appear in the HTML path search engines can use.
// technical SEO audit
Need the technical blockers found and fixed?
Send the site, the platform and what has changed recently. I will tell you whether the problem looks technical, content-led or authority-led before we scope any work.