Published September 1, 2026.
A new article is incomplete when its route exists but readers cannot discover it from the intended collection. This coverage check connects content files to the public Blog or Research index and the appropriate sitemap.
Identify required surfaces
Before release, name the article family, collection route, expected sort position, pagination behavior, and sitemap. A blog guide belongs on /blog; a source-led study belongs on /research. Avoid relying on a generic fallback that masks a missing record.
Test the built navigation
Open the collection and follow its link to the article. Verify the card title, description, category or cluster, date, and destination. Repeat at narrow viewport widths so wrapping and pagination do not hide access.
| Surface | Required observation | | --- | --- | | Collection | Unique title and direct link | | Article | Direct response and self-canonical | | Sitemap | One matching location | | Navigation | Usable keyboard focus and label |
Separate discoverability from indexing
An index-page link and sitemap entry make the route discoverable; they do not prove a search engine has indexed it. Report only the evidence collected. Search indexing is a later observation with its own timing and tools.
Combine this check with the rendered-page QA routine and Google’s sitemap guidance.
Frequently asked questions
Is a sitemap entry enough?
No. The correct collection should also link to the page so readers and crawlers can reach it through the site structure.
What if the article falls onto page two?
Test the actual pagination path and confirm the collection still exposes a crawlable link without relying on client-only state.