#OnePassApps

A measurement of the build-time HTML comments our own build writes into all 56 served pages: two marker pairs, seven or four comments per page, and the byte size of each marked region.

The served fallback copy on our 22 app pages carries 22 cost statements: 20 say "Yes, it is free" and two name your plan.

What app.onepassapps.com does with its support address across 56 pages: the email sits in the JSON-LD, the guide footers print it as plain text, and a clickable mailto appears on 4 screens.

The 56 pages we serve carry 308 accessible names and zero form controls: every field and button on app.onepassapps.com exists only after the bundle boots.

Every one of our 56 pages carries the same 27 meta names, one custom indexing tag, and two different names for the same app.

Comparing each of our 22 app pages with its guide twin: identical feature and limits blocks, one lifted answer, two element id sets, and the byte cost of the difference.

The OnePassApps vote board's own API returns twelve ideas with statuses and ranks. The public page renders five. A measured look at the difference.

What app.onepassapps.com tells search engines: 16 sitemap URLs, five robots.txt rules, a self-referencing canonical on every page, and the JSON-LD behind it.

What OnePassApps' link preview shows: one shared 1200x630 image, per-page Open Graph and Twitter card tags, and what is missing.

Full disclosure: I work on OnePassApps. A voice note, a podcast intro or a screen recording usually...