Technical audit

Technical audit: what is actually holding the site back.

We look at the site the way a crawler does: can it reach the pages that matter, does it see duplicates, does it get the content in time. The output is not eighty pages of theory but a prioritised task list with the consequences spelled out.

Available as a standalone service or as the first stage before an SEO engagement.

Technical SEO sets the conditions under which the rest of the work can produce anything at all. You can write perfect copy for a page blocked in robots.txt and get nothing back. That is why the audit always comes first.

Scope of work

What is included in the service.

01

Crawlability

robots.txt, directives, click depth, orphan pages, crawl budget.

02

Indexing

What made it into the index, what is excluded and why; noindex in unexpected places.

03

Response codes and redirects

404 and 5xx errors, redirect chains, redirects to addresses that no longer exist.

04

Duplicates and canonicals

The same content on different URLs, filters, parameters, trailing-slash variants.

05

Structured data

Whether the markup exists, whether it validates and whether it matches what is on the page.

06

Core Web Vitals

LCP, INP and CLS on mobile — with the specific causes, not a single overall score.

07

Internal links

How authority is distributed and which important pages are left without links.

08

Images and media

Formats, dimensions, attributes, lazy loading.

09

JavaScript rendering

Whether the crawler sees content that only appears once scripts have run.

10

Sitemap and language versions

Whether the sitemap is current, plus hreflang and the correctness of language versions if there are any.

Numbers

How we measure the result.

Crawl
Crawl errors in Search Console
Index
Indexed pages versus pages in the sitemap
CWV
Share of URLs in the green Core Web Vitals band
Dupes
Number of duplicates and stray canonicals

Our approach

A proven path to the result.

  1. 01 Data collection Crawling the site, Search Console data, analytics and server logs where available.
  2. 02 Analysis We group findings by type and assess the real impact of each one.
  3. 03 Prioritisation We split them into critical, important and nice to have — with the consequences explained.
  4. 04 Report and walkthrough A document with tasks plus a call where we answer questions.
  5. 05 Implementation If you want, we take the tasks on, or hand them to your team.

FAQ

Questions we get asked most often.

Checks on crawlability and indexing, response codes and redirects, duplicates and canonicals, structured data, speed against Core Web Vitals, internal links, images and JavaScript rendering. The output is a prioritised task list.

For a typical service website, usually a few working days once we have access. A large catalogue with filters takes longer, because most of the work there is untangling duplicates and parameters.

Google Search Console, analytics, access to the site’s admin area and ideally to the server or its logs. Without Search Console part of the picture is missing — that is where you see what the crawler actually gets.

We can. The audit and the fixes are separate stages: after the report you decide whether your team takes the tasks or we do. The report is written so that any external developer can work from it.

Yes — a short pre-launch check saves months. The most common findings on new sites are a staging domain still blocked from indexing, missing meta tags and incorrect canonicals.

Let's talk

Describe the task — we will tell you how to solve it.

Even if you do not end up needing our services. One conversation, after which you have a clear next step.