Technical SEO Audit: The 80-Point Checklist Used by Top Agencies

Author: Guy Sheetrit Updated Date: May 24, 2026 Category: Advanced SEO Techniques

A proper technical SEO audit isn’t a checklist exercise — it’s a diagnostic investigation. Most sites have 3–7 critical technical issues actively suppressing their rankings, and another 15–30 minor issues creating cumulative drag. The goal of this guide is to give you the exact 80-point framework our agency uses to find and prioritize every one of them.

This checklist is organized by impact tier: we start with indexability (if Google can’t crawl it, nothing else matters), then move through performance, structure, structured data, and authority. Work through it in order.

Contents

Tier 1: Crawl & Indexability (Points 1–20)

Nothing matters if search engines can’t access and index your pages. Audit these first — a single misconfigured robots.txt has tanked enterprise sites overnight.

Robots.txt (Points 1–5)

Robots.txt is accessible — Verify your robots.txt loads at yourdomain.com/robots.txt and returns a 200 status. A 404 here is bad; a 5xx is catastrophic.
No unintended Disallow rules — Audit every Disallow directive. “Disallow: /” blocks your entire site. Disallow rules blocking CSS/JS prevent Google from rendering your pages.
Sitemaps are referenced — Your robots.txt should contain a Sitemap: directive pointing to your XML sitemap location.
Crawl-delay not set aggressively — Crawl-delay limits how fast Googlebot crawls. Too aggressive and you’ll leave indexing on the table. Only set this if you have server capacity issues.
No conflicting allow/disallow rules — Overlapping directives cause unpredictable crawl behavior. Audit for conflicts.

XML Sitemaps (Points 6–10)

XML sitemap exists and is valid — Validate your sitemap against the sitemaps.org protocol. Tools: Google Search Console sitemap report, Screaming Frog.
Sitemap contains only indexable URLs — No noindex pages, redirects, or 404s in your sitemap. These waste crawl budget and signal poor quality.
Sitemap is under 50,000 URLs / 50MB — If larger, implement a sitemap index file with multiple child sitemaps.
Lastmod dates are accurate — Use dynamic lastmod that reflects actual last-modified dates. Static or incorrect dates reduce crawl prioritization.
Sitemap is submitted to Google Search Console and Bing Webmaster Tools

Indexation (Points 11–16)

Correct pages are indexed — Compare your expected indexable page count against what Google actually indexes (Search Console → Pages report). Large discrepancies need investigation.
No unintended noindex tags — Audit every noindex directive. CMS plugins frequently noindex pages by accident (especially WordPress SEO plugins on certain templates).
Canonical tags are correct — Every indexable page should have a self-referencing canonical. Duplicate or cross-domain canonicals must be intentional and accurate.
No canonical/noindex conflicts — A noindex page with a canonical pointing to an indexable page creates mixed signals.
Pagination handled correctly — For paginated content, ensure the paginated URLs are either indexable (with unique content) or canonicalized to the first page.
International pages use hreflang correctly — Hreflang errors are endemic. Validate with Screaming Frog or Ahrefs. Common errors: missing return tags, incorrect language codes, pointing to noindex pages.

Crawl Efficiency (Points 17–20)

Server response times under 200ms TTFB — Time to first byte above 500ms signals a performance problem that impacts crawl rate and user experience.
No crawl traps — Session IDs, infinite calendar pages, faceted navigation generating millions of URLs. Use URL parameters in Google Search Console to limit crawl waste.
No significant redirect chains — Chains of 3+ redirects waste crawl budget and dilute link equity. Map and flatten your redirect chains.
Crawl budget is allocated to priority pages — Log file analysis shows you exactly what Googlebot is crawling. High-value pages getting crawled less than low-value pages? Fix your internal linking and sitemap prioritization.

Tier 2: Performance & Core Web Vitals (Points 21–35)

Core Web Vitals are a direct ranking factor. More importantly, they affect conversion rates — every 100ms of load time improvement is worth meaningful revenue.

Largest Contentful Paint — LCP (Points 21–25)

LCP under 2.5s on mobile — This is the “good” threshold. Above 4s is “poor” and will hurt rankings.
LCP element is a prioritized resource — The hero image or above-fold text block that triggers LCP should be preloaded, not lazy-loaded.
Hero images are correctly sized — Serving a 2000px image for a 800px container wastes bytes and delays LCP.
Server-side rendering or prerendering for dynamic content — If your LCP element is rendered by JavaScript, the browser must execute JS before it paints. Consider SSR for above-fold content.
No render-blocking resources above the fold — CSS and JS that blocks rendering delays LCP. Move non-critical scripts to deferred or async loading.

Cumulative Layout Shift — CLS (Points 26–29)

CLS under 0.1 — Layout shifts above 0.25 are “poor.” Common culprits: images without dimensions, ads loading late, fonts causing FOUT.
All images have explicit width and height attributes — The single most common CLS cause. Missing dimensions mean the browser can’t reserve space before the image loads.
Web fonts use font-display: swap or optional — Prevents invisible text and reduces font-related layout shifts.
Ad slots have reserved dimensions — Dynamic ads without reserved space are a major CLS source on monetized sites.

Interaction to Next Paint — INP (Points 30–32)

INP under 200ms — INP replaced FID as a Core Web Vital. It measures responsiveness to all interactions, not just first input.
No long tasks blocking the main thread — JavaScript that runs for 50ms+ blocks interaction response. Audit with Chrome DevTools Performance panel.
Third-party scripts evaluated for INP impact — Chat widgets, analytics, and ad scripts are common INP culprits. Audit each one.

General Performance (Points 33–35)

Images use modern formats (WebP, AVIF) — 20–35% smaller than JPEG/PNG with equivalent quality.
Efficient cache policies on static assets — CSS, JS, and images should be served with long cache TTLs (1 year) and cache-busted via versioned filenames.
Content delivery network (CDN) in use — For any site with global traffic, a CDN reduces TTFB significantly for non-local users.

Tier 3: Site Architecture & Structure (Points 36–50)

URL Structure (Points 36–40)

URLs are clean, descriptive, and consistent — Lowercase, hyphens (not underscores), no unnecessary parameters.
URL depth is reasonable — Important pages should be reachable within 3 clicks from the homepage. Pages buried 5+ levels deep get crawled less frequently.
No dynamic URL parameters for indexable content — ?page=2&sort=date creates duplicate content issues. Static, descriptive URLs are strongly preferred.
Consistent trailing slash policy — Either use trailing slashes everywhere or nowhere. Mixed usage creates duplicate content (yourdomain.com/page/ and yourdomain.com/page are technically different URLs).
URL changes are handled with 301 redirects — Never change URLs without implementing permanent redirects from old to new.

Internal Linking (Points 41–46)

All important pages receive internal links — Orphan pages (no internal links pointing to them) get crawled infrequently and rank poorly.
Anchor text is descriptive and varied — Over-optimized exact-match anchor text in internal links is an under-discussed issue. Use natural, descriptive text.
No broken internal links — Screaming Frog or Ahrefs can identify all 404 internal links. Fix or redirect immediately.
Link equity flows to priority pages — Map your internal linking to ensure high-value conversion pages receive link equity from high-traffic informational pages.
No excessive links per page — Hundreds of links per page dilutes link equity. A reasonable maximum is 100–150 internal links per page.
Breadcrumbs implemented sitewide — Breadcrumbs improve crawl efficiency, user experience, and qualify for breadcrumb rich results in SERPs.

Duplicate Content (Points 47–50)

www vs. non-www resolved to one version — Implement a 301 redirect and canonical to ensure all traffic lands on one version.
HTTP redirects to HTTPS — Every HTTP URL should 301 redirect to HTTPS equivalent.
Duplicate page variants handled with canonicals — Print pages, AMP pages, and tracking parameter variants need canonical tags.
Content syndication uses canonical or noindex — If your content is syndicated to other sites, ensure canonical attribution points back to your original or that the syndicated versions are noindexed.

Tier 4: On-Page Technical Factors (Points 51–63)

Title Tags & Meta (Points 51–55)

Every page has a unique title tag — Duplicate titles are one of the most common issues on large sites.
Title tags are within 50–60 characters — Truncated titles lose click-through rate.
Every page has a unique meta description — While not a direct ranking factor, well-written meta descriptions significantly impact CTR.
No missing H1 tags — Every page should have exactly one H1 that clearly states the topic.
Heading hierarchy is logical (H1 → H2 → H3) — Heading structure communicates content organization to crawlers and improves accessibility.

Images (Points 56–59)

All images have descriptive alt text — Improves accessibility and provides context for image indexing.
Images are compressed appropriately — Use tools like Squoosh, ImageOptim, or server-side compression pipelines.
Image filenames are descriptive — “hero-image.jpg” vs. “technical-seo-audit-checklist-2026.jpg” — the latter provides topical context.
No images larger than 1MB on standard pages — Large images are among the most common page weight issues.

JavaScript SEO (Points 60–63)

Critical content not JavaScript-dependent for rendering — Use Google’s Mobile-Friendly Test and Rich Results Test with JavaScript disabled to see what Googlebot sees without JS execution.
Internal links in HTML, not only JavaScript — Links only in JS event handlers may not be followed by all crawlers.
Lazy loading implemented correctly — Images below the fold should be lazy-loaded; above-the-fold content should not be lazy-loaded.
No infinite scroll without pagination fallback — Infinite scroll content is often not crawled. Implement a /page/2/ URL structure as a fallback.

Tier 5: Structured Data & Schema (Points 64–72)

Schema markup is implemented on appropriate pages — Article, Product, FAQ, HowTo, LocalBusiness, Person — use schema types relevant to your content.
No schema validation errors — Validate with Google’s Rich Results Test and Schema.org validator.
BreadcrumbList schema matches visible breadcrumbs — Schema should reflect the actual page hierarchy.
FAQPage schema on FAQ content — FAQ schema can generate rich results (accordion-style) in SERPs.
Product schema on product pages (if applicable) — Includes price, availability, reviews — enables product rich results and Google Shopping integration.
Organization schema on homepage — Establishes entity identity including logo, sitelinks searchbox, contact info.
No schema on pages that don’t qualify — Adding FAQ schema to non-FAQ pages is a quality guideline violation.
Schema is in JSON-LD format — Google’s preferred format, easier to maintain than microdata or RDFa.
Schema supports GEO/AI search via entity markup — Ensure your schema clearly establishes topic associations for GEO optimization.

Tier 6: Security & Mobile (Points 73–80)

Security (Points 73–76)

HTTPS with valid SSL certificate — Certificate must be from a trusted CA, not expired, and correctly covers all subdomains used.
HSTS header implemented — HTTP Strict Transport Security tells browsers to only connect via HTTPS, preventing protocol downgrade attacks.
No mixed content warnings — HTTPS pages loading HTTP resources generate browser warnings and reduce security scores.
Security headers implemented — X-Frame-Options, Content-Security-Policy, X-Content-Type-Options. These don’t directly impact SEO but signal a well-maintained site.

Mobile (Points 77–80)

Mobile-friendly confirmed in Google Search Console — Check the Mobile Usability report for issues.
Viewport meta tag is correctly set — <meta name=”viewport” content=”width=device-width, initial-scale=1″> is required for correct mobile rendering.
Tap targets are appropriately sized — Buttons and links should be at least 48×48px with adequate spacing.
No interstitials that obstruct content on mobile — Intrusive interstitials (pop-ups that cover content) are a negative ranking signal on mobile.

How to Prioritize Your Findings

After running this 80-point audit, you’ll have a list of issues. Here’s how to prioritize them:

P1 — Fix Immediately (within 1 week)

Any issue preventing indexation (wrong robots.txt, noindex on key pages), 5xx server errors, Core Web Vitals failures in “poor” range, security certificate issues.

P2 — Fix in Current Sprint (within 1 month)

Redirect chains, canonical issues, missing structured data on high-traffic pages, broken internal links, CLS/LCP in “needs improvement” range.

P3 — Schedule for Next Quarter

URL structure improvements (these require careful redirect planning), JavaScript SEO improvements, advanced schema implementation, hreflang optimization.

For a personalized prioritization of your site’s technical issues, our team can provide a customized audit report.

Ready to Dominate AI Search?

Our team at Over The Top SEO has helped hundreds of businesses achieve top visibility in AI-powered search results. Let’s build your strategy.

Get Your Free SEO Qualification →

Frequently Asked Questions

What is a technical SEO audit?

A technical SEO audit is a comprehensive analysis of a website’s infrastructure to identify issues that prevent search engines from effectively crawling, indexing, and ranking your pages. It examines factors including site architecture, page speed, mobile optimization, structured data, Core Web Vitals, crawl efficiency, HTTPS security, URL structure, and more.

How long does a technical SEO audit take?

A thorough technical SEO audit for a medium-sized site (1,000–10,000 pages) typically takes 15–40 hours of expert time. Large enterprise sites can require 80–200+ hours. Using tools like Screaming Frog, Ahrefs, or Semrush can automate data collection, but analysis and prioritization of findings requires human expertise. Quick “flash audits” covering critical issues can be done in 3–5 hours.

What tools do I need for a technical SEO audit?

The core tool stack includes: Screaming Frog SEO Spider (crawl analysis), Google Search Console (indexing data, Core Web Vitals), Google PageSpeed Insights (performance), Ahrefs or Semrush (backlink profiles, site explorer), Bing Webmaster Tools (additional crawl data), and GTmetrix or WebPageTest (deep performance analysis). For JavaScript-heavy sites, also use Chrome DevTools and Puppeteer-based crawlers.

What are the most critical technical SEO issues to fix first?

Prioritize in this order: (1) Indexability blockers — noindex tags, disallow rules, or server errors preventing pages from being indexed; (2) Core Web Vitals failures — especially LCP above 2.5s and CLS above 0.1; (3) Duplicate content and canonicalization issues; (4) Crawl waste — large numbers of irrelevant URLs consuming crawl budget; (5) Broken internal links and redirect chains.

How often should I run a technical SEO audit?

Run a full technical SEO audit quarterly. Additionally, perform automated monitoring weekly for critical metrics (crawl errors, indexation changes, Core Web Vitals regressions). After any major site redesign, CMS migration, or hosting change, run a full audit immediately. Monthly, review Google Search Console for new indexing issues.

By Guy Sheetrit
May 24, 2026

Technical SEO Audit: The 80-Point Checklist Used by Top Agencies