SiteAuditLint checklist library
What this checklist covers
An SEO QA checklist gives developers and QA teams a pre and post deployment test plan for status codes, redirects, canonicals, robots directives, metadata, headings, internal links, structured data, sitemaps, and rendered content.
It is organized into 15 sections: Before Deployment, HTTP Status, Redirects, Canonicals, Robots Directives, Titles and Meta, Headings, Internal Links, Structured Data, XML Sitemap, JavaScript Content, Tracking, AI Crawler Access, Regression Checks and Sign-off. Each check lists exactly what to verify and a priority, so you can work through the highest impact items first.
For background on the concepts behind these checks, see SEO testing course, SEO testing guide, Linear SEO tickets.
Testing method: This checklist is the list of release checks. For how to run them, see SEO QA, pre-deployment SEO testing and post-deployment SEO testing.
Who it is for:
Download the seo qa checklist
Use the interactive version below, or download it to share with your team, attach to tickets, or work through offline.
SEO QA Checklist
Work through each check
0 of 16 checks complete
Before Deployment
HTTP Status
Redirects
Canonicals
Robots Directives
Titles and Meta
Headings
Internal Links
Structured Data
XML Sitemap
JavaScript Content
Tracking
AI Crawler Access
Regression Checks
Sign-off
Progress is saved in this browser only.
Detailed explanations
Each section below explains what to check, why it matters, the problems you will usually find, how to fix them, and how to confirm the fix.
Before Deployment
What to check:
- Crawl staging build. No new critical errors against baseline.
Why it matters: Launches often ship staging settings to production. A single forgotten noindex or Disallow can keep a new site out of search for weeks.
Common problems:
- Staging noindex left on production
- Robots.txt still disallowing everything
- Canonicals pointing to the staging domain
- Analytics not installed
How to fix it: Use a launch runbook that removes staging protections, swaps domains in canonicals and sitemaps, and verifies tracking.
How to verify: Crawl production immediately after launch and compare against the final staging crawl.
Learn more: Pre-launch website checklist, Run your first audit, Noindex issues.
How SiteAuditLint helps: it checks before deployment across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
HTTP Status
On this checklist: check status codes. Explained in full in the Technical SEO Checklist.
Redirects
On this checklist: check redirects. Explained in full in the Technical SEO Checklist.
Canonicals
On this checklist: check canonicals. Explained in full in the Indexability Checklist.
Robots Directives
On this checklist: check meta robots; check robots.txt. Explained in full in the Robots.txt Checklist.
Titles and Meta
On this checklist: check titles and descriptions. Explained in full in the On-Page SEO Checklist.
Headings
On this checklist: check H1s. Explained in full in the On-Page SEO Checklist.
Internal Links
On this checklist: check internal links. Explained in full in the On-Page SEO Checklist.
Structured Data
On this checklist: check schema. Explained in full in the On-Page SEO Checklist.
XML Sitemap
On this checklist: check sitemap. Explained in full in the Technical SEO Checklist.
JavaScript Content
On this checklist: check rendered content. Explained in full in the JavaScript SEO Checklist.
Tracking
What to check:
- Check analytics. Tracking fires after deploy.
Why it matters: Without tracking you cannot measure the impact of launches, migrations, or fixes. Missing tags after a deployment create gaps that cannot be backfilled.
Common problems:
- Analytics missing on new templates
- Duplicate tags inflating sessions
- Conversion events lost after a redesign
- Search Console not verified on the new domain
How to fix it: Deploy analytics through a tag manager across all templates, verify Search Console, and test conversion events before launch.
How to verify: Use tag assistant and real time reports to confirm tags fire on each template and that conversions record.
Learn more: Tracking and analytics audit, Tracking pixel audit, Tracking missing on page issue, SEO KPIs lesson.
How SiteAuditLint helps: it checks tracking across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
AI Crawler Access
On this checklist: check AI crawler rules. Explained in full in the Technical SEO Checklist.
Regression Checks
What to check:
- Compare to previous crawl. Diff reviewed and unexpected changes investigated.
Why it matters: Comparing crawls before and after a change is the only reliable way to catch regressions. Many SEO problems are invisible on a single page but obvious in a diff across thousands of URLs.
Common problems:
- Changes to titles, canonicals, or noindex hidden in a release
- Removed internal links reducing link equity to key pages
- URL count changes nobody intended
- Schema dropped from a template
How to fix it: Keep a baseline crawl, compare every new crawl against it, and investigate every unexpected change before it reaches production or within hours of release.
How to verify: Run a crawl comparison report and review changes by field: status, indexability, canonical, title, H1, links, and schema.
Learn more: Audit comparison, SEO testing guide, Scheduled SEO audits.
How SiteAuditLint helps: it checks regression checks across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Sign-off
What to check:
- Approve release. QA owner signs off.
Why it matters: A checklist is only useful if findings are prioritized, assigned, and verified. Process steps turn a list of issues into fixed issues.
Common problems:
- Findings without owners or deadlines
- Low impact issues fixed before critical ones
- Fixes never verified with a re-crawl
- No record of what changed and why
How to fix it: Score each issue by impact and affected URL count, assign an owner, and require a verification crawl before closing.
How to verify: Re-crawl after fixes and confirm the issue count for each item has dropped to zero or an accepted level.
Learn more: Audit process lesson, Prioritization lesson, SEO audit prioritization, How to report technical SEO issues.
How SiteAuditLint helps: it checks sign-off across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Common mistakes
Testing only one URL per template
Missing header level changes like X-Robots-Tag
Not comparing against a baseline crawl
Treating SEO QA as a post launch task
When to run the checklist
- Before every production release
- After deployments that touch templates, routing, or headers
- After CMS or plugin updates
- During sprint review
How to verify fixes
Save a baseline crawl before you change anything. Fix high-priority and template-level issues first, since one template fix resolves many URLs, then re-crawl with the same start URL and settings and compare the two audits with audit comparison. Finally, confirm important pages in Search Console with URL Inspection. See how to prioritize audit findings.
SiteAuditLint workflow
Most checks in this list run automatically in a SiteAuditLint crawl. Use audit comparison to diff crawls and scheduled audits to monitor for regressions.
All SEO checklists
See the full checklist library, with a guide to choosing the right checklist for each job.