What a Competitor's Sitemap Leaks Before They Announce

Almost every SaaS company publishes a sitemap.xml at the root of its domain. It exists for search engines: a machine-readable list of every URL the company wants Google to crawl and index. Nobody writes it by hand for humans, and almost nobody on the marketing team thinks of it as a public document. That's exactly why it's worth reading. The sitemap routinely lists pages that exist and are crawlable but aren't linked anywhere in the site's navigation yet — which means it leaks launches before the launch.

The sitemap is a complete page inventory, not a curated one

A homepage shows you what a competitor wants you to see this week. The sitemap shows you everything their CMS knows about. Most sitemaps are generated automatically from the content system, so a page goes into the sitemap the moment it's published — even if it's not yet in the header, the footer, or any internal link. The marketing team is thinking about the launch announcement; the sitemap already shipped the URL.

Open competitor.com/sitemap.xml (or /sitemap_index.xml, which often points to several child sitemaps split by content type). You'll usually find blog posts, feature pages, comparison pages, integration pages, and landing pages all enumerated with <loc> URLs. Read the URL slugs. They're written by people who assumed only a crawler would ever see them, so they're honest.

New URLs appear before they're linked in navigation

The single most useful move is to compare today's sitemap against last month's and look at what's new. A URL like /features/sso or /solutions/healthcare or /compare/competitor-vs-you appearing in the sitemap — when there's no nav link to it yet — is a page that's built, staged, and waiting for a launch moment.

That gap between "in the sitemap" and "linked in the nav" is your lead time. A new /solutions/<vertical> slug means they're building a vertical motion. A new /compare/<name> slug tells you exactly who they've decided to position against — sometimes you, sometimes a rival you didn't know they cared about. A cluster of new /integrations/<tool> slugs is the same ICP-movement signal you'd read off the integrations page, except you see it before the logos go live.

lastmod timestamps tell you what's actively being worked

Many sitemaps include a <lastmod> field next to each URL — the date the page last changed. Sort the sitemap by lastmod and the most recently edited pages float to the top. That's a near-real-time map of where the competitor's content and product effort is going right now.

If their pricing page, enterprise page, and security page all have lastmod dates within the same recent week, something coordinated is happening — likely an upmarket push. A burst of edits across /docs/* is the same engineering-honest signal you'd get from watching their docs and API reference. The timestamps turn a static list into a heat map of attention.

Disappeared URLs mark quiet retreats

Pages that drop out of the sitemap between visits are as informative as new ones. When a competitor removes a feature page, a vertical landing page, or a whole product section from their sitemap, they've usually decided to stop investing in or indexing that motion. It's the same kind of quiet retreat you can confirm with Wayback pricing archaeology — except the sitemap flags the removal at the structural level, often before the page actually 404s.

A vertical they pulled out of is frequently an opening for you. A deprecated product area they stopped indexing tells you where their roadmap is not going, which is just as useful as where it is.

How Seeto handles this

A sitemap can hold hundreds or thousands of URLs, and the meaningful change is one new slug buried in the middle — the kind of tedious-by-hand diffing nobody does on a schedule. Seeto treats the sitemap as a monitored surface, so newly added URLs, removed URLs, and shifting lastmod clusters surface as discrete change events on the same cadence as the homepage and pricing. It doesn't guess what an unannounced page means — it just makes sure the new /compare/you slug lands in front of you the week it appears, instead of the week the competitor decides to tell the market about it. Reading the implication is still your job; not missing it is the part that's automated.

The two-minute version

For each of your top three competitors, once a month:

1. Open competitor.com/sitemap.xml (try /sitemap_index.xml too) and scan the URL slugs for anything new since last month — especially /compare/*, /solutions/*, /features/*, and /integrations/* pages that aren't linked in their nav yet.
2. If the sitemap exposes lastmod dates, sort by them and note which pages were edited most recently — that cluster is where their effort is going, and it often precedes a positioning shift by a quarter.