Technical SEO Audit: What Gets Checked and What You Receive
A technical SEO audit shows whether Google can properly crawl, render and index your pages - and what exactly is getting in the way. I run technical SEO audits by hand, with Screaming Frog, Google Search Console and server logs, and deliver a prioritized list of issues with a ready-to-use spec for your developer instead of an automated report. The first step is a free express audit.
Contents
- How a technical audit differs from a full SEO audit
- When you need technical SEO audit services
- What a technical SEO audit checks
- Tools I use
- How I work: stages of a technical audit
- What the deliverable looks like
- Typical findings of a technical audit
- Why work with me
- Pricing and how to start
- Checklist: when you need a technical audit now
- Frequently asked questions
- Summary
How a technical audit differs from a full SEO audit
A full SEO audit looks at the whole site: technical setup, content, meta tags, backlinks and competitors. A technical audit goes deep into one part only - how the site is built and how a search engine crawler sees it. I cover the full audit, its types and scope in a separate article: SEO audit: what it includes and how to avoid paying for a worthless report.
| Aspect | Full SEO audit | Technical audit |
|---|---|---|
| Focus | Why the site does not rank, overall | Whether Google can access the site and whether technical blockers exist |
| What is analyzed | Technical setup, content, keywords, backlinks, competitors | Crawling, indexing, architecture, rendering, speed, status codes |
| Technical depth | Core checks | Every page template, server logs, JavaScript rendering |
| Who receives the result | Owner, marketer, SEO team | Primarily the developer |
A simple rule: a page that is not in the index does not rank, no matter how good the content is.
When you need technical SEO audit services
You need a technical audit when site changes or sheer size create a risk that Google sees something different from what you see.
| Situation | Business risk | What I check first |
|---|---|---|
| Before launch | The site goes live blocked from indexing or full of duplicates | robots.txt, noindex, canonical, sitemap, status codes |
| After a redesign or migration | Lost rankings due to changed URLs and broken redirects | 301 redirect map, old URLs, internal links |
| Traffic drop | Pages dropped out of the index or lost rankings | Search Console statuses, template changes, logs |
| Large catalog or store | Google spends its resources on filters and duplicates instead of products | Crawl budget, parameters, pagination, logs |
| Slow site | Worse user experience and conversion, especially on mobile | Core Web Vitals, page weight, scripts |
If traffic has already dropped, a technical audit is part of finding the cause. I describe how I investigate drops in the article on traffic drop recovery.
What a technical SEO audit checks
Below is the full list of areas. Not every site needs all of them: a single-language landing page does not need hreflang.
| Area | What I check |
|---|---|
| Crawling | robots.txt, sitemap.xml, crawl budget, server logs for large sites: which pages Googlebot actually visits |
| Indexing | Page statuses in Search Console, canonical, noindex, duplicates, URLs with parameters and filters |
| Architecture | Click depth, internal links, orphan pages with no links pointing to them, pagination |
| Rendering | JavaScript sites: whether Googlebot sees the text, links and meta tags after rendering |
| Status codes | 404, 5xx, soft 404, redirect chains and loops, links pointing to redirects |
| Speed | Core Web Vitals (LCP, INP, CLS) from real-user data plus lab tests |
| Mobile | Same content and markup on mobile and desktop, responsive layout |
| HTTPS | Certificate, HTTP to HTTPS redirect, mixed content |
| Structured data | Valid schema.org markup that matches the visible content |
| hreflang | For multilingual sites: return links, language codes, x-default, consistency with canonical |
| Security | Security issues report in Search Console, hacked pages, spam URLs in the index |
Crawling and indexing
This is the most important area. I compare three lists: what is in the sitemap, what the crawler finds and what Google has actually indexed. The gaps between them are the most valuable finding. I also check the "Crawled - currently not indexed" and "Discovered - currently not indexed" statuses in Search Console: they often point to duplicates, thin templates or crawling problems.
According to Google itself, crawl budget is not a concern for most sites with up to a few thousand pages. For stores with faceted filters it is the opposite: thousands of parameter combinations eat up the crawler's attention. Server logs help here - they show where Googlebot really goes.
Rendering JavaScript sites
If the site is built on React, Vue or similar frameworks, I check what Google sees after rendering: through URL Inspection in Search Console and by comparing the raw HTML with the rendered version. A typical problem is links without a regular href that the crawler never discovers.
Duplicates, canonical and parameters
Duplicates come from sorting parameters, UTM tags, trailing slashes, www and non-www versions. The key is that canonical tags, internal links and the sitemap all point to the same version of a page. More on this in the article on canonical tags and duplicate pages.
Get a free express audit
Send me your site URL - I will check indexing, crawling and the main technical errors and tell you whether you need a full technical audit.
Message me on TelegramTools I use
- Screaming Frog SEO Spider - full site crawl, status codes, canonical, redirects, click depth, JavaScript rendering, log file analysis;
- Google Search Console - Google's own data: indexing, URL Inspection, Core Web Vitals, security, sitemaps;
- PageSpeed Insights - speed from real-user data (CrUX) and the Lighthouse lab test;
- Ahrefs Site Audit - scheduled crawls and monitoring of new errors after site changes.
Tools only collect data. Conclusions and priorities are manual work: a tool does not know that a noindex tag on a page is intentional.
How I work: stages of a technical audit
Free express audit
I review the site and Search Console, find the most visible problems and explain whether a deep audit makes sense. Sometimes two or three fixes are enough.
Data collection
I get access to Search Console and, if needed, to server logs. I crawl the site with Screaming Frog, with rendering for JavaScript sites. I group pages by template: home page, categories, products, articles, filters.
Analysis and priorities
I rate each issue on two scales: impact on traffic and effort to fix. A template error that affects a thousand products goes first, and minor issues on a single page come later.
Spec for the developer
I write tasks so a developer can start on them without extra explanations: what exactly to change, on which URLs or templates and how to verify the result.
Re-check after fixes
After the fixes, I crawl the site again and verify every item in the spec. Then I monitor indexing in Search Console: Google reprocesses pages gradually, so the effect shows over time.
What the deliverable looks like
The result is a working document, not a 100-page automated PDF. It contains:
| Issue | Impact | Effort | Priority |
|---|---|---|---|
| Catalog filters are open to indexing and create duplicates | High | Medium | 1 |
| Chains of 3-4 redirects left from an old migration | Medium | Low | 2 |
| Some article images have no alt text | Low | Low | 3 |
The table above shows the format, not the results of a specific site. Each item comes with a description, sample URLs and a spec. Fixes are usually implemented by your developer or the agency that maintains the site.
Timelines depend on the size and complexity of the site: a landing page and a store with 100,000 URLs are very different amounts of work. I give an exact timeline after the express audit.
Typical findings of a technical audit
- The site is blocked from indexing after development. A leftover Disallow: / in robots.txt or noindex on every page from the staging version;
- Filters and sorting pages get indexed. Thousands of near-identical URLs, while important categories are crawled less often;
- Broken redirects after a migration. Old URLs return 404 or point to the home page instead of the matching page;
- Canonical contradicts the links. The canonical points to one version, while the menu and sitemap point to another;
- Slow LCP caused by heavy images and scripts. Especially on mobile;
- hreflang errors. Missing return links between language versions, or hreflang pointing to redirected pages.
Why work with me
I have 13+ years in SEO and 70+ projects. From 2016 to 2022 I led SEO for Ukraine International Airlines across 40+ markets - a multilingual site with hreflang and a complex structure. I have worked with manufacturer and B2B equipment catalogs and with finance (YMYL) sites. Today I am Head of SEO at the SportLife fitness chain. I work remotely and communicate in English in writing, via Telegram or email.
An example of results in a competitive local services niche: organic traffic to sportlife.ua grew from 35,495 (spring 2024) to 131,003 visits per month at the seasonal peak (May 2026), 8,000+ keywords, DR 52 in Ahrefs, local SEO for clubs in 20+ cities. The site's technical foundation was part of this work.
Pricing and how to start
The first step is a free express audit. After it, I tell you whether you need a full technical audit, what the scope is and how long it will take. If you then need ongoing SEO, monthly SEO starts from $450/month. The exact budget depends on your niche, competition and site size. What monthly work includes is covered in the article on monthly SEO services.
Checklist: when you need a technical audit now
- You are planning a launch, redesign, move to a new CMS or domain change
- The number of "Crawled - currently not indexed" pages in Search Console is growing
- Traffic has dropped, but nothing changed in the content
- Your catalog has thousands of products and filters with URL parameters
- PageSpeed Insights shows poor Core Web Vitals on mobile
- Your site has several language versions
Frequently asked questions
How much does a technical SEO audit cost?
It depends on the size and complexity of the site, so I define the scope and timeline after a free express audit. Monthly SEO after the audit starts from $450/month.
How long does a technical SEO audit take?
It depends on the number of URLs, templates and the data available. I give an exact timeline after the express audit.
What do you need from me?
View access to Google Search Console, ideally also to Google Analytics 4. For large sites, server logs for the last few weeks. And your developer's contact so we can align on the spec.
Who fixes the issues you find?
Usually your developer or agency. I provide the spec, answer questions in writing during implementation and verify the result with a new crawl.
Does a new website need a technical audit?
Yes, ideally before launch. Fixing robots.txt, canonical tags and redirects before indexing is easier than winning back lost rankings later.
Summary
A technical SEO audit answers one question: can Google crawl, understand and index your pages. Its value is not in the number of errors found, but in clear priorities and a spec your developer can actually implement.
Order a technical SEO audit
We start with a free express audit: I check indexing and the main technical issues, then propose a prioritized plan of work.
Send a request