The 55 of 56: What Our Sitemap and Our llms.txt Agree On, and the One URL Only One of Them Names

Disclosure first: I work on OnePassApps, the team behind app.onepassapps.com. This is a measurement of our own two machine-readable files, not of someone else's site.

Two files on our site describe the same site to a machine. There is the XML sitemap a crawler fetches by convention, and there is the llms.txt we publish for AI tools. On 8 November 2026 I fetched both with plain HTTPS - no browser, no session, no cookies and no JavaScript - and compared the two sets of URLs as they actually stand today.

The two files

https://app.onepassapps.com/sitemap.xml answers 200 with 4,046 bytes and 56 <url> entries. Every one of the 56 entries carries a <loc> and nothing else: 56 of 56 have no <lastmod>, no <priority> and no <changefreq>.

https://app.onepassapps.com/llms.txt answers 200 with 17,965 bytes, eight heading lines and 55 links. All 55 are distinct.

What they agree on

Every URL in llms.txt is in the sitemap. The two files share 55 URLs, and llms.txt contributes nothing the sitemap has not already listed.

The order matches too. The 22 app paths, the 22 guide paths and the 7 studio paths appear in identical order in the sitemap and in llms.txt, in all three groups.

The one URL they differ on

The home page. The sitemap lists https://app.onepassapps.com/ as its first entry, and llms.txt does not link it anywhere. All 55 of its links carry a path, and there is no bare mention of the origin without one - so llms.txt never hands a reader the front door of the site, even though its first line is the title and its second line is the summary.

Three sections of llms.txt with no links at all

llms.txt has seven sections. Four of them carry links: Live apps has 22, App guides has 23, Browser-local Studios has 7 and Platform information has 3. The other three carry prose only, not a single link: Access and cost (23 bullets), Plans and prices (3 bullets) and Terms of use sections (12 bullets).

App guides is worth a note because its 23 links are not 23 guides. They are the guides index plus the 22 guide pages.

What neither file gives a reader: the support page

Our support page answers 200 but appears in neither file - I wrote on 4 November that it is not in the sitemap, and llms.txt does not list it either. llms.txt does carry the support address, in plain text rather than as a link:

• Support contact: info@onepassapps.com

So the address is there and the page is not.

The caching side, briefly

Both files carry an ETag, and both answer with public, max-age=0, must-revalidate. robots.txt is 160 bytes with public, max-age=14400, must-revalidate, and it names only the sitemap - it has never mentioned llms.txt. The home page HTML does not mention it either.

Limits, so nobody reads more into this than it says

One build, one GET per URL, 8 November 2026, plain HTTPS from one network, with no browser, no session, no cookies and no JavaScript. Both link sets are a snapshot of one build. I did not test how any crawler or AI tool reads either file - this is a comparison of what the files contain, not a claim about what a reader does with them. The order comparison is between the two files as served today, not a claim about how either is generated. And the set relation I measured today did not exist in this shape on 4 November: I first wrote about llms.txt then, when it was 6065 bytes, 7 sections, 15 entries, against a 16-URL sitemap.

That earlier post is here: https://dev.to/onepassapps/what-apponepassappscom-tells-ai-tools-a-measured-look-at-our-llmstxt-2lko

And the sitemap and robots.txt, measured on the same day: https://dev.to/onepassapps/the-onepassapps-sitemap-and-robotstxt-16-public-urls-every-canonical-and-the-json-ld-behind-them-4f81

https://app.onepassapps.com/?utm_source=devto&utm_medium=post&utm_campaign=llms-sitemap-set&utm_content=site-link
https://app.onepassapps.com/guides?utm_source=devto&utm_medium=post&utm_campaign=llms-sitemap-set&utm_content=guides-link