Menu

Menu

Menu

Technical SEO that lets everything else work

Crawling, rendering, site speed, structured data and migrations, handled by the kind of senior specialist you would hope a technical SEO agency puts on your account. Every issue is traced to its cause and handed to your developers as a fix they can ship.

What it is

The part of SEO your developers own

Technical SEO covers everything that decides whether search engines and AI crawlers can crawl and render your pages, and understand what each one is for. When it goes wrong, good content and hard-won links go to waste, and the damage tends to surface as a fall in traffic nobody can explain.

Most faults live in templates. One mistake repeats across every page built on that template, and one fix clears it everywhere. The work is finding the few faults that cost the most, then writing each fix so a developer can ship it without a meeting.

It matters most when a site changes, in a replatform or a move into new markets, and on large sites, especially those built on JavaScript frameworks. If a migration has already cost you traffic, start with Troubleshooting and Recovery. If you want the full picture first, start with an audit.

Approach

How we find what is holding the site back

01

Crawled the way Google sees it

We crawl with JavaScript rendering on and compare what a browser shows with what a crawler receives. On modern stacks the two are often different.

01

Crawled the way Google sees it

We crawl with JavaScript rendering on and compare what a browser shows with what a crawler receives. On modern stacks the two are often different.

01

Crawled the way Google sees it

We crawl with JavaScript rendering on and compare what a browser shows with what a crawler receives. On modern stacks the two are often different.

02

Checked against your own data

Crawl findings are tested against Search Console’s indexing and crawl reports and your analytics, so the work targets the pages search engines actually visit.

02

Checked against your own data

Crawl findings are tested against Search Console’s indexing and crawl reports and your analytics, so the work targets the pages search engines actually visit.

02

Checked against your own data

Crawl findings are tested against Search Console’s indexing and crawl reports and your analytics, so the work targets the pages search engines actually visit.

03

Fixed at the template

Issues are grouped by the template that causes them, so a single change clears every page built on it.

03

Fixed at the template

Issues are grouped by the template that causes them, so a single change clears every page built on it.

03

Fixed at the template

Issues are grouped by the template that causes them, so a single change clears every page built on it.

04

Ranked by impact and effort

Each fix carries its likely effect and the development effort involved, so your team can plan it into a sprint.

04

Ranked by impact and effort

Each fix carries its likely effect and the development effort involved, so your team can plan it into a sprint.

04

Ranked by impact and effort

Each fix carries its likely effect and the development effort involved, so your team can plan it into a sprint.

05

Checked once live

We check each fix after release, in the rendered page and in Search Console, and reopen anything that did not hold.

05

Checked once live

We check each fix after release, in the rendered page and in Search Console, and reopen anything that did not hold.

05

Checked once live

We check each fix after release, in the rendered page and in Search Console, and reopen anything that did not hold.

What you get

Seven areas, each handed over as fixes

Every area ends in tickets your developers can pick up, with the evidence and the pages affected attached.

01

Crawl and index control

What search engines and AI crawlers waste time on, and what should never have been indexed, with the robots.txt and sitemap changes that fix both.

01

Crawl and index control

What search engines and AI crawlers waste time on, and what should never have been indexed, with the robots.txt and sitemap changes that fix both.

01

Crawl and index control

What search engines and AI crawlers waste time on, and what should never have been indexed, with the robots.txt and sitemap changes that fix both.

02

Site architecture

Hierarchy and internal links arranged so authority reaches the pages that earn money.

02

Site architecture

Hierarchy and internal links arranged so authority reaches the pages that earn money.

02

Site architecture

Hierarchy and internal links arranged so authority reaches the pages that earn money.

03

Core Web Vitals

Real-user performance traced to the specific cause, with fixes a developer can act on without guesswork.

03

Core Web Vitals

Real-user performance traced to the specific cause, with fixes a developer can act on without guesswork.

03

Core Web Vitals

Real-user performance traced to the specific cause, with fixes a developer can act on without guesswork.

04

JavaScript rendering

A comparison of what a browser shows and what a crawler receives on your key templates, and the changes that close the gap.

04

JavaScript rendering

A comparison of what a browser shows and what a crawler receives on your key templates, and the changes that close the gap.

04

JavaScript rendering

A comparison of what a browser shows and what a crawler receives on your key templates, and the changes that close the gap.

05

Migration plan

For a replatform or redesign: the redirect map, checks of the new site against the old before launch, a rollback point, then monitoring once it is live.

05

Migration plan

For a replatform or redesign: the redirect map, checks of the new site against the old before launch, a rollback point, then monitoring once it is live.

05

Migration plan

For a replatform or redesign: the redirect map, checks of the new site against the old before launch, a rollback point, then monitoring once it is live.

06

Structured data

Schema that validates and matches what each page shows, for rich results and for AI systems reading the page.

06

Structured data

Schema that validates and matches what each page shows, for rich results and for AI systems reading the page.

06

Structured data

Schema that validates and matches what each page shows, for rich results and for AI systems reading the page.

07

International setup

Market and language versions structured so each searcher lands on the version meant for them, with hreflang that is valid and reciprocal.

07

International setup

Market and language versions structured so each searcher lands on the version meant for them, with hreflang that is valid and reciprocal.

07

International setup

Market and language versions structured so each searcher lands on the version meant for them, with hreflang that is valid and reciprocal.

FAQ

Common questions

Answers to what most people ask before we start. If yours is not here, get in touch.

Contact us

Contact us

What does a technical SEO audit cover?

How search engines and AI crawlers reach the site, what they can render, what gets indexed, how fast pages load for real users, how the site is structured and linked, and whether its structured data is valid. Each finding is traced to its cause and comes with a fix.

What does a technical SEO audit cover?

How search engines and AI crawlers reach the site, what they can render, what gets indexed, how fast pages load for real users, how the site is structured and linked, and whether its structured data is valid. Each finding is traced to its cause and comes with a fix.

Can you work directly with our developers?

Yes, and it is usually the quickest route. Fixes are written as tickets with the evidence and the expected effect attached, and we answer your developers’ questions as they build. Your team makes the changes, so nothing ships without your sign-off.

Can you work directly with our developers?

Yes, and it is usually the quickest route. Fixes are written as tickets with the evidence and the expected effect attached, and we answer your developers’ questions as they build. Your team makes the changes, so nothing ships without your sign-off.

How do you protect traffic during a site migration?

We map every old URL to its new home and check the new site against the old one before launch. A rollback point is agreed in case something breaks, and after launch we watch indexing and traffic until the numbers settle. The earlier we are involved, the more of the risk can be designed out.

How do you protect traffic during a site migration?

We map every old URL to its new home and check the new site against the old one before launch. A rollback point is agreed in case something breaks, and after launch we watch indexing and traffic until the numbers settle. The earlier we are involved, the more of the risk can be designed out.

Do Core Web Vitals affect rankings?

Google says its ranking systems use them, and also that relevant content can still rank with a weaker page experience. So we treat speed as one input among several. We fix what your real-user data shows is slowing the templates that earn money, and we say so when speed is not your biggest problem.

Do Core Web Vitals affect rankings?

Google says its ranking systems use them, and also that relevant content can still rank with a weaker page experience. So we treat speed as one input among several. We fix what your real-user data shows is slowing the templates that earn money, and we say so when speed is not your biggest problem.

Do you handle international sites and hreflang?

Yes. We check how each market version is structured and whether its hreflang tags are valid and reciprocal, then confirm searchers land on the version meant for them. Addam has run search across the UK, US, Germany, France, Italy, Australia, South Korea and Japan.

Do you handle international sites and hreflang?

Yes. We check how each market version is structured and whether its hreflang tags are valid and reciprocal, then confirm searchers land on the version meant for them. Addam has run search across the UK, US, Germany, France, Italy, Australia, South Korea and Japan.

Ready to find what is holding your site back?

One conversation with the person who would actually do the work. No juniors, no handoffs.

Start the conversation

Start the conversation

Start the conversation