Start with the pages that matter
Write down the pages that earn leads, sales, or a return visit. Include a representative URL from each template: your homepage, a category, a product or service, and an article. A small, deliberate sample helps you understand what a crawler later finds at scale.
Record the audit date, the crawl settings, and recent releases. Keep a baseline so your next audit can distinguish old issues from new ones.
Check access before polishing metadata
Open the page as a visitor, inspect its HTTP status, and check whether the main content appears in the rendered page. Review robots.txt separately from a page’s indexing directives. A disallowed URL and a noindex page have different meanings.
Use Search Console’s URL Inspection for your verified site to compare your expectation with Google’s reported state. A successful live test alone is not proof that a URL is indexed.
- Check for accidental authentication, blocked assets, and production noindex directives.
- Confirm important internal links use normal, crawlable anchor elements.
- Investigate redirect loops, broken links, and server errors before minor copy changes.
Choose the URL you want people to find
Check that each important page has a sensible canonical URL. Look at redirects, sitemap entries, and internal links together: they should consistently point toward the intended version. Avoid sending every page of a category to page one as its canonical.
Review filtered and sorted URLs. If a combination does not offer a distinct, useful landing page, keep it out of your sitemap and avoid building an unlimited network of crawlable filter links.
Improve the template, then verify the result
Group findings by their cause. Fixing one template that emits missing titles or broken navigation can improve many URLs. Prioritize by affected pages, business importance, confidence, and effort.
After a deployment, inspect the rendered HTML and rerun the same crawl configuration. Use PageSpeed Insights for performance diagnostics, remembering that a lab score and real-user data describe different things. Document what changed and what still needs attention.
Keep an audit rhythm
For an actively changing site, check important templates after releases and compare recurring crawls. DIYSEOHub is our own tool and our recommended starting point for a public technical report. Use the findings as a work list, then validate the important fixes yourself.
A technical score does not measure whether your writing is accurate, your offer is useful, or your business deserves to rank. Pair it with search performance, user behavior, and content review.