Key takeaways
- Compare status, canonical, robots directives, and sitemap inclusion together.
- Preserve useful search-performing pages before deciding to consolidate.
- Verify outcomes in Search Console instead of assuming submission means indexing.
Putting this workflow into practice? Explore Technical SEO & UX Audits for implementation scope, controls, and next steps.
Before publishing more articles, check whether search engines can reach and interpret the pages you already have. A useful technical SEO review follows a URL from discovery to its HTTP response, canonical declaration, rendered content, and internal links. It does not assume that a green plugin score means the page is indexed or earning traffic.
Build a small evidence table
Choose representative URLs: the homepage, one service, a category, a recent article, an older article receiving clicks, and a missing page. For each, record the final URL after redirects, status code, robots directive, canonical URL, title, H1, and sitemap inclusion. Inspect the HTML response as well as the browser-rendered page.
This catches contradictions that disappear when separate teams check separate tools. A page can be listed in the sitemap while declaring noindex, or receive internal links at one address while pointing its canonical at another. Investigate the reason before changing either setting.
Separate exclusion from canonicalisation
Noindex asks a search engine not to show the page in results. A canonical identifies the preferred representative of duplicate or closely similar content. They are not interchangeable tools. Google specifically advises against using noindex merely to influence canonical selection within a site.
If two tutorials answer different questions and both have search demand, improve their distinct usefulness rather than automatically consolidating them. If one page is genuinely replaced, review its traffic, links, and relevance before choosing a redirect. A broad redirect to an unrelated homepage is not a content repair.
- Inventory the affected URLs
- Check status and canonicals
- Verify rendered content
- Compare Search Console evidence
A visual map of this article’s approach. The detailed requirements and exceptions are explained in the surrounding sections.
Treat the sitemap as an inventory
A sitemap should describe the canonical pages you want discovered. Future-dated posts should enter it when they become public. Removed URLs and intentionally excluded duplicates should not remain simply because an old export still contains them. Google describes sitemap submission as a hint, not a guarantee of crawling or indexing.
Use lastmod for a meaningful page change. Rewriting every timestamp each morning makes the value less informative. For a scheduled article imported earlier, its public release can be later than its database creation time; discovery documents should reflect that reality without exposing the article prematurely.
Test the page without relying on JavaScript
Fetch the initial response and check for a useful title, description, canonical, and social preview metadata. Then check the rendered page for missing content or scripts that overwrite those values. Server-rendered metadata makes inspection easier and supports consumers that do not execute the site's JavaScript.
Do not treat every screenshot issue as a ranking diagnosis. Overlapping text and inaccessible controls are real usability problems, but their impact should be measured separately from whether the page is crawlable. Fix the interface and verify the technical signals rather than substituting one check for the other.
Track these separately. Evidence for one does not automatically confirm the others; use the article’s review and ownership checks.
Use Search Console to decide what happens next
Inspect the specific URL and compare Google's selected canonical with the declared one. Review exclusion reasons, queries, impressions, and clicks for comparable date ranges. A newly corrected page may need time to be crawled again. A page with impressions but few clicks needs a different investigation from a page Google has never discovered.
Record the deployment date and the exact URLs changed. That gives later performance reviews a useful baseline instead of an unsupported claim that SEO is "complete." For a practical review, share your website or request a website audit.
Primary references
- Google: canonicalisation methods
- Google: controlling indexing with noindex
- Google: building and submitting sitemaps
Frequently asked questions
What should a technical SEO evidence table contain?
For each important URL, record its response, indexability, canonical, sitemap presence and internal discovery path. Compare those signals before deciding whether the issue is exclusion, canonicalisation or usability.
Does inclusion in a sitemap guarantee Google indexing?
No. A sitemap helps discovery; the page still needs consistent access and indexing signals, useful content and crawlable links. Google makes the eventual indexing decision.
Related implementation guides
Founder, The Night Marketer (Shopify Select Partner). The agency has served 450+ brands since 2015.
Technical SEO & UX Audits
I review the technical and human path together: indexability, page structure, mobile layout, CTA clarity, tracking, and conversion friction.
