A technical SEO checklist should help a website owner identify real problems and assign useful work. It should not encourage changing production settings just to remove every warning from a crawler.
Use these 15 checks on representative pages: the homepage, a priority service, a product or article, a contact form and an important filtered or paginated route. Save evidence, record the affected template and make sure a responsible person can test any proposed fix.
1. Confirm the public response
Open the page without editor access and inspect its HTTP response. A genuine missing page should not silently return the homepage with a successful status. Test expected error routes as well as pages that work. Record redirects and their final destination before recommending changes.
2. Inspect crawling instructions
Check robots.txt for accidental restrictions on public content or assets needed for rendering. Crawling controls and index removal are different tasks. Robots.txt is not authentication and must not be used to protect private customer information. Use Google’s robots.txt guide when interpreting rules.
3. Check page-level indexing directives
Inspect the HTML and relevant response headers for noindex instructions. Compare the directive with the page’s purpose: staff previews and internal search pages may intentionally be excluded. Removing an intentional exclusion without understanding the route can expose unsuitable pages.
4. Follow canonical destinations
Check whether the canonical points to the page’s intended public version. Look for conflicting internal links, sitemap entries or redirects. A canonical is not a substitute for deciding which URL the business intends to maintain. Keep changes consistent with canonical guidance.
5. Review the XML sitemap
Inspect a sample of listed URLs and confirm that they are public, canonical and intended for indexing. Exclude drafts, private routes and redundant versions. A sitemap helps communicate URLs; it does not guarantee indexing. Dates should reflect genuine content changes rather than a daily refresh job.
6. Test discovery through internal links
Start at the homepage and find the priority service through normal navigation. Identify pages that require knowledge of the URL or depend entirely on an internal search form. A useful hierarchy should support a visitor as well as a crawler.
7. Compare initial and rendered content
Check whether important text and links are available reliably, including when a script fails. A page that depends on several fragile requests may work differently under other conditions. Do not remove necessary application scripts without testing the actual function they support.
8. Inspect duplicate URL patterns
Review parameters, trailing slashes, alternate hosts and campaign variants. Group patterns before acting; thousands of URLs may share one template issue. Avoid blanket redirects that discard a valid customer selection or move unrelated pages to the homepage.
9. Trace important redirects
Check old campaign and migration URLs, not just the current navigation. Remove unnecessary intermediate steps when safe. Confirm that a retired page points to a genuinely relevant replacement rather than a destination chosen only to avoid a 404.
10. Review structured data against visible facts
Parse JSON-LD and confirm that names, URLs and described content are accurate. Do not add invented reviews, ratings or office locations. Valid syntax alone does not establish eligibility for a rich result, and structured data should not contradict the page.
11. Check mobile task completion
Use a narrow viewport to read the page, open navigation and complete the non-sensitive parts of a form. Test long labels, error messages and sticky elements. A screenshot of the hero cannot establish that the enquiry journey works.
12. Diagnose performance with suitable evidence
Distinguish a repeatable laboratory test from field data. Record the page, device conditions and test date. A high score on one URL does not describe every template. The speed optimization guide explains how to prioritise loading, responsiveness and stability work.
13. Check image behaviour
Verify that images load, have suitable dimensions and do not move surrounding content unexpectedly. Important explanatory images need useful alternatives. Avoid lazy-loading the main above-the-fold image without considering its role in the page’s loading behaviour.
14. Review pagination and filters
Open later pages of a listing and test invalid page numbers. Check that useful items are not accessible only through an interaction the application cannot represent reliably. Decide intentionally which filter combinations deserve a public URL and which would create unnecessary duplication.
15. Verify the release and recovery plan
Test the public response after implementation. Recheck forms, authentication and important integrations affected by a template or caching change. Keep a backup and rollback responsibility clear. An audit issue is not closed because a ticket was marked complete.
Make the checklist actionable
For every finding, record the issue, affected pattern, evidence, impact, recommended change, owner and verification result. Prioritise broken access and failed customer tasks before minor housekeeping. If the diagnosis is uncertain, write down what evidence would resolve it.
Read what a sitemap does before treating sitemap submission as a fix for every indexing problem. SEO services can help organise the audit, while website development may be needed for implementation. Agree that boundary before work starts.