I work on OnePassApps, the team behind app.onepassapps.com. This is about our own site, and every number below was measured on 8 November 2026 with plain HTTPS from one network: no browser, no session, no cookies and no JavaScript.
There is a hand-set order of our 22 apps. It shows up in more than one place, and this post is about the places where it shows up, the places where it does not, and one pairing rule nobody had written down.
An earlier post on this site compared our sitemap and our llms.txt as two sets and said the order inside the three groups matches. This post goes one level out: it compares the order of the groups themselves, and it brings in the guides index page, which that post did not read.
The order inside a group is the same everywhere
Take the 22 app slugs. newsflow, movie-tracker, paperkit, cv-builder, email-signature, chart-maker, subtitle-workbench, teleprompter, screen-planner, label-maker, social-card, citation-formatter, calendar-maker, password-generator, word-counter, focus-timer, qr-code-maker, ambient-noise-mixer, time-zone-planner, invoice-maker, signature-maker, screen-recorder.
That exact sequence appears, in that exact order, in four places:
- the 22 app paths in sitemap.xml
- the 22 links in the "Live apps" section of llms.txt
- the 22 entries of the "OnePassApps apps" ItemList in the home page's JSON-LD
- the 22 guide links on the guides index page, https://app.onepassapps.com/guides
The guides index is the one that surprised me. It lists its guides in guide order, not app order, so I expected a different sequence. It does not: the 22 guide links it writes are in the same order as the 22 apps, and it also carries 22 links back to the app pages, in that same order. The index answers 200 with 61,739 bytes.
The order of the groups is not the same everywhere
This is the part the earlier post did not look at. Our sitemap lists its 56 URLs in this order, by group:
- five non-tool URLs, positions 1 to 5
- seven studio paths, positions 6 to 12
- 22 app paths, positions 13 to 34
- 22 guide paths, positions 35 to 56
Our llms.txt lists the same 56 URLs' worth of content in a different group order. It has seven sections and four of them carry links: "Live apps" with 22, "App guides" with 23, "Browser-local Studios" with 7 and "Platform information" with 3. Read in order, that puts the apps first, then the guides, then the studios, then the platform links.
So the studios come before the apps in the sitemap, and after the guides in llms.txt. The same seven paths, in the same order within the group, filed under different neighbours.
The three platform links make it sharper, because there are only three of them and they are in a different order too. The sitemap's five non-tool URLs are the home page, the vote board, the plans page, the guides index and the terms page, in that order. llms.txt carries three of those five as links - the plans page, the terms page and the vote board - and it lists them in that order. Take the three that appear in both and compare: the sitemap says voting, plans, terms; llms.txt says plans, terms, voting. One is the other's rotation by a single step.
Every guide sits exactly 22 places after its app
The sitemap's structure is regular in a way that is worth stating plainly. For all 22 apps, the guide for that app is exactly 22 positions later in the same file, and the guide's slug is the app's slug.
Concretely: newsflow is at position 13 and its guide is at position 35. screen-recorder is at position 34 and its guide is at position 56. Every pair, 22 apart, and the two URLs differ only in the segment in the middle - /apps/ against /guides/.
So you can take any position in the app block, add 22, and you are holding that app's guide. There is no exception in the 22, and no guide whose slug does not match the app above it 22 places earlier.
The home page's structured data uses the same list twice over
The home page carries one JSON-LD block whose @graph holds five entries: Organization, WebSite, WebApplication, and two ItemLists. One is named "OnePassApps apps" and holds 22 entries. The other is named "OnePassApps browser-local Studios" and holds 7. The 22-item list is the same sequence as the sitemap's app block and the llms.txt "Live apps" section, and the 7-item list is the same sequence as the studio block in both files.
The JSON-LD and the two text files therefore agree on a single order for the apps and a single order for the studios. The only place where the order of a group is a choice rather than a copy is the sitemap against llms.txt.
What this is
One sequence, written once, read out in four places - and then the same groups assembled in a different sequence in two of them.
It is worth measuring because the obvious assumption is that a sitemap and an llms.txt listing the same pages will present them the same way. Ours does not: the studios move from before the apps to after the guides, and the three platform links rotate by one.
Limits
One build, one GET per URL, 8 November 2026, plain HTTPS from one network, with no browser, no session, no cookies and no JavaScript. The sitemap answers 200 with 4,046 bytes and 56 locations; llms.txt answers 200 with 17,956 bytes and 55 links. Both are a snapshot of one build, so a later build may reorder them. I did not test how any crawler or AI tool reads either file, and I am not claiming that one order is better than the other - the page does not say which was written first, and from the outside there is no way to tell. The order of the visible home page cards is not part of this post.
The site link below is the home page; the second link is the guides index, which is where the 22-guide sequence can be read directly.
I work on OnePassApps.
Top comments (0)