SEO Audit Checklist: 18 Steps to Fix Issues Fast

Searching for an SEO audit checklist you can actually use? This 18-step guide shows exactly how to find, prioritize, and fix issues across technical, content, UX, and off‑page SEO in 2026—plus templates, scoring models, and implementation workflows.

Follow the steps in order, use the included scoring sheet to prioritize by impact/effort, and you’ll ship improvements that move rankings, Core Web Vitals, and conversions—fast.

Read This First — Audit Goals, Scope, and How to Use This Checklist

What you’ll achieve with this audit:

• Surface critical technical blockers (indexation, Core Web Vitals, structured data, mobile).
• Elevate content quality and information architecture so priority pages rise.
• Strengthen entity/E‑E‑A‑T signals, backlinks, and local/international visibility.
• Build a 30/60/90‑day roadmap with measurable KPIs and a clean implementation workflow.

How to use it:

1. Benchmark: Set up GA4, GSC, and a crawler; capture baselines for speed, rankings, and conversions.
2. Audit: Work through Technical, On‑Page/Content, Off‑Page, and SERP Features/AI sections.
3. Prioritize: Score each issue with the ICE/RICE template provided.
4. Implement: Create tickets with acceptance criteria, QA, and rollback plans.
5. Track: Report weekly; re‑audit monthly/quarterly.

Benchmark & Setup (GSC, GA4, crawling, baselines)

1. Google Search Console (GSC)
   • Verify all properties (domain + protocol + subdomains). Add users/alerts.
   • Submit XML sitemaps and check Coverage/Pages, Core Web Vitals, and Enhancements.
   • Export last 16 months: queries, pages, countries, devices, rich results.
2. GA4 and Tag Management
   • Audit GA4 data streams, time zone, referral exclusions, and internal traffic filters.
   • Validate Events/Conversions with DebugView; map key conversions (leads, checkout, demo).
   • GTM health: container versions, environments, consent mode, data layer variables, cross‑domain linking.
3. Crawling/baselines
   • Run a full crawl (Screaming Frog/Sitebulb) authenticated if needed. Include JS rendering and sitemaps.
   • Connect APIs: GSC, GA4, PageSpeed Insights, link index (Ahrefs/Majestic/Semrush).
   • Baseline speed: PageSpeed Insights + Lighthouse; prioritize field data (CrUX) over lab.
   • Set up rank tracking for priority keywords (by device/country).
4. Governance
   • Create a central tracker (issues, owners, due dates, status) and a change log.
   • Define success metrics (e.g., +20% non‑brand clicks in 90 days, LCP ≤2.5s on top templates).

Technical SEO Audit

Crawlability & Indexing (robots.txt, sitemaps, canonicals, status codes)

1. robots.txt
   • Disallow only what you truly don’t want crawled (e.g., /cart/, /search/ with faceted parameters).
   • Expose XML sitemaps with an absolute URL. Block staging environments and ensure they’re password protected.
2. Sitemaps hygiene
   • Separate sitemaps by type (pages, products, posts, images, video, news). Keep ≤50k URLs or 50MB uncompressed per file.
   • Only indexable 200 URLs; include lastmod with realistic dates; remove 3xx/4xx/5xx and noindex URLs.
3. Status codes & redirects
   • Fix 4xx/5xx on indexable URLs. Convert temporary 302s to 301s where appropriate.
   • Minimize redirect chains; prefer direct 301s. Use 410 for intentionally removed content.
4. Canonicals & parameters
   • One self‑referencing canonical per unique page; avoid conflicting canonicals in headers and HTML.
   • Handle parameters (sort, color, size) with canonicalization or noindex; avoid indexing infinite combinations.
5. Index controls
   • Use noindex,follow for pages you want crawled but not indexed (e.g., filtered category views).
   • Use X‑Robots‑Tag in headers for media/PDF control at scale.
6. Log files & crawl budget
   • Sample server logs: confirm Googlebot hits on priority pages and sitemaps.
   • Reduce waste: remove broken pagination, stop indexing session IDs, ensure stable 304 responses for unchanged assets.

Site Architecture & Internal Linking

• Depth: Priority pages should be ≤3 clicks from the homepage; build hub & spoke clusters.
• Navigation: Use descriptive anchors; enable breadcrumbs with schema; avoid internal nofollow except for true crawl budget control.
• Orphans: Identify pages with zero internal links and connect them to relevant hubs.
• Paginaton: Use clear rel links in HTML where UX requires; ensure canonicalization to page 1 is not incorrectly used on deeper pages.
• Faceted navigation: Predefine indexable faceted combinations; block the rest via canonicals/noindex.

Performance & Core Web Vitals (INP, LCP, CLS)

Targets as of 2026 for the 75th percentile of field data (mobile):

• LCP ≤ 2.5s (optimize TTFB, hero images, preconnect to critical origins).
• INP ≤ 200ms (minimize long tasks, hydrate interactives progressively, avoid heavy input handlers).
• CLS ≤ 0.10 (reserve space for media/ads, use font-display: optional/swap, avoid layout shifts).

Common fixes:

• Ship modern media (AVIF/WEBP) and responsive images (srcset, sizes); lazy‑load below the fold.
• Minify/inline critical CSS; defer non‑critical JS; split bundles; reduce render‑blocking resources.
• Use HTTP/2 or HTTP/3 + TLS 1.3, Brotli compression, 103 Early Hints, CDN edge caching with proper cache keys.

Mobile UX & Responsive Readiness

• Viewport meta set; no horizontal scroll; tap targets ≥48px; labels for all form fields.
• Test on real devices (iOS Safari, Android Chrome) and emulators; verify cookie banners don’t block content.
• Check dark mode, color contrast, and zoom; avoid intrusive interstitials.

Structured Data & Rich Results

• Implement JSON‑LD per template: Organization, Website, Breadcrumb, Article/BlogPosting, Product/Offer/Review, FAQ, HowTo, LocalBusiness, VideoObject.
• Use @id to link entity nodes; add sameAs to official profiles; validate with Rich Results Test and Schema Markup Validator.
• Follow eligibility guidelines (e.g., Product requires offers/price, Review requires source transparency).

Accessibility & ADA/WCAG

• WCAG 2.2 AA checks: keyboard navigation, focus states, ARIA roles, form error messaging, alt text accuracy.
• Audit with Lighthouse Accessibility, axe DevTools, and manual screen reader testing (NVDA/VoiceOver).
• Remediate color contrast (≥4.5:1), heading order, skip links, and video captions/transcripts.

Security & Crawl‑Budget Stewardship

• Headers: HSTS, CSP, X‑Content‑Type‑Options, X‑Frame‑Options, Referrer‑Policy, Permissions‑Policy.
• Consistent 200/304 responses for unchanged assets; cache policy for images/CSS/JS set with sensible TTLs.
• Monitor 429/5xx spikes; rate‑limit bots that hammer non‑indexable paths.

International SEO

• Hreflang matrix: map language‑region pairs (e.g., en‑us, en‑gb, fr‑fr) with reciprocal tags and a valid x‑default.
• Consistent URL strategy (subfolders like /en‑us/ preferred for most, or ccTLDs for strong geo signals).
• Localize content, currency, and schema; avoid auto‑translate for primary money pages.
• CDN geo routing verified; don’t cloak content by IP.

On‑Page & Content Audit

Titles, Meta, Headers, URLs, Media

• Title tags: ≤580px width, include the primary topic early, unique per page; dynamic patterns tested for CTR.
• Meta descriptions: benefit‑led, ≤155 characters; avoid duplication; don’t stuff keywords.
• Headers: one H1; H2/H3 reflect search sub‑topics; include FAQ/PAA phrasing where relevant.
• URLs: short, readable, stable; use hyphens; avoid dates/IDs unless needed; enforce trailing slash convention.
• Media: descriptive file names, alt text for context (not stuffing), AVIF/WEBP, lazy‑load, and captions when helpful.

Content Quality, Thin/Duplicate, Cannibalization

• Thin content: merge or expand pages with no traffic/links; consider noindex for unavoidable low‑value pages.
• Duplicate/near‑duplicate: normalize case/trailing slashes/parameters; consolidate with canonicals or redirects.
• Cannibalization: map one primary intent per URL; consolidate overlapping posts; adjust internal anchors.
• Refreshes: update stats, screenshots, and examples quarterly or when SERPs shift; add datePublished/dateModified schema.

E‑E‑A‑T & Entity Signals

• Authors: real bios with credentials, LinkedIn, and expert review for YMYL topics; Author schema.
• Trust: clear About, Contact, editorial policy, and privacy pages; sitewide phone/address when relevant.
• Entity home: a canonical Organization page with Organization schema, sameAs to official profiles, Wikidata if applicable.
• Citations: link to primary sources; avoid vague claims; show methodology on studies and benchmarks.

Off‑Page Audit

Backlink Profile, Toxic Links, Lost Links, Opportunities

• Profile analysis: export referring domains, anchors, follow/nofollow ratio, topical relevance (Ahrefs/Majestic/Semrush + GSC).
• Toxic patterns: PBN footprints, spam anchors, hacked subdomains; request removals; use disavow cautiously for clear spam.
• Link loss: find 404 targets with links; 301 to the best match or restore content; reclaim unlinked brand mentions.
• Gap/opportunities: compare competitor link intersections; pitch expert contributions, data studies, tools, calculators, and PR.

Advanced SERP Features & AI Visibility

Featured Snippets & People Also Ask (PAA)

• Snippet formats: provide a 40–60 word definition, a step list, a comparison table, or a concise bulleted answer near the top.
• Use exact‑match question subheads and answer directly before elaborating; add FAQ schema where content truly is Q&A.
• Track: mark target queries; note snippet ownership weekly; test different answer framings.

AI Overviews/GEO readiness checks

• Topical coverage: build complete clusters with internal links; ensure each page answers a discrete intent.
• Factual grounding: cite primary sources; include clearfacts boxes and pros/cons to help summarizers.
• Entity clarity: consistent naming, Organization/Author schema, sameAs, and authoritative external profiles.
• Structure: scannable sections, short answers, step lists, and data points that LLMs can lift accurately.
• Measurement: document presence with scheduled SERP captures; monitor changes in CTR/impressions in GSC for affected queries; track “Overview present” via third‑party SERP features if available.

International & Local SEO Deep‑Dive

International SEO Validation

• Language intent mapping: keyword research per market; avoid one‑size‑fits‑all translations.
• Hreflang testing: validate with GSC International targeting reports and manual source checks.
• Localization: currencies, shipping, measurements, customer service availability, and localized FAQs.

Local SEO Audit

• Google Business Profile: accurate NAP, primary/secondary categories, services, products, booking links, UTM tagging.
• Listings: NAP consistency across top aggregators (Data Axle, Neustar Localeze, Foursquare, Apple Maps). Fix duplicates.
• On‑page local signals: city/service pages with unique content, schema LocalBusiness with geo coords, embedded map.
• Reviews: volume, velocity, responses; embed first‑party reviews (no schema for self‑serving per guidelines).

Prioritization & Roadmap

Impact/Effort Scoring (ICE/RICE) and 30/60/90 Plan

Use this lightweight scoring model to prioritize:

Scales: 1–10 for R/I/C; 1–10 for Effort (higher = harder). Sort by RICE score. For teams that prefer ICE, drop Reach and score Impact/Confidence/Effort.

Suggested 30/60/90:

• Days 1–30: P0 fixes—indexation errors, LCP/INP regressions, sitemap hygiene, critical schema, high‑impact content consolidations.
• Days 31–60: P1 fixes—IA improvements, internal links, local listings cleanup, snippet targeting, entity enhancements.
• Days 61–90: P2/Nice‑to‑haves—long‑tail content expansion, UX polish, advanced schema, experimental linkable assets.

Tracking & Cadence

Rank Tracking, Dashboards, Re‑Audit Schedule

• Weekly: core keyword ranks (mobile/desktop), snippet ownership, AI overview presence checks.
• Monthly: GA4 non‑brand traffic, conversion rate, assisted conversions, LCP/INP/CLS by template via CrUX.
• Quarterly: full recrawl, backlink profile refresh, content cannibalization audit, international/local checks.
• Dashboards: Looker Studio with GSC, GA4, CrUX, and rank tracker data; annotate releases in the change log.

Templates & Resources

• SEO audit tracker & RICE sheet: download
• Core Web Vitals remediation checklist: download
• Entity & schema starter pack (Organization/Person/FAQ): download
• GA4/GTM governance checklist: download

Sample Jira/Linear ticket template:

• Title: Fix LCP on Product Template to ≤2.5s (Mobile, 75th pct)
• Description: Optimize hero image (AVIF + srcset), preload critical font, defer non‑critical JS, enable Early Hints.
• Acceptance Criteria: PSI mobile LCP ≤2.5s (lab), CrUX LCP improves to ≤2.5s after 28 days; no CLS regressions.
• Owner/Reviewer: Eng + SEO; Attachments: before/after Lighthouse, code diff.
• QA Steps: device tests (iOS/Android), compare RUM dashboards, monitor error logs.

Verticalized Mini‑Checklists

Ecommerce:

• Product schema with Offer/Review, in‑stock signals; variant handling without index bloat.
• Faceted nav rules; image dimensions standardized; PDP LCP budget <2.5s.

SaaS:

• Feature/solution pages aligned to BOFU queries; comparison pages with structured pros/cons.
• Docs/help center indexability and internal search schema.

Publishers:

• Article/NewsArticle schema; Top Stories eligibility; author bylines and citations.
• Evergreen refresh program; strict cannibalization guardrails.

Marketplaces:

• Listing deduplication; user‑generated content moderation; LocalBusiness schema for vendors when relevant.
• Server‑side rendering for critical listing info; pagination controls.

Local/Service businesses:

• City/service pages with unique proof (photos, team, case studies); GBP posts/offers with UTMs.
• Local citations cleanup; review generation and response SOP.

Frequently Asked Questions

What is an SEO audit and why is it important?

An SEO audit is a systematic evaluation of your site’s technical health, content quality, user experience, and off‑page signals. It matters because it uncovers issues that block crawling/indexing, depress Core Web Vitals, dilute topical relevance, or waste link equity—so you can fix them and grow qualified organic traffic.

How often should I perform an SEO audit?

Run a light audit monthly (dashboards, crawl spot checks) and a full audit quarterly. Add an ad‑hoc audit after major releases, migrations, or ranking swings.

Which tools do I need for a comprehensive SEO audit?

Essentials: Google Search Console, GA4, a crawler (Screaming Frog/Sitebulb), PageSpeed Insights/Lighthouse, CrUX, a rank tracker, and a backlink tool (Ahrefs/Majestic/Semrush). Helpful: log analyzer, Looker Studio, axe DevTools, and schema validators.

How do I check if my site is being crawled and indexed properly?

Review GSC Coverage/Pages, test live URLs with the URL Inspection tool, analyze server logs for Googlebot hits, verify sitemaps only include 200/indexable URLs, and spot noindex/x‑robots conflicts. Crawl the site to find 3xx/4xx/5xx and orphan pages.

How can I improve Core Web Vitals and overall page speed?

Optimize LCP by reducing TTFB, compressing hero media (AVIF/WEBP) and preloading critical assets. Improve INP by splitting JS bundles, removing long tasks, and using passive listeners. Reduce CLS by reserving space for images/ads and using font‑display swap/optional. Validate changes in PSI and monitor CrUX field data.

How do I find and fix duplicate or thin content?

Use your crawler’s duplicate checks (titles, content similarity), align parameters/canonicals, and consolidate overlapping pages. For thin pages, expand with unique value or noindex/prune. Monitor changes in GSC queries per landing page to confirm consolidation success.

What steps are in a technical SEO audit vs. an on‑page/content audit?

Technical covers crawling/indexing, sitemaps, canonicals, status codes, site architecture, Core Web Vitals, mobile UX, structured data, security, and internationalization. On‑page/content covers titles/meta/headers/URLs/media, content depth, thin/duplicate/cannibalization fixes, internal links, and E‑E‑A‑T/entity signals.

How do I run a backlink audit and disavow toxic links?

Aggregate links from GSC and a link index; evaluate referring domain quality, anchors, and patterns. Outreach removals for obvious spam or hacked domains; disavow only when removal fails and the risk is clear. Reclaim lost links (404s to 301), and pursue quality placements via PR, data studies, and partner content.

How do I prioritize issues found during an audit?

Score each issue using RICE (Reach, Impact, Confidence, Effort). Tackle P0 blockers (indexation errors, severe Web Vitals, broken templates) first, then P1 improvements (IA, internal links, schema enhancements), followed by P2 optimizations. Build a 30/60/90 plan and track outcomes.

How long does an SEO audit take and what should the deliverables include?

Small sites: 1–2 weeks; mid‑market: 3–4 weeks; enterprise: 6–8+ weeks with log analysis and international scope. Deliverables: findings deck, prioritized backlog with RICE scores, annotated crawl/export files, measurement plan, dashboards, and implementation tickets with acceptance criteria.

Further reading

• Technical SEO foundations
• How to build content hubs that rank

Bottom line

A great SEO audit doesn’t drown you in spreadsheets—it turns findings into a punchy, prioritized roadmap you can ship. Use this 18‑step checklist, score issues with RICE, and track changes rigorously in GA4/GSC. When you’re ready to scale content production that matches search and AI intent, try our All‑in‑One AI Ebook Creator to build high‑quality, structured resources that win snippets and links.