Last reviewed April 2026 by TheFreeSEOToolKit editorial workflow.

1. Check robots.txt

Make sure robots.txt exists, is accessible, and is not blocking important page paths by mistake. It should also reference your sitemap if possible.

2. Check whether key pages are indexable

Look for accidental noindex tags, blocked canonicals, login walls, or JavaScript-only rendering problems on pages you want in search results.

3. Review canonical tags

Each important page should normally self-canonicalize unless there is a genuine duplicate or preferred version elsewhere. Incorrect canonical tags can suppress pages from indexing.

4. Review status codes

Important pages should return 200 status codes. Broken pages, redirect chains, and unnecessary redirects make audits look worse and create crawl waste.

5. Check sitemap coverage

Your sitemap should include important pages and avoid low-value or broken URLs. A mismatch between sitemap URLs and indexable URLs is a common technical weakness.

6. Review internal linking

Important pages should be reachable through normal links, not only through search or isolated menus. Weak internal linking makes it harder for crawlers to discover and prioritize your content.

7. Confirm mobile viewport and responsive layout

Every key page should have a mobile viewport and work cleanly on smaller screens. Mobile usability remains a core technical baseline for search visibility.

8. Check page speed basics

Look for oversized images, excessive scripts, poor caching, and bloated assets. You do not need a perfect lighthouse score to rank, but obvious slowness hurts both users and audit quality.

9. Review heading and HTML structure

Technical SEO is not only server-side. A page with missing H1s, broken heading order, or messy structure can still underperform, especially when content is already thin.

10. Look for duplicate or near-duplicate pages

Multiple pages targeting the same intent can split relevance. If two pages overlap too closely, consolidate, retarget, or improve one clearly over the other.

11. Check image and asset handling

Meaningful images should have alt text, and all assets should load consistently without broken URLs or mixed-content problems.

12. Recheck after changes

A technical checklist only becomes useful when you rerun it after fixes. That second pass shows whether the site is actually cleaner or whether hidden issues remain.

How to use the checklist on a live site

Run the checklist against the homepage, one or two important commercial pages, and one supporting content page. That gives you a better picture than auditing a single URL in isolation. If the same issue appears across those pages, you are usually looking at a template or system-level problem rather than a one-off mistake.

This matters because technical SEO work can expand quickly. Grouping problems by template, page type, or system prevents you from fixing the same issue manually across dozens of URLs.

What to prioritise if the list is long

How technical findings connect to real outcomes

A technical audit is useful when it changes what happens in search. Cleaner canonicals can stabilise indexing. Better internal links can improve crawl discovery. Lighter pages can reduce friction for users. The checklist works best when each fix is tied to a real page outcome rather than treated as housekeeping for its own sake.