I work on OnePassApps, so this is our own documentation, and everything below was read from our own live pages on 7 November 2026 over plain HTTPS - no browser, no session, no cookies, signed out.
Two days ago this site shipped two guide pages and this account had a post describing them. There are now 22 guides, one for every live app route, and all 22 are the same page with different words. This post reads that template: the element ids, the on-page navigation, the section skeleton, the questions, the related-guide cards and the structured data we serve.
How this was measured
- One GET per URL over plain HTTPS with a desktop Chrome user agent. No JavaScript ran, so this is the HTML a crawler gets.
- The 22 guide URLs came out of sitemap.xml, which lists 56 URLs in total: 22
/apps/pages, 22/guides/pages, seven studio pages and five others (the home page, the vote, the plans page, the guides index and the terms). The guide slugs and the app slugs are the same 22 names. - Byte counts are the decompressed response body.
- The parser walked each page for element ids, heading levels, section elements, links and the JSON-LD graph.
Nothing here says what the pages look like, only what they contain.
The index
The index at /guides is 61,739 bytes and links to 22 guides. Its own filter reads "22 apps", and it carries 22 headings, one per guide.
Its "Before you start" note draws the line the guides then follow:
Browser-local tools process the files and details you choose in your tab. They are free, need no account and never use credits; export your work before leaving. Apps that use hosted services explain their account, permission and usage requirements in their guide; compare allowances on Plans .
Eleven ids, the same on every page
All 22 guides answer HTTP 200. They run from 26,582 bytes (NewsFlow) to 32,435 bytes (QR Code Maker) - 639,558 bytes in total.
Every one of them carries exactly the same 11 element ids, and nothing else:
onepassapps-structured-data, guide-content, features, features-heading, steps, steps-heading, limits, limits-heading, questions, questions-heading, related-heading
An earlier post on this site counted ten ids on the two guide pages that existed then. The eleventh is related-heading: a fifth section, Related guides, was added since.
The section skeleton is identical too, on all 22:
What you can do / How to use this app / Limits and privacy / Common questions / Related guides
The nav, and where it lands
The nav is the same on all 22 pages: "Skip to content", "Features", "Steps", "Limits and privacy", "Questions". It points at #guide-content, #features, #steps, #limits, #questions.
But the labels are not the headings they land on. "Features" lands on "What you can do", "Steps" on "How to use this app" and "Questions" on "Common questions". Only "Limits and privacy" matches its heading exactly.
Measured across all 22 guides and all 88 label-to-heading pairs, 22 of them match - one per page. That is the same mismatch the earlier post found on the two-guide version of this site; it now holds on every page.
There is also no nav link to the fifth section. The other four sections each carry a section id beside its heading id - features, steps, limits, questions - while Related guides has only the heading id, its section is labelled with aria-labelledby, and no #related anchor exists to point at.
67 questions, and still no FAQPage
Each guide carries a Common questions section. 21 of them answer three questions and MovieMatcherAI answers four - 67 question-and-answer pairs in all, and no two guides ask the same question.
Word Counter's guide asks "Are emoji and accented letters counted correctly?" and answers "Each emoji or accented character counts as one character." Its next pair is "Is my text sent anywhere?", answered "No. Counting happens in this tab. The TXT report holds the numbers only, not your text." Screen Recorder's guide asks "Which formats can I download?"
The hosted pair writes its own line differently. MovieMatcherAI's guide asks "Is MovieMatcherAI free, and does it use credits?" and answers "Browsing and title details are open without an account, and a free account adds the private Tracker, ratings, notes and reactions. Film analysis and fresh movie data look-ups run on our servers for your account and use credits from your plan's recurring allowance, which the Free plan includes. Plans compares the allowances."
That shape - a question and an answer per entry - is what schema.org's FAQPage type describes. The JSON-LD on every guide page is BreadcrumbList, ContactPoint, ListItem, Organization, WebApplication, WebPage, WebSite, and there is no FAQPage node on any of the 22 guides, on the index, or on any of the 22 app pages. I am not claiming how any search engine treats that; it is a statement about the markup we serve.
The credits line marks the hosted apps
20 of the 22 guides contain the sentence "never uses OnePassApps credits". The 2 that do not are MovieMatcherAI and NewsFlow - the two apps that use hosted services rather than processing files in the tab.
So the documentation marks the split itself, and the index says the same thing: browser-local tools "never use credits", while hosted apps explain their account, permission and usage requirements.
Related guides
Every guide ends with a Related guides section. 17 of them list two other tools and 5 list one. Each card links twice: to the other tool's guide and to that tool's app page.
What I did not measure
No browser was opened, so nothing here describes how the pages look. I did not run any app, produce any export, or test how a search engine reads these questions. These are one fetch of each URL on one build on 7 November 2026, so treat the byte counts as a snapshot.
I work on OnePassApps, and this is our own documentation. The 22 guides are at the app guides, and the app behind the questions quoted above is the Word Counter.
Top comments (0)