I work on OnePassApps, so this is our own site, and every number below was measured over plain HTTPS on 9 November 2026 - one GET per URL, no session, no cookies, no JavaScript - with a real HTML parser rather than a regex.
We have already published the head of these pages (the link-element layer, 491 link tags) and the graph between our guide pages (39 directed edges). This post is the layer in between: the anchors themselves - what the links say, where they point, and how often the same words come back.
The counts
All 56 URLs in our sitemap answer HTTP 200. Between them they carry 1,058 anchors, and those anchors use 162 different link texts.
The per-page anchor count is not spread evenly. There are eight page shapes:
- 63 anchors on /terms - one page
- 61 on the home page - one page
- 58 on /guides - one page
- 25 on 17 of the 22 guide pages
- 23 on the other 5 guide pages
- 14 on /plans - one page
- 11 on all 22 app pages
- 10 on the remaining 8 pages (/voting and the seven studios)
One footer, repeated on all 56 pages
Four link texts appear on every single page of the site: "Terms of use", "Privacy", "Refunds and cancellation" and "Plans and pricing" - 56 times each, 224 anchors in all.
"App guides" appears 101 times across all 56 pages, because it sits in the header and again in the footer. "Skip to content" appears on 23 pages, the guides. "Reload" and "All apps" appear on 33 pages each - the pages that ship the app bundle.
One link text, 22 destinations
On the home page the same phrase - "Read the guide" - appears 22 times, and each of those 22 links points at a different guide: 22 distinct destinations, one page.
That is the only place in our own navigation where one phrase is not one destination.
The same destination, written two ways
22 of our link texts are written twice with two different hrefs for the same page. On /guides they are relative, such as /apps/newsflow, and on the app pages themselves the same 22 phrases are absolute, such as https://app.onepassapps.com/apps/newsflow.
A browser ends up in the same place either way. The difference is in the HTML we serve.
The address, rewritten
No served document contains a mailto: link. The contact address is rewritten into 74 anchors whose href is /cdn-cgi/l/email-protection with a hex fragment - 44 distinct fragments in all - and the visible text is "[email protected]" with a non-breaking space inside the brackets. Decoded, every one of those fragments is the same single address on onepassapps.com.
This is not a contradiction of our earlier post on where the contact link lives. That one measured the live page in a browser, where the panel builds a mailto anchor once JavaScript runs. This is the HTML the server sends, and in that HTML the address is never a mailto at all.
Two smaller facts fall out of the same sweep. The endpoint itself answers 404 if you fetch it as a page. And no anchor on the site carries an aria-label - not one - so every link takes its accessible name from its own text.
One link that is not in the sitemap
"Support" appears on 33 pages and points at /support. That route answers HTTP 200 and is not one of the 56 URLs in our sitemap.
What leaves the site
19 of the anchors go off-site, all of them on /terms: licences, data sources, and one complaint page, across 12 hosts. 24 anchors carry a rel attribute, all on that page - 23 of them "noopener noreferrer", and one, the ICO complaint link, "noreferrer" on its own.
The limits of this measurement
These are counts of the served HTML only: the fallback card a crawler, or a reader without JavaScript, gets. The panel replaces that card once the bundle runs, and nothing here counts what the panel adds. One build, one day, one IP.
If you want to see the links themselves, the whole site is here: https://app.onepassapps.com/?utm_source=devto&utm_medium=post&utm_campaign=anchor-text-layer&utm_content=site-link
Every guide for all 22 apps and 7 studios is here: https://app.onepassapps.com/guides?utm_source=devto&utm_medium=post&utm_campaign=anchor-text-layer&utm_content=guides-link
Top comments (0)