Technical SEO

Find it, then fix it

An audit that names every technical problem holding your site back, what each one is worth, and how to fix it. Then we fix it. One engagement, fixed scope, an end date.

Findings reportSample
404s inside internal linksCritical
Canonical tags missing on templatesCritical
LCP over 4s on the CMS templateHigh
Duplicate title tags across 40 pagesMedium
Orphan pages with no internal linksLow

Every finding comes with the URLs affected, the fix, and what it is worth. Sorted by impact, not alphabetically.

Crawlability
Indexing
Core Web Vitals
Schema Markup
Site Architecture
Page Speed
Crawlability
Indexing
The deliverable

An audit you can use

Most technical SEO audits are a PDF of red and green circles produced by a tool, with a covering page and no idea which of the 340 issues matters. The difference is not how much we find. It is whether anyone can do anything with it afterwards.

In the report
The usual audit
What we send
How findings are ordered
By category, or by whatever order the crawler emitted them in.
By what fixing it is worth. The top five items are the ones to do this month.
How many issues
Three hundred, because a long list looks like value.
However many are real. Cosmetic findings are listed separately and marked as optional.
The fix
“Add canonical tags.” No location, no method, no owner.
The URLs affected, the specific change, and which template or setting it lives in.
Performance data
One Lighthouse run on the homepage, on a fast connection.
Field data from real users, on the templates that actually carry your traffic.
Who can act on it
Only the agency that wrote it, which is rather the point of it.
Any competent developer, including one who is not us. It is written to be handed over.
What happens next
A proposal for a twelve-month retainer.
A fixed price to implement, with the audit fee taken off it. Or nothing, and you keep the report.
Why the audit is paid

A free audit attracts people who want a free audit. Charging for it means we spend real days on yours rather than running a tool and pasting the output — and because the fee comes off the implementation price, it costs you nothing if you go ahead. If you would rather have a free look first, our migration pages offer exactly that; this is a different depth of work.

Scope

What gets checked

Six areas, on any stack. Webflow, WordPress, Shopify, Next.js or something your team built — the physics are the same.

01

Crawl and indexation

What Google can reach, what it chooses to index, and what it is wasting crawl budget on. Robots rules, sitemaps, noindex left on from staging, parameter URLs multiplying.

Coverage
02

Speed and Core Web Vitals

Field data, not just a lab score. LCP, INP and CLS measured on the templates that carry your traffic, with the specific element causing each one named.

CWV field data
03

Structure and internal links

Click depth, orphan pages, where authority pools and where it leaks. The links that exist because a menu has them, versus the links that exist on purpose.

Link graph
04

Markup and schema

Heading order, semantic HTML, structured data, and whether what you have is valid or just present. Rich result eligibility checked against what Google actually parses.

Schema validity
05

Duplication and canonicals

Same content on several URLs, canonicals pointing at the wrong place, trailing-slash and www variants competing. The quiet killer on template-driven sites.

Canonical logic
06

Search Console reality

Coverage errors, manual actions, queries you rank for but did not intend to, and pages that lost impressions after a change nobody logged.

GSC history
Straight answers

What technical SEO will not do

Technical SEO is a ceiling, not an engine. It removes the reasons Google cannot rank you; it does not supply a reason it should. Four things this work does not fix, so you can judge whether it is what you actually need.

It will not write your content

Why it matters

Technical SEO makes a page eligible to rank. It does not make it worth ranking. If your pages are three paragraphs of description on a topic twenty better pages already cover, fixing your canonicals will not change your traffic and we will say so in the report rather than bill you for the fix.

It will not build your authority

Why it matters

Links and reputation are a different discipline with a different budget. A technically perfect site in a competitive market still loses to a slower site that people cite. We tell you when technical is not your bottleneck — that is most of the value of paying someone to look.

It will not create demand

Why it matters

If nobody searches for what you sell, ranking first for it changes nothing. Part of the audit is checking that the terms you want actually have volume and intent behind them, and telling you plainly when they do not.

One-time or ongoing SEO support

Why it matters

This is one engagement with an end date. Technical debt does come back as your site grows, but it comes back slowly — most sites need this properly once, then a check-up once a year, not a retainer.

Process

Crawl, prioritise, fix, verify

Six steps with a defined end. You can stop after step three with the report in hand and take it anywhere.

STEP 01

Full crawl

We crawl every reachable URL, pull your sitemaps, connect to Search Console and Analytics if you will grant read access, and take field performance data from real users rather than a single lab test.

STEP 02

Prioritise by impact

Every finding gets a severity and an estimate of what fixing it is worth. A missing canonical on your highest-traffic template outranks forty missing alt tags, and the report says so instead of listing them alphabetically.

STEP 03

Report and walkthrough

You get the findings as a working document — issue, where it is, the fix, and what it is worth — plus a call to walk through it. Yours to keep and to hand to any developer, including one who is not us.

STEP 04

Implementation

If you want us to do the work, we do it. Fixed scope taken straight from the report, so there is no second negotiation, and your audit fee comes off the price.

STEP 05

Verify, don't assume

Every fix re-tested against the thing that flagged it — re-crawled, re-validated, re-measured. A fix that was not verified is a claim, not a fix.

STEP 06

Thirty days of watching

We stay on Search Console for a month afterwards: coverage, impressions, anything that moved the wrong way. Then we hand over and get out of your way.

Which one you need

Available once or ongoing

We sell two different things and they suit two different situations. This is the honest version of which one you are looking for.

You are on the right page if

You want it fixed, once

Your traffic is flat, something feels technically wrong, and you want a specialist to find it, fix it and leave. One invoice, one end date, no monthly commitment.

You want the other page if

You want it handled monthly

You are on Webflow and you want technical work, content and authority handled continuously rather than in one pass. That is a retainer, and it is a different page.

Webflow SEO retainer →
FAQ

Technical SEO, answered

01

How is this different from your Webflow SEO retainer?

+

02

Do you only work on Webflow sites?

+

03

What exactly do I get for the audit fee?

+

04

What does it cost?

+

05

How long does it take?

+

06

Will you break my site?

+

07

What if the audit finds nothing serious?

+

Start here

Stop guessing why traffic is flat

Send the URL and we will tell you whether a technical audit is worth your money before you spend any. If it is not, we will say so — that answer is free.

Replies within one business day · US, UK & EU hours covered