How long until we see the effect?

Indexing and rendering fixes can show within weeks. Rankings take longer, but speed improves conversion right away.

Do we need this if the site is new?

If we built it, the review is already included. If another team built it, a technical review is worth doing.

Does it still matter with AI search?

More than before: answer engines are less forgiving of broken structure.

What if the problem is the platform?

We'll tell you. Some problems can only be fixed by changing platforms.

Grow · 03.2

The part nobody sees and everything depends on.

Technical SEO isn't a growth tactic. It's the foundation that lets the other tactics work: a page that crawlers can't reach, render or understand won't rank or appear in AI answers.

Grow

LCP ✓INP ✓CLS ✓index ✓

01 / When

Signs it's a technical problem.

Check what you see on your site.

If two or more sound familiar, it’s time.

01
Pages that don't get indexed
Content is still missing from search weeks later, or the wrong version appears.
02
Content that depends on scripts
The initial HTML is nearly empty and the content only appears after JavaScript runs.
03
A slow site on mobile
Speed metrics are poor on real devices, even though desktop seems fine.
04
Thousands of URLs nobody created
Filters, parameters and pagination generate near-duplicate pages.

02 / Included

What the work includes.

Fixes shipped and measured, not just a list of problems.

Fixes shipped

We work alongside your developers, or we ship the changes ourselves.

Priority by impact

The few most important issues come first.

Structured data from content

Schema generated from each page's real data.

Before and after measurement

Every change is compared against a baseline.

Ongoing monitoring

Errors, indexing and speed checked on a schedule.

Documented decisions

The reasoning behind each change is written down.

03 / What to watch

What we usually find.

Each risk, and how we avoid it.

×Content that only appears after JavaScript runs.

Key content is rendered on the server.

×Near-duplicate URLs from filters and parameters.

Crawl rules and canonicals for each URL pattern.

×Canonicals pointing to the wrong page.

Canonicals audited template by template.

×Unreviewed third-party scripts slowing rendering.

A script inventory listing each script's cost and owner.

×Schema copied from an example that describes something the page doesn't contain.

Schema generated from the page's actual fields.

04 / How it works

How it works.

Our usual way of working. The quote sets the real dates before work starts.

Week 1
Diagnose
Full crawl, render comparison, index coverage and speed measured on real devices. Deliverables: technical findings and a priority list.
Weeks 2–3
Fix what blocks
Indexing, rendering, duplicates and canonicals. Deliverables: fixes shipped and a new baseline.
Weeks 4–6
Structure and speed
Internal linking, hierarchy, structured data and performance. Deliverables: structural changes and a Core Web Vitals report.
Ongoing
Monitor
Coverage, errors and speed tracked, with a monthly note. Deliverables: monitoring and a monthly report.

05 / Questions

Questions we get asked

Often, and it's usually cheaper. We diagnose, specify and review.

Also in Grow

The rest of Grow.

Grow · 03.1

Visibility audit

Two weeks, one deliverable and an honest verdict.

Grow · 03.3

Generative engine optimization

Becoming the source answers are built from.

Grow · 03.4

Content clusters

Covering a topic thoroughly enough to become the source.

Find out where you stand.

Send us your URL. We'll tell you which searches you should own, which answers leave you out and what it would take to change that.