The sitemap

One generated index of the canonical marketing pages, the whole feature engine, every system page and every published post — built from the same source the engine pings read.

What it is

A generated sitemap combining the canonical page list with its per-page priorities, the feature explorer, every system page, every individual feature page, and every published post with its last-modified date. Feature pages carry different priorities by depth; systems outrank individual features.

Also called: sitemap.xml · site index · page list for google

See it
The sitemap
Area
Integrations
Group
Search engine plumbing
System
Marketing Site
Solves
2 named problems
01SITE_PAGES supplies the canonical routes and their priorities.
02The feature registry and the systems list supply their own routes.
03Published posts are appended with their updated timestamp as lastModified.
The URL set broken down by source — canonical pages, feature pages, system pages, posts — with counts. Sample data — no customer information appears here.
How it works
  1. 1SITE_PAGES supplies the canonical routes and their priorities.
  2. 2The feature registry and the systems list supply their own routes.
  3. 3Published posts are appended with their updated timestamp as lastModified.
  4. 4liveSiteUrls() builds the same set for change detection and the IndexNow ping, so the sitemap and the announcements can never disagree.
  5. 5The route is on the public middleware allowlist.
Why we built it

The canonical list exists so "the Pages tab, /sitemap.xml, and the search-engine pings all read THIS list — add a page here and every surface knows about it." Including the feature engine is argued explicitly: "The feature pages are the largest surface on the site by a wide margin and the one most likely to be found by someone searching their problem rather than our product name, so leaving them out of the sitemap would waste the best-matching pages we have."

The problem
  • Different surfaces had different ideas of what pages existed.
  • The largest and best-matching page set was not being submitted.
Sound familiar?
What you get
One list feeds the sitemap, the change hash and the engine pings
Every feature and system page is submitted, not just the marketing shell
Posts carry their real last-modified date

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →