Technical SEO Checklist: A Prioritized Site Audit
A technical SEO checklist is useful only when it produces priorities. A site with a blocked homepage does not need a debate about image filenames. Start with issues that prevent discovery, access, rendering, indexation, or conversion, then move toward quality and maintainability.
Priority 1: access and indexation
Confirm the production host resolves, HTTPS works, important pages return 200, robots rules are intentional, meta robots directives are correct, canonicals resolve, and the site does not require scripts or cookies merely to expose public content.
Priority 2: architecture and URLs
Use stable descriptive URLs, shallow navigation for important pages, breadcrumbs where useful, clean internal links, consistent trailing-slash policy, and redirects for retired URLs. Find orphan pages and loops.
Priority 3: rendering
Inspect raw and rendered HTML. Verify headings, main copy, links, metadata, and structured data. Test client-side routes with direct loads and ensure missing routes return 404.
Priority 4: performance
Measure real-user and lab performance. Optimize server latency, main content resources, image delivery, script execution, layout stability, caching, fonts, and third-party tags.
Priority 5: page signals
Review unique titles, descriptions, H1s, language declarations, canonicals, hreflang where applicable, social metadata, and structured data. These should be generated from reliable page data.
Priority 6: operations
Automate checks in deployment. Monitor server errors, sitemap coverage, crawl behavior, template changes, broken links, redirect chains, expired certificates, and performance regressions.
Implementation checklist
- [ ] Production uses one preferred HTTPS hostname.
- [ ] Important pages return 200 and missing pages return 404/410.
- [ ] Robots.txt is intentional and tested.
- [ ] Indexable pages do not contain noindex.
- [ ] Canonical tags are unique and consistent.
- [ ] XML sitemaps contain preferred URLs only.
- [ ] Important pages have crawlable internal links.
- [ ] No major orphan pages exist.
- [ ] Redirect chains and loops are removed.
- [ ] Raw HTML contains essential public content.
- [ ] Client routes support direct navigation.
- [ ] Titles and descriptions are unique.
- [ ] Each page has a descriptive main heading.
- [ ] Images have dimensions and useful alternative text.
- [ ] Server response time is monitored.
- [ ] Critical CSS and main content load efficiently.
- [ ] JavaScript long tasks are reduced.
- [ ] Third-party scripts have owners.
- [ ] Structured data matches visible content.
- [ ] Hreflang is reciprocal where used.
- [ ] Security headers and HTTPS are configured.
- [ ] Broken links are monitored.
- [ ] Analytics excludes internal and bot noise where possible.
- [ ] Deployments include SEO regression tests.
- [ ] Major changes have rollback plans.
Frequently asked questions
How often should a technical audit run?
Run automated checks continuously and perform deeper reviews after migrations, redesigns, framework upgrades, or major traffic changes.
Should every warning be fixed?
No. Prioritize by user impact, indexation risk, scale, and business value.
Can a crawler replace manual review?
No. Crawlers find patterns; humans evaluate purpose, usability, and business context.
Turn the checklist into an action plan
A useful guide should end with a decision, not another browser tab. Run the site through Rofix, review the highest-impact findings first, and assign each fix to an owner. Re-run the audit after deployment so the team can verify that the issue is actually resolved rather than merely marked complete.