Dev.to WebDev πŸ›  Dev πŸ‘ 0 πŸ“– 4 min read

The Related Guides Graph: 39 Links Between 22 Guides, One Hub and Four Guides Nothing Points At

I work on OnePassApps, the team behind app.onepassapps.com, so this is a measurement of our own documentation. Every one of our 22 app guides ends with a "Related guides" section. An earlier post here measured the shape

I work on OnePassApps, the team behind app.onepassapps.com, so this is a measurement of our own documentation.

Every one of our 22 app guides ends with a "Related guides" section. An earlier post here measured the shape of that section - "17 of them list two other tools and 5 list one", and "Each card links twice: to the other tool's guide and to that tool's app page".

This post measures the thing that shape hides: the graph those links make.

39 directed edges, 26 pairs

Counting only the guide-to-guide links inside the Related guides sections: 39 directed edges across 22 guides. 26 of those edges are reciprocated - 13 pairs where A points at B and B points back at A. The other 13 are one-way.

The 26 distinct pairs break down as 13 mutual and 13 one-way.

The graph is one piece

All 22 guides sit in a single connected component: from any guide you can walk the related links and reach every other one. Nothing is stranded, and no guide is an island.

One hub, and four guides nothing points at

label-maker is the most-referenced guide in the fleet: 5 other guides point at it - calendar-maker, chart-maker, invoice-maker, paperkit, qr-code-maker - while it points at only 2 of its own.

The other end of the scale is four guides that no other guide points at: citation-formatter, newsflow, screen-recorder, signature-maker. Each of them still points outward (1, 1, 2, 2 links respectively), so they are not isolated - they are simply never returned to.

Five clusters inside the reciprocal half

Strip out the one-way edges and look only at the 13 mutual pairs. They fall into 5 clusters:

  • Cluster of 6: chart-maker, cv-builder, email-signature, label-maker, paperkit, social-card.
  • Cluster of 4: ambient-noise-mixer, calendar-maker, focus-timer, time-zone-planner.
  • Cluster of 3: password-generator, qr-code-maker, word-counter.
  • Cluster of 2: movie-tracker, screen-planner.
  • Cluster of 2: subtitle-workbench, teleprompter.

17 guides sit in a cluster. The other 5 - citation-formatter, invoice-maker, newsflow, screen-recorder, signature-maker - share no reciprocal edge with anything at all.

Every pair is described twice, differently

For all 13 mutual pairs the two cards describe each other in different words - 0 of 13 share a description. The CV Builder guide's card for the PDF Organiser reads "How to merge and organise PDF pages in your browser"; the PDF Organiser's card for the CV Builder reads "How to build a CV and print or save a rΓ©sumΓ© as PDF".

So the sentence on a card is written for that card, not pulled from a shared field on the target page.

A category label on every card

Each card also prints a three-part category label next to the app name - a group, a subject, and a note. There are 18 distinct labels, one for each guide that any card points at, and no two pointed-to guides share one.

14 of them end in Local utility. Four do not:

  • cv-builder - Writing / Documents / Careers
  • email-signature - Writing / Work / Utility
  • movie-tracker - Personal / Media / Discovery
  • screen-planner - Personal / Media / Planning

The four guides nothing points at have no label on any card, and for the same reason: a label only appears where a card points at that guide.

The order has nothing to do with the sitemap

The related links do not follow the order the guides are listed in. 24 of the 39 edges point backwards through that order and 15 point forwards, and only 9 of them connect two guides that sit next to each other in it.

Who else points at the guides

Only three kinds of page outside the guide pages link to a guide at all. The home page links all 22, the guides index links all 22, and each of the 22 app pages links to its own guide exactly once.

So a guide with no inbound edge from another guide still has three inbound links from elsewhere on the site.

Limits

One build, one GET per URL, 8 November 2026, plain HTTPS from one network, no browser, no JavaScript. Nothing here describes how the pages look once they render, and no claim is made about how a crawler or a reader follows the links.

The byte counts are a snapshot of one build: the sitemap answers 4,046 bytes and 56 URLs, and the 22 guide pages run 26,600 to 32,451 bytes.

The graph counts the links inside the Related guides sections only. The home page, index and app-page links are counted separately above, and are not part of the 39.

I work on OnePassApps - the team behind app.onepassapps.com. The 22 guides are at https://app.onepassapps.com/guides?utm_source=devto&utm_medium=post&utm_campaign=guide-link-graph&utm_content=guides-link, and the most-referenced one, the Label & Card Maker, is at https://app.onepassapps.com/apps/label-maker?utm_source=devto&utm_medium=post&utm_campaign=guide-link-graph&utm_content=label-maker-link.

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.