Technical SEO Audit Scope: What It Covers and What It Doesn't
Short answer A technical SEO audit checks whether Google can reach, load and store your pages: crawling, indexing, errors, redirects, HTTPS, speed on phones and how pages link. It doesn't judge your writing, design, ads, legal pages or conversions. Before it starts, write down which addresses it covers, what access you give, what the report looks like and who fixes things.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhat does a technical SEO audit cover?
The plumbing: can Google find each page, load it, and store it in its index? Google sets three minimum conditions for a page to be eligible:
"Googlebot isn't blocked. The page works, meaning that Google receives an HTTP 200 (success) status code. The page has indexable content." (Google Search Central: Google Search technical requirements)
A technical audit tests those three, plus the things around them that Google's documentation names:
| In scope | The question it answers | Free place to look |
|---|---|---|
| Crawling | Is anything blocking Google, such as robots.txt or a login wall? | Search Console: Page indexing and Crawl stats reports |
| Indexing | Which pages are left out of Google, and why? | Search Console: Page indexing report, URL Inspection |
| Errors and redirects | Broken pages (404), server errors (5xx), redirect chains | A site crawler; URL Inspection |
| Duplicates | Does one page live at several addresses (www and not, http and https)? | Search Console: URL Inspection tool |
| Sitemap | Does it list the real, live pages? | Open your sitemap (often yoursite.com/sitemap.xml) and compare |
| HTTPS | Is every page served securely? | Search Console: HTTPS report |
| Speed on phones | Do pages pass Core Web Vitals? | Search Console: Core Web Vitals report |
| Internal links | Can Google and visitors reach every service page through links? | A site crawler |
| JavaScript | Does content added by scripts show up for Google? | URL Inspection or Rich Results Test: view the rendered HTML |
| Structured data | Is schema markup valid and true to the page? | Google's Rich Results Test |
Google's own report names changed. The old Coverage report is now Page indexing, and the Mobile-Friendly Test is gone: Google retired it, its API and the Mobile Usability report on December 1, 2023 (Google Search Central Blog, April 2023). A scope that lists either is copied from an old template.
Speed belongs in scope, but with limits. Google says "Core Web Vitals are used by our ranking systems," and also that good scores don't "guarantee that your pages will rank at the top" (Google Search Central: Understanding page experience). More in Core Web Vitals and ranking.
What a technical SEO audit doesn't cover
Anything about what your site says, how it sells, or what happens off the site. An audit may mention these in passing, but it shouldn't bill for them.
| Out of scope | Who handles it | Read more |
|---|---|---|
| Quality of your writing, which services to add | Content writer or SEO strategist | On-page SEO for service pages |
| Backlinks, reviews, directory listings | SEO strategist | Backlinks for a local business |
| Google Business Profile | Local SEO help | Local SEO checklist |
| Look, layout, booking flow | Designer, conversion specialist | Website not getting leads |
| Google Ads, Meta ads | Ads manager | SEO vs Google Ads |
| Privacy policy, cookie banners, accessibility law | Lawyer, developer | ADA website compliance |
| Firewalls, backups, hosting upkeep | Your host or IT person | Ask your host |
Paid ads are out for a plain reason. Google says:
"Advertising with Google won't have any effect on your site's presence in our search results" (Google Search Central: Do you need an SEO?)
Gray areas to settle before work starts
These sit on the border. Neither answer is wrong; just agree on it in writing so nobody bills twice or skips it.
| Item | Usually in a technical audit? | Why it's unclear |
|---|---|---|
| Page titles and descriptions | Missing or duplicate ones, yes; rewording them, no | Spotting is technical; writing is content |
| Call and form tracking | A check that it works, often yes; building it, no | Without it nobody can tell whether fixes paid off. See GA4 key events |
| AI crawlers in robots.txt | Checking what's blocked, yes | Whether to block them is a business choice. See blocking AI crawlers |
| Fixing what it finds | Separate unless written in | Many audits only diagnose |
| Slow server response | Flagging it, yes; fixing the server, no | The fix is your host's job |
How to write the scope before you buy or run one
Seven lines on one page. The same list works whether you hire someone or audit your own site.
- Addresses. Every domain and subdomain: www and non-www, a booking or shop page on another platform, a blog on a subdomain, an old domain that redirects.
- Size. Total pages, and the 10 or so that bring customers (service, location, contact pages). Those get checked by hand; the rest by a crawler.
- Access. Read-only. Google's advice for an audit: "only grant read access to Search Console (at this stage, don't grant them write access)" (Google Search Central: Do you need an SEO?). Add analytics viewer access if tracking is in scope.
- Rendering. If the site is custom-built or heavy on JavaScript, say the audit must check the rendered page. Google renders scripts later, "Once Google's resources allow" (Google Search Central: Understand the JavaScript SEO basics).
- Deliverable. Each finding names the pages, the cause, the fix, who does it and the effort. Google says an audit "should be about giving you realistic estimates of improvement, and an estimate of the work involved" (Google Search Central: Do you need an SEO?).
- Fixes. Included or not, and who does them: you, your web developer, your host, or the auditor.
- Re-check. One follow-up crawl after fixes, with a date, compared against the indexed pages and search clicks recorded at the start.
Ask for evidence beside each finding. Google warns that third-party tools "don't have access to Google's internal ranking data" (Google Search Central: Do you need an SEO?), so a tool's score is not Google's view.
How big should the audit be?
Match it to the site, not to the longest checklist on offer.
| Your site | Fitting scope |
|---|---|
| Under a few hundred pages on Wix, Squarespace, Shopify or WordPress | Search Console reports plus one crawl. Hours, not weeks |
| Custom-built or JavaScript-heavy | Add rendering checks on key templates |
| Planning a redesign or domain move | Add a list of old and new addresses and a redirect plan. See traffic after a redesign |
| Tens of thousands of pages that change daily | Add crawl budget and server log review |
Crawl budget is often padded into small-site audits. Google's guide is meant for sites with "1 million+ unique pages" changing weekly, or "10,000+ unique pages" changing daily (Google Search Central: Crawl budget management for large sites). Prices for each size are in how much SEO costs.
Example
A 30-page plumbing site on WordPress
The scope covers the main domain and the booking widget's subdomain, with read-only Search Console access. The report finds 6 service pages left out of the index by a leftover "noindex" tag and a redirect chain on the old /services/ address. Fixing both takes the web developer about 2 hours. Content and Google Business Profile wait for a separate project.
A med spa quoted a "full technical audit"
The proposal lists crawl budget, social media and ad account reviews. The site has 80 pages. The owner strikes the three, adds a tracking check for the booking form, and asks for one re-check after fixes.
An accounting firm moving to a new domain
The scope adds a map of 120 old addresses to new ones, written before launch, and a check of the redirects the week after.
FAQ
Is a technical SEO audit the same as a full SEO audit?
No. A technical audit covers whether Google can reach and store your pages. A full audit adds content, links, local listings and tracking.
Does a technical SEO audit include fixing the problems?
Only if the scope says so. Many audits deliver a fix list; your developer, host or the auditor does the work as a separate job.
What access should I give an auditor?
Read-only Search Console access, as Google advises, and viewer access to analytics if tracking is in scope. No passwords to your website editor until fixes start.
How long does a technical audit take for a small site?
For a template-built site of a few dozen pages, the checks themselves take hours. Longer quotes should name the extra work.
Different for you?
- Running the checks yourself: Google Search Console for a small business.
- Pages crawled but not indexed: crawled or discovered, not indexed.
- Site missing from Google entirely: website not showing on Google.
- Choosing who does the audit: hiring an SEO company.
- Want the technical checks and fixes done for you: SEO agent.