The Card Title Is the Target Guide's Own Heading: 39 of 39, Word for Word

I work on OnePassApps, the team behind app.onepassapps.com. This is the third post on the "Related guides" section that closes all 22 of our app guides. The first measured the section's shape, the second measured the graph its links make. This one reads what is written on the card.

What I measured

2026-11-12: all 22 guide pages and all 22 app pages of app.onepassapps.com, fetched over plain HTTPS, signed out, no cookies, no JavaScript, GET only. Every page answered HTTP 200. On each guide page I parsed the Related guides section and, for every card in it, the tool name, the category label, the title link, the description paragraph and the Open button.

The section holds 39 cards in total: 17 guides list two other tools and 5 list one.

A card carries five written fields, and all five come from the target

Here are three of the cards, with every field each one carries:

Three things in those rows are worth pulling apart.

The title link text is the target guide's own heading, word for word. For every one of the 39 cards, the text of the title link is byte-identical to the <h1> of the guide it points at: 39 of 39. It is also a prefix of that guide's document title in 39 of 39 cases, because every guide title is its own heading followed by the same suffix - a space, an em dash, a space and the word OnePassApps.

The name and the button come from the target app page. The card's name is the head of the target app page's own <h1> in 39 of 39 cards, and the button text is "Open " plus that same name in 39 of 39, pointing at the same tool as the title link in 39 of 39.

The description is shared by every card that names the same tool. The 39 cards name 18 distinct tools, and each of those tools carries one description string wherever it appears - 18 distinct description strings across 39 cards. The description is written once per tool and repeated on every card that names it.

This corrects what I wrote on 8 November

An earlier post here measured this same section and made the graph it makes. It concluded, from two examples, that "the sentence on a card is written for that card, not pulled from a shared field on the target page", and the two sentences it quoted were "How to merge and organise PDF pages in your browser" and "How to build a CV and print or save a résumé as PDF".

Both of those strings are the card's title link, and both are the target guide's own <h1>. So the title link is not written for the card - it is the heading the target page already prints, reused as the link text.

The description under it is the other field on the card, and that one is shared by every card naming the same tool, which is why the two descriptions in a reciprocal pair differ from each other: they are two different tools' descriptions, not two different sentences written for two cards.

The graph itself is unchanged and that post remains the canonical write-up for it: 39 edges across 22 guides, 26 of them reciprocated, in 13 pairs. This post is about what the words on the card say, not about how the links connect.

The app links on a guide page

Each guide page also carries exactly two links to its own app page - 44 across the 22 guides - plus one Open button per card, so guide pages carry 83 links to app pages in total. A guide page links to its own guide 0 times.

What I did not do

One build, one day, one network, plain HTTPS, GET only, signed out, no cookies and no JavaScript, so this measures the documents the server sends and not the rendered pages. I did not click a link and I did not open an app, so I am claiming only that the served documents carry these fields and these words. A card or a label added by JavaScript would not appear in this count.

If you want to walk the apps themselves, they are here: https://app.onepassapps.com/apps/label-maker?utm_source=devto&utm_medium=post&utm_campaign=card-text-layer&utm_content=label-maker-link - and the guides that carry the cards are here: https://app.onepassapps.com/guides?utm_source=devto&utm_medium=post&utm_campaign=card-text-layer&utm_content=guides-link