Make the public route inventory explicit
Technical SEO starts with deciding which pages should exist. List the homepage, services, cases, articles and utility pages. Give each public page a distinct purpose; keep authentication, private workspaces and draft reports outside the indexable set.
Use the same route inventory for generation, metadata and validation. Separate lists tend to drift: a page may exist in navigation but be absent from the sitemap, or the sitemap may advertise a route that returns a generic shell.
Inspect the returned HTML
Open the built page with JavaScript unavailable or inspect the document response. A crawler should receive the meaningful title, description, main heading and public content. For a static blog, published database records can be fetched during the build and rendered into article HTML.
| Check | Expected result |
|---|---|
| Canonical | One absolute URL matching the preferred public route |
| Main heading | One meaningful H1 for this page |
| Robots | Indexable content allowed; private or empty utility output handled deliberately |
| Structured data | Describes visible facts and real authorship |
| Social card | Fetchable image with correct format and dimensions |
| Missing route | A real not-found response rather than a successful empty app shell |
Structured data is an aid to interpretation, not a guarantee of a search feature. Google’s Article documentation describes supported article properties; use real publication dates and author information.
Validate links and discovery
Check that every important page is reachable from an ordinary anchor. A sitemap helps discovery but does not replace navigation. Exclude drafts and private URLs. After URL changes, test the redirect target and avoid redirect chains.
For a multilingual site, use only real translated variants and reciprocal language references. Do not reuse the same article body behind fifteen language URLs.
Launch with evidence
Save the build report and test representative routes on the deployed host, including unknown URLs. Configure the real domain before submitting the sitemap to search services. Search visibility and rankings require subsequent observation; a passing build cannot promise them.
Explore SEO and performance alongside the content and delivery architecture, rather than adding metadata at the end.
A practical question
Does a valid sitemap guarantee indexing?
No. It is a discovery signal. The returned content, robots directives, canonical relationships and search-engine decisions still matter. Inspect actual deployed pages after the release.