Technical SEO

From SEO audit to priority list, step by step

What a technical SEO audit checks, how to prepare it and how thousands of findings become a short list.

Michael WeberLast updated: October 15, 20269 min read
In short
  • An SEO audit checks whether Google can find, fetch, render and index your pages, and whether the content answers search queries well.
  • A crawl quickly produces thousands of findings. The value of the audit lies in the order, weighted by affected URLs and clicks.
  • An audit is a snapshot. The next release can put new errors live.

What does an SEO audit cover?

An SEO audit is a structured check of your website for everything that costs visibility in search. The benchmark is Google Search Essentials, which consist of three parts: the technical requirements, the spam policies and the key best practices.

The minimum technical requirements are short. Googlebot must not be blocked, the page must respond with status 200 and it needs indexable content. On large websites, entire page types often fail on exactly these points, for example because of a noindex in the template or an overly broad rule in robots.txt.

AreaKey question
CrawlingDoes Google find and reach all important URLs?
IndexingAre the pages allowed into the index, and which version counts as the original?
RenderingIs the content still in the HTML after JavaScript has run?
Content and snippetsDo the title, heading and text answer the query?
Internal linkingDo the pages link to the important targets with descriptive anchor texts?
PerformanceDo the pages achieve good Core Web Vitals for real users?

Audit and monitoring

An audit answers the question of where the website stands today. Monitoring checks the same points continuously and alerts you when something changes. The two complement each other. The audit defines what good looks like, and monitoring keeps it that way.

Preparation

A good audit starts before the first crawl. Without a goal and a data basis, you end up with a long list that nobody works through.

  1. Set the goal. Is it about a traffic loss, a planned relaunch or a status review?
  2. Define page types, such as category, product, filter, guide and brand, with example URLs for each type.
  3. Connect data sources. Search Console provides clicks per URL, analytics provides revenue or leads. Log files show what Googlebot actually fetches.
  4. Configure the crawl. Turn on JavaScript rendering and add URLs from the XML sitemap and Search Console as extra sources, so that unlinked pages show up too.
  5. Clarify access. Many servers block unknown crawlers. An IP allowlisting is often needed.

The audit areas

The following table is the checklist for the technical part. Most points have their own guide with details.

CheckWhat you checkGuide
Status codes4xx and 5xx, redirect chains, internal links to redirects404 errors, 301/302
robots.txtBlocks on important directories, CSS and JavaScriptIndexing
Indexingnoindex in the HTML and HTTP header, Page indexing reportIndexing
CanonicalsSelf-reference, canonicalization to 404s or redirects, conflict with hreflangCanonical
hreflangReturn links, language and country codes, indexable targethreflang
XML sitemapsOnly indexable URLs with status 200, limits of 50,000 URLs and 50 MB per fileXML sitemap
RenderingRaw HTML against rendered HTML, title, links and content after JavaScriptJavaScript crawling study
Internal linksPages without internal links, click depth, anchor texts
Structured dataErrors and warnings, markup matching the visible contentSchema markup and AI
Core Web VitalsLCP, INP and CLS from field data per page typeCore Web Vitals

You can check individual responses quickly in the terminal. This shows the status code, redirect and a noindex in the header at a glance.

curl -sI https://www.example.com/kategorie/gartenmoebel/ | grep -iE "^HTTP|x-robots-tag|location|link" HTTP/2 200 x-robots-tag: noindex

The example shows a typical finding. The page responds with 200, but the header excludes it from the index.

What you can leave out

Google's SEO Starter Guide lists points that play no role in search. These include the meta keywords tag, a particular text length, keywords in the domain name and the order of headings. According to Google, duplicate content is not a violation of the spam policies. It does cost crawl resources, though. In an audit, such points belong in a footnote at most.

Prioritizing

The first crawl of a large website is often overwhelming. Tens of thousands of missing meta descriptions sit next to a noindex on every category. So sort every finding by three questions.

  1. How many URLs does it affect, and which page types?
  2. How many Search Console clicks do these URLs have, or how much revenue?
  3. Does the error prevent crawling or indexing, or does it only make the presentation worse?
Rule of thumb

Whatever prevents pages with clicks from being indexed goes to the top. Whatever only affects pages without clicks and blocks nothing goes to the bottom, even if the number of findings is large.

The result is a short list with owners. Each point describes the cause, the affected page types, example URLs and the expected effect.

After the audit

Once fixes are in place, you crawl the affected page types again and check whether the fix is live. In Search Console, URL Inspection shows how Google now sees a page. According to Google, it takes hours to months before changes show up in search.

The risk after an audit is the next release. A template update can bring back a noindex or overwrite canonicals, and the last audit will not notice. That is why it pays to repeat the most important checks regularly.

Common mistakes

  • Crawling without JavaScript rendering. Shops and single-page apps then lack links and content.
  • Weighting all findings equally and starting with the easiest.
  • Only checking linked URLs. Pages that only appear in the sitemap or Search Console stay invisible.
  • Handing over the audit as a PDF and never opening it again.
  • Checking points that Google says play no role, such as meta keywords.

FAQ

What is an SEO audit?

A structured check of your website for everything that costs visibility in search, from crawling and indexing to rendering, content and performance. The result is a prioritized list of actions.

Can I do an SEO audit myself?

Yes. You need access to Search Console, a crawler with JavaScript rendering and time for the assessment. The checklist above covers the technical part.

How often should I do an SEO audit?

A full audit before larger projects such as a relaunch and after heavy traffic losses. Repeat the most important technical checks after every release or monitor them continuously.

How long does an SEO audit take?

That depends on size and goal. Crawling a large website takes hours to days, and the assessment and prioritization usually take longer than the crawl itself.

Which tools do I need?

Google Search Console, a crawler with JavaScript rendering and, for large websites, log files. PageSpeed Insights shows the Core Web Vitals of individual pages.

Can ChatGPT do an SEO audit?

A language model can assess individual pages and explain findings. For an audit it lacks the data, meaning a complete crawl, the clicks from Search Console and the log files.

searchVIU crawls your website every week including JavaScript and runs over 100 automatic checks, sorted by impact. searchVIU compares raw and rendered HTML for every page, with the Search Console clicks right next to it. Find out more on the SEO Audit Tool page.

Request a demo

Sources

Retrieved on October 15, 2026. If something is out of date or missing, let us know.

  1. Google Search Essentials: https://developers.google.com/search/docs/essentials · As of Dec 10, 2025
  2. Google, Technical requirements: https://developers.google.com/search/docs/essentials/technical · As of Dec 18, 2025
  3. Google, SEO Starter Guide: https://developers.google.com/search/docs/fundamentals/seo-starter-guide · As of Dec 10, 2025
  4. Search Console Help, Page indexing report: https://support.google.com/webmasters/answer/7440203 · Retrieved Oct 15, 2026
  5. sitemaps.org, protocol: https://www.sitemaps.org/protocol.html