Skip to content
ClusTraly

The pillar page: neither dump nor table of contents

The pillar page: neither dump nor table of contents

This guide starts from a simple observation: on page pilier, the gap between sites that progress and the rest rarely comes down to a secret. It comes down to a method applied without exception.

Spotting orphan pages

A page no internal link points to technically exists but has almost no chance of performing. On older sites they often represent a fifth of published content.

Identifying them is easy; deciding their fate is not. Each orphan must be attached, merged or removed — leaving it as is, is not a neutral option.

How to measure that it works

Set the measurement before acting, not after. Record the starting value, the date, and the exact metric you expect to move. Without that initial snapshot, any conclusion is just an impression.

Prefer one metric per project. Following twelve curves at once feels like control, but makes it impossible to attribute a result to a cause.

The three-link rule

Each secondary piece points to its main page, to a sibling of the same level, and receives at least one link from the main page. That minimal reciprocity is enough to form a coherent set.

Beyond that, extra links quickly show diminishing returns, and end up diluting the very signal you meant to concentrate.

Keeping the structure alive

A cocoon built once then forgotten degrades with every publication. The habit to install is simple: before publishing, every new piece must know which set it belongs to and who will link to it.

Asking that upfront avoids accumulating isolated content that will need attaching later, at a far higher cost.

A silo is not a folder

The most frequent confusion is believing a cocoon is built in the URL tree. It is built in contextual links, inside the text, where they actually carry meaning.

A clean URL structure helps readability, but it is internal linking that transmits authority and signals thematic kinship.

Check before moving on

  • Document the decision, not just the action
  • Automate every repetitive check
  • Remove before adding
  • Measure before, not after
  • Assign each point to a named person
  • Schedule a review in six months

What it changes for the reader

It is tempting to treat this as a purely technical constraint. In practice, each of these optimisations translates into a clearer, faster or more predictable experience for the person reading.

That is precisely why engines care about these criteria: they approximate, imperfectly, genuine user satisfaction.

Read next

Where to start

If you take only one action from this article, take the one touching the largest number of pages at once: the effort-to-impact ratio is almost always best there. The rest follows more easily.