A sitemap is a declaration of the public pages a site wants search engines to discover. Its lastmod field is useful only when it reflects a meaningful public change—not every deploy, footer edit, or generated timestamp.
Put only intentional public pages in the sitemap
Inpages.me builds the sitemap from public routes such as the blog and Engineering Notes. Authenticated routes, private Memories, and technical endpoints do not enter it merely because they are routable. A sitemap is a public editorial choice, not an inventory of every controller action.
Google likewise recommends including the URLs you want to appear in Search, rather than every technically reachable URL, in its sitemap documentation.
Make sitemap, canonical, and rendered page agree
Each Engineering Note renders a canonical URL, Article metadata, and a sitemap entry for the same public address. Aligning these signals makes the intended owner of a piece of content clear without treating any one signal as a ranking guarantee.
Pagination, filtered archives, and duplicate parameter URLs need their own canonical rules rather than a silent sitemap inclusion.
Update lastmod only for a substantive change
Inpages.me tracks an editorial modified_at value and uses it for sitemap lastmod when present. A new primary section, a materially changed technical statement, structured-data update, or intentional internal-link change can justify it. A build timestamp or footer change does not.
Google’s guidance is similarly specific: lastmod should reflect a significant visible change and stay consistently accurate. It is not a request to recrawl unchanged pages on demand.
Keep public visibility separate from search eligibility
A shareable page and an indexable page are different product decisions. Inpages.me evaluates public-search eligibility separately and revokes that eligibility when relevant public writing changes. Protected Memories cannot be published, and private writing is never used as search material.
The product-level model is documented in private and public content trust boundaries.
Test the exclusion rules as carefully as inclusion
Focused tests cover sitemap inclusion for intended public pages, canonical URLs, Article metadata, robots rules, and exclusions for private or protected content. A test that only asserts “the sitemap has URLs” misses the privacy boundary that makes the sitemap trustworthy.
Treat an editorial revision as a technical change
Before publishing or substantially revising a note, check its canonical URL, title, description, structured data, inbound links, outbound links, and modification date. This note belongs beside account-scoped data exports and privacy-safe Rails logging: public discovery should not quietly expand a private-data boundary.