Start a Technical SEO Audit with Your Important Pages
Start with the homepage and important service, product, guide or contact templates. If you find a shared-template problem, inspect another page using it.
If a live page will not load, check HTTP first. If it is missing from search, inspect crawl, noindex and canonical settings. If it feels slow, distinguish loading, interaction and layout movement. Follow the instructions before choosing a result; leave unchecked tasks untested and inaccessible work blocked. Notes remain optional.
To prioritize technical findings alongside content and measurement issues, use the SEO audit checklist.
Fix Technical SEO Problems in Templates and Server Settings
Ask for the specific change at its source: “Remove the unintended noindex header from public service pages while retaining it on the thank-you page.” A page setting cannot override a conflicting server header.
For broad template changes, use a safe test environment before publication. Then inspect the public response and test important navigation and forms.
Handle Filters, Pagination and Language Versions When They Exist
Use these checks only when the feature exists.
Filters: inspect generated parameter URLs. Keep useful search landing pages and have the developer control unnecessary combinations. Do not block crawling while relying on Google to read noindex on the blocked page.
Pagination: give later results distinct URLs, such as /guides/?page=2, and crawlable links. Genuinely different results pages need their own canonical; a Load more button should not be the only discovery route.
Languages: annotate real equivalent versions with hreflang using supported language and optional region codes. Include each page itself and reciprocal references. Real English and French equivalents can use en and fr; do not invent regional pages to fill annotations.
For content and planning beyond these technical checks, continue with the website SEO checklist.
Correct a Canonical That Points to the Wrong Page
Imagine a distinct boiler-care guide declaring the homepage canonical because of a reused template default. Set the guide’s own full preferred address in its canonical field or template. Inspect published output and check related guides for the same mistake.
Align conflicting internal links and sitemap entries. Later compare Google’s selected canonical in URL Inspection; a live test cannot establish that its index has already changed.
Which focused checklist should you use for a crawl or indexing issue?
Choose the specialist workflow that matches the question you need to answer. Crawling a page and deciding whether it is eligible for indexing are different checks; a successful result in either does not guarantee a search listing.
When an important page is hard to discover or fetch, use the crawlability checklist to trace its links, access rules and server response.
Once a page can be fetched, use the indexability checklist to separate intended exclusions from eligibility problems and actual indexing observations.
For a suspected crawl-rule problem, follow the robots.txt checklist to compare representative URLs with the intended allow or block rules.
To review index and preview controls in HTML or HTTP headers, use the meta robots checklist and compare their combined effect with the page’s intended behavior.
To review which URLs belong in your sitemap, use the XML sitemap checklist to check canonical membership, timestamps and processing.
For duplicate pages or conflicting preferred-URL signals, follow the canonical tags checklist.
When an address moves or takes several hops, use the redirect audit checklist to test the mapping and final destination.
To compare what visitors see with the server response, follow the HTTP status code SEO checklist.
When a link leads to an error or the wrong content, use the broken link audit checklist to trace the referring page and choose a useful repair.
Before choosing a canonical or merging content, use the duplicate content audit checklist to classify which page groups are actually duplicates.
For a new path convention or a justified address change, use the URL structure SEO checklist to keep URLs stable, readable and consistent.
For a large or rapidly changing site with crawl delays or unnecessary URL expansion, use the crawl budget audit checklist.
To inspect verified crawler requests in your own server or CDN records, use the log file analysis SEO checklist.
When content or navigation depends on JavaScript, use the JavaScript SEO checklist to compare the delivered page with its rendered output.
Check Mobile Experience, Secure Delivery and Structured Data
After verifying access and indexing signals, use a focused workflow for the template or delivery problem you found. Mobile parity, field performance, resource optimization, HTTPS and structured data each need different evidence.
Use the Mobile SEO Checklist for mobile content parity, navigation, directives and usable layouts.
Use the Core Web Vitals Checklist for field performance and the causes of loading, interaction and layout instability.
Use the Page Speed SEO Checklist for critical resources, compression, caching, image and font delivery, lazy loading and rendering delays.
Use the HTTPS SEO Checklist for protocol redirects, mixed content, certificate access and canonical consistency.
Use the Structured Data Audit Checklist for markup accuracy, visible-content alignment, supported types and validation errors.