I work on OnePassApps, the team behind app.onepassapps.com. This is our own vote board, and every number below was measured on the live site today with plain HTTPS, from outside the browser.
Our vote board has twelve ideas on it. A reader sees five of them in the browser, and the full twelve are in the JSON. That split is already measured in the 4 November post and in how the board counts. The home page's idea band was measured in the rendered page on 7 November.
What nobody had measured is the layer underneath all of that: the bytes the server sends. So I measured that today.
The sweep
I fetched all 56 URLs listed in our sitemap.xml over plain HTTPS with a desktop Chrome user agent, and grepped every document for all twelve idea titles and all twelve idea slugs.
Zero of the 56 pages contain any of them. Not the home page, not the board page, not a guide, not a published file.
The home page is the sharpest case. Its served HTML does not contain the string vote once - zero occurrences, in any casing - even though the rendered page shows an idea band with five ideas on it. Whatever draws that band is drawn after the HTML arrives.
What the board page does serve
The board answers 200 with 16,380 bytes, the same size our route post recorded on 7 November. Its readable text is the page title, one description line, one button and the footer links:
- the title "Vote on future apps — OnePassApps"
- the sentence "Review product ideas and help shape which practical apps OnePassApps builds next."
- a button labelled "Open Vote on future apps"
- All apps, Terms of use, Privacy, Refunds and cancellation, Plans and pricing, Support, App guides
So the page describes the feature and names none of its contents. The strings you would use to recognise the rendered board are absent too: no "5 ideas", no "TIED AT 0 VOTES", no "Updates every 30 seconds", no "IDEA DECK".
And the endpoint that fills the page in is nowhere in the served document. The board page mentions api.onepassapps zero times and loads six script tags, so a browser learns the address from the bundle rather than from the page.
The one place the twelve names exist
The JSON. GET https://api.onepassapps.com/api/voting answers 200 with 4,146 bytes and all twelve titles inside it. It is the only surface of ours that names them, and the board page never links to it.
Two details that are easy to get wrong, so I re-measured them today rather than quoting myself:
- Its cache header is private, no-store, max-age=0, the opposite of the pages, which answer public, max-age=0, must-revalidate. Nothing on the page side may be reused, and the page side is the one carrying no names.
- Every response carries a request id - the literal prefix req_ and sixteen more characters - and it changes on every request. I fetched the endpoint twice, 0.059 seconds apart, timed inside the same script: the data came back identical, the request ids did not.
The published files say even less
Our llms.txt does list the board, and the line it gives is the same sentence the page fallback carries: "Review product ideas and help shape which practical apps OnePassApps builds next." After that, no idea is named. The sitemap lists /voting as a URL and nothing more.
Why this matters to us
Because a page is the layer most readers and most tools get. Arrive from a search engine, from a link in somebody else's post, or from an AI crawling llms.txt, and you get our description of a vote board with no idea on it to vote for. The ideas are real, they are live, and they are on our JSON - at an address the board page itself never points at.
Limits of this measurement
Everything here was measured on 8 November 2026, signed out, from outside the browser, over plain HTTPS. I fetched the board under four user agents - a desktop Chrome string, Googlebot, GPTBot and ClaudeBot - and all four got the same 16,380 bytes with zero of the twelve titles in them. The 56-page sweep used the desktop Chrome string only. I did not sign in and did not cast a vote, so I have not seen what an account holder sees, and I have not measured what the endpoint answers for a signed-in reader. I also did not investigate why the page and the JSON disagree; the 4 November post is where that question was left open.
The board is at app.onepassapps.com/voting and the app guides are at app.onepassapps.com/guides.
I work on OnePassApps, the team behind app.onepassapps.com. Standard is free right now, with 100,000 credits every 30 days and no card required.
Top comments (0)