Technical SEO Audit Checklist for Site Owners
Most audits fail because they treat every issue as equal. This guide ranks problems by business impact, then covers crawlability, architecture, speed, mobile and structured data. You will finish with a technical SEO audit checklist you can run yourself.
Key Takeaways
- Rank findings by business value and technical severity, not by failed-check count.
- Keep money pages within three clicks of the homepage, since deeper pages are crawled less often.
- Audit mobile rendering first, since mobile accounts for around 62 to 64% of online traffic.
- Judge Core Web Vitals against 2026 thresholds (LCP under 2.5 seconds, INP under 200ms, CLS under 0.1) using Search Console field data.
- Log each finding with its URL, quadrant and owner, then re-audit on a fixed schedule.
Table of Contents
- Technical SEO Audit Fundamentals: What an Audit Checks and Why It Matters
- Crawlability and Indexation: Making Sure Google Can Find and Keep Your Pages
- URL structure analysis: readable, stable, consistent URLs
- Internal linking audit: finding orphaned pages, broken links and weak anchors
- Page Speed, Core Web Vitals and Mobile Optimization
- Building Your Audit Checklist and Prioritizing Fixes
- Conclusion and Summary
- Frequently Asked Questions
Technical SEO Audit Fundamentals: What an Audit Checks and Why It Matters
Technical SEO covers how search engines reach, render and store your pages. Content explains what a page means, and links signal how much the web trusts it, but technical SEO decides whether either can be read at all. A strong article that Google cannot crawl or index earns nothing from search results. A regular technical SEO audit checklist catches these blockers before they cost traffic. Each audit surfaces crawl and indexing issues, along with duplicate content. Speed issues can be checked with PageSpeed Insights, and a full review of your website’s structure should cover all of them.
When a site owner should run a technical audit
Run a full audit before launch, before and after a migration, when organic traffic drops without a clear cause, and quarterly. Sudden losses can also reflect Google policy decisions, so check policy as well as configuration. Review internal links and their anchor text, since descriptive wording helps search engines understand each target page.
The audit workflow in brief
Work in five stages: crawl the site, diagnose each finding, prioritise it, fix it, then verify the fix in Search Console. Prioritisation is where most audits go wrong, so see the Priority Triage Matrix later in this guide.
Crawlability and Indexation: Making Sure Google Can Find and Keep Your Pages
Confirm that search engines can reach your important pages and keep them indexed. A page that does not rank is often not indexed, or is blocked somewhere in the chain. Run a regular technical SEO audit checklist as part of your recurring SEO audits to catch these issues before they cost you traffic.
robots.txt and XML sitemaps
Check your robots.txt file first. It should allow crawling of every revenue or lead page and block only admin areas, cart sessions and internal search results. Pass: no Disallow rule covers a revenue page. Fail: a stray Disallow: / line left from staging hides the site. Test URLs with the robots.txt report in Google Search Console, then submit an XML sitemap listing only canonical, indexable URLs.
Reading the Page indexing report
Open the Page indexing report under Indexing in Search Console and sort by reason. “Discovered, currently not indexed” usually signals low perceived value or weak internal links. “Excluded by noindex tag” is a configuration fault you can fix directly. Pass: every priority URL is indexed. Fail: a priority URL sits under an exclusion reason.
Click depth and the three-click rule
Keep important pages within three clicks of the homepage, since pages five or six clicks deep get crawled less often. Pass: each priority URL is reachable in three clicks or fewer. Fail: a priority URL sits deeper. Add links from higher-level pages or move it into the main navigation.
URL structure analysis: readable, stable, consistent URLs
Check site URLs for mixed casing, session IDs, duplicate paths and addresses that change after updates. Pass: each URL is lowercase, has no session parameters and returns one version of the page. Fail: any URL that returns more than one version or changes after an update. Log failing URLs in the Priority Triage Matrix.
Internal linking audit: finding orphaned pages, broken links and weak anchors
Crawl the site to find orphaned pages, fix broken internal links and replace vague anchors like “click here” with descriptive text. Pass: every page has an internal link and every anchor names its target.
Page Speed, Core Web Vitals and Mobile Optimization
Core Web Vitals show whether a page feels fast and responsive, so check them before cosmetic fixes. Mobile devices account for around 62 to 64% of online traffic, so test mobile first.
The 2026 thresholds to aim for are:
- Largest Contentful Paint (LCP): under 2.5 seconds
- Interaction to Next Paint (INP): under 200 milliseconds
- Cumulative Layout Shift (CLS): under 0.1
Core Web Vitals are a modest ranking signal, so treat speed fixes as a way to reduce visitor friction, not a shortcut to rankings. Pairing speed fixes with [internal linking](internal linking) helps visitors and crawlers reach key pages faster, and surfacing performance issues early keeps templates from degrading over time.
Field data versus lab scores
Read real Core Web Vitals in Search Console’s Core Web Vitals report, which uses field data from real users. Pass: each metric is under its threshold for mobile and desktop. Fail: any metric is over threshold for a group of URLs. A single PageSpeed Insights lab score shows one test, not visitor experience.
Mobile optimization and responsive design checks
Google retired its Mobile-Friendly Test in December 2023, so check mobile rendering with Search Console’s URL Inspection tool and real devices. Pass: text reads without zooming and tap targets are spaced apart. Fail: either problem appears on a priority template.
Structured Data and Schema Markup
Structured data helps search engines understand what a page is about. Validate markup with Google’s Rich Results Test and fix errors that block rich results. Only mark up visible content. Schema does not change rankings on its own.
Google stopped showing FAQ rich results in May 2026, so FAQ schema no longer produces a visible search enhancement. Keep FAQ content for readers, but do not expect a rich result.
Canonical tags and title tags
Check that each indexable page has one canonical tag matching its sitemap URL. Pass: one canonical per page, matching the sitemap. Fail: duplicate or missing tags. Review title tags for duplicates and missing tags, which make pages harder to tell apart.
Building Your Audit Checklist and Prioritizing Fixes
A checklist is only useful when it tells you what to fix first. Group every finding by URL, then score it on two axes: the business value of the URL group and the severity of the technical problem across your website.
Priority Triage Matrix
Score each finding as the revenue share of its URL group multiplied by a severity weight (3 for a blocked revenue page, 2 for a slow template, 1 for a cosmetic issue). A product group earning 40% of revenue with severity 3 scores 1.2, while a blog archive earning 5% with severity 3 scores 0.15. This is one way to order work by business value, not a rule search engines apply; your own revenue data may justify a different order.
| Quadrant | Business value | Technical severity | Action |
|---|---|---|---|
| 1 | High | High | Fix this week |
| 2 | High | Low | Fix in the next sprint |
| 3 | Low | High | Schedule when capacity allows |
| 4 | Low | Low | Log and monitor |
Ranking by business value rather than issue count is the core of this method. A single blocked product page should outrank 47 failed checks on a blog archive.
Worked example: reordering the list
An audit returns 12 findings, and a flat list would start with 9 cosmetic blog title and meta issues. Scored by the matrix, a crawl block on a product group worth 40% of revenue moves to position one.
Before and after: triage in practice
Before triage, a team fixed issues in the order the tool reported them and spent two weeks on archive canonicals. After triage, it fixed the blocked product group in two days.
Verifying fixes and setting a recurring schedule
After each fix, check the affected URLs in Search Console to confirm the change has been picked up. Re-run the full audit each quarter and after any major site change.
Page Speed, Core Web Vitals and Mobile Optimization
Core Web Vitals and mobile performance are checked in two passes. Lab tools find causes, and field data confirms results on real visits. Start with lead- and sales-driving pages, and trace each issue back to the template it affects. A full site audit of the website helps identify which templates to fix first.
The 2026 thresholds: LCP under 2.5 seconds, INP under 200ms, CLS under 0.1
Treat these as pass marks for your highest-value pages:
- LCP: under 2.5 seconds
- INP: under 200ms
- CLS: under 0.1
Why INP replaced FID and what it measures across the whole session
INP replaced First Input Delay as a Core Web Vital in March 2024. FID measured only the first tap, while INP measures responsiveness across the whole page session. A checkout page that stutters on the fifth click fails even if its first interaction was quick.
Field data versus lab scores: where to read real Core Web Vitals in Search Console
A lab score is a diagnostic, not a verdict. Read real-user field data in the Core Web Vitals report in Search Console, then confirm lab-identified fixes in field data weeks later.
Mobile optimization and responsive design checks
Mobile devices account for around 62 to 64% of all online traffic, so audit mobile rendering first. Check that tap targets, text and forms work at phone width, and that the mobile version carries the same content and structured data as desktop.
- Load the URL at phone width in a device emulator, or with the URL Inspection tool’s live test.
- Confirm buttons and links are easy to tap, and forms can be completed.
- Compare headings, text and structured data with desktop. Any removed content or markup is a fail.
Google retired its Mobile-Friendly Test in December 2023, so use the emulator and Search Console checks instead. For tooling comparisons, see our guide to seo tools.
Structured Data and Schema Markup
Structured data is where a technical audit often finds hidden losses. A page can rank well and still miss rich results, or show Google different content than users see.
Validating schema markup and fixing errors that block rich results
Run every template through the Rich Results Test and check Search Console enhancement reports. Errors block rich results, while warnings usually flag missing recommended fields. Fix errors on revenue pages first.
Rich result changes to know about: FAQ and HowTo display updates
Do not add FAQ or HowTo markup expecting a visible result. Google dropped HowTo rich results in 2023 and stopped showing FAQ rich results in May 2026.
JavaScript rendering: confirming Googlebot sees the same content users do
Compare raw HTML with the rendered DOM using the URL Inspection tool in Search Console. If headings, product details or internal links appear only after scripts run, Google may index a thinner page.
AI crawler access: what blocking Google-Extended does and does not change
Google-Extended controls whether your content may be used to train Google’s AI models. Blocking it does not remove your site from Google Search, which uses a separate crawler. Decide this as a content policy question, and confirm the robots.txt rule does not accidentally block Googlebot.
Building Your Audit Checklist and Prioritizing Fixes
Start from pages that earn revenue or leads, then work outward. Score each finding by business value first, then by technical severity, and use anchor text that describes the destination clearly. Keep the audit centered on the pages that drive your website’s results, and treat your SEO audits as a recurring process rather than a one-off project.
The step-by-step checklist, grouped by area
Work through each area in this order, because crawl and index problems hide everything that comes after them:
- Crawl: confirm robots.txt does not block key sections, and that the sitemap lists only canonical, indexable URLs.
- Index: review the Page indexing report in Search Console for excluded or removed URLs, including duplicate content flagged as excluded.
- Architecture: check that important pages sit within three clicks of the homepage.
- Speed: check Core Web Vitals field data against the 2026 thresholds: LCP under 2.5 seconds, INP under 200ms and CLS under 0.1.
- Mobile: render key templates on a phone first, confirming content, navigation and forms work at phone width.
- Markup: validate schema on pages that can earn rich results, and fix errors first.
Scoring issues by impact and effort
Place each finding on two axes: Business Page Value (high, medium or low) and Technical Severity (blocks indexing or crawling, degrades performance, or is cosmetic). This is one prioritisation model, not a rule search engines apply, so adjust it to your own revenue picture.
| Quadrant | Typical finding | Action |
|---|---|---|
| Fix now | High value page, blocks indexing | Fix this sprint |
| Schedule | High value page, degrades performance | Plan within the quarter |
| Monitor | Low value page, degrades performance | Track in the next audit |
| Ignore | Low value page, cosmetic | Leave alone |
Log each finding with its URL, quadrant and owner so no issue goes untracked.
Verifying fixes and setting a recurring schedule
Confirm each fix with the URL Inspection tool, then recheck field data after the next reporting cycle, since Core Web Vitals reflect real user sessions. Run a full audit each quarter and a focused check after any migration or redesign.
Conclusion and Summary
Work through the technical SEO audit checklist in sequence: crawl, confirm indexing, check architecture and speed, validate markup, then fix by business value. Keep key pages within three clicks of the homepage. Measure Search Console field data against LCP under 2.5 seconds, INP under 200ms and CLS under 0.1. Audit mobile first. Log each finding with its URL, priority and owner, then repeat on a fixed schedule.
Technical SEO Audit Checklist for Site Owners: Frequently Asked Questions
How often should a site owner run a technical SEO audit checklist?
Run a full technical SEO audit checklist quarterly, before and after launches or migrations, and whenever organic traffic drops without a clear cause. Check the Page indexing and Core Web Vitals reports in Search Console monthly, and treat any new error spikes as a signal to run a site audit sooner.
Can I run a technical SEO audit without paid tools?
Yes. Search Console’s Page indexing report, Core Web Vitals report, URL Inspection tool and Rich Results Test are free, and a free crawler covers broken links and canonical tags. For paid options, see our technical SEO tools comparison.
Why are my pages marked as “Discovered, currently not indexed”?
Google has found the URL but has not crawled it yet, often because the page has few internal links or low perceived value. Strengthen internal links, improve the content and confirm the page is in your sitemap, since issues like these are common on a large website.
Do Core Web Vitals directly affect rankings?
They are a modest ranking signal. Content relevance outweighs them, but poor performance still hurts visitor experience and conversions.
Will fixing schema markup improve click-through rate?
Correct structured data helps search engines understand a page, but it does not guarantee higher click-through rates. Google stopped showing FAQ rich results in May 2026, so check current documentation first.
Does blocking AI crawlers remove my site from Google Search?
No. Google-Extended controls whether content may be used to train Google’s AI models, and blocking it does not stop Googlebot from crawling or indexing pages. Review the Google-Extended documentation on Google Search Central before changing this setting, and consider a professional SEO audit if you are unsure of the impact.
Disclosure: digitalmarketingtools.ai is sponsored by Digimetrics.ai. Sponsored Highlights are clearly labelled advertising. Our reviews, comparisons and guides are written to be useful and fair regardless of who sponsors the site. Read the full disclosure.
