中
Back to notes

Root theory: SEO is a root system, not a list of pages

The mental model behind everything I ship 鈥?pillar pages as taproots, internal links as root hairs, and the domain as the biggest root pot of all.

Most people treat a site's content as a list of pages. I treat it as a root system. That single shift is the theory behind Anchor, behind module 3 of Cheese SEO, and 鈥?as of the fusion 鈥?behind why the estate is split across two domains at all. I call it root theory, and this is the long version of it.

One topic, one tree

The unit of content is not the page; it is the tree. A tree is one topic, grown deliberately:

The taproot is the pillar page 鈥?the core long-form on one topic that every cluster article links back to. The lateral roots are the topic clusters: sub-topic articles around the pillar, each covering exactly one long-tail angle. The root hairs are the internal links 鈥?the connections crawlers follow to discover the whole site, the way water finds its way through soil.

Equity flows up, traffic enters at the tips

Every internal link passes authority. Done right, the cluster's link equity flows back along the laterals and gathers in the taproot 鈥?the pillar page gets stronger precisely because its cluster exists. Meanwhile search traffic enters the system at the root tips: the long-tail keywords, the capillaries. You do not rank the pillar by wishing; you rank it by growing enough tips for the water to come in.

Two more pieces complete the picture. Articles in one cluster should link to each other 鈥?sibling links, reinforcing the topical-relevance signal on every crawl. And when a topic outgrows one tree, a super hub links the trees together so equity can flow between them. That is the 鈽?node, and it is a mode in the workbench, not a metaphor.

What goes wrong

Most content fails the same two ways, and both are visible in the root metaphor. An orphan page is a dashed circle: no internal link points to it, so it is hard to find and hard to rank 鈥?it exists, but it is not part of the system. And a standalone article that belongs to no tree at all is exactly what it sounds like: content falling in the forest with nobody linking to it. The fix is always the same 鈥?link it into a cluster, or fold it under a pillar. And when a page retires, it should 301 into a related pillar: the link equity goes home instead of dying with the URL.

The domain is the biggest root pot

Here is where the theory stops being about pages and starts being about architecture. If one tree is one topic, then the domain is the biggest root pot of all. This is why aeox.uk and go.aeox.uk stayed two domains through the fusion: the technical tree and the commercial long-tail grow in different soil, and a marketplace selling ebooks does not muddy a technical site's topical signal any more than a garden centre next door changes what grows in your pot. It is also why this very blog keeps its categories separate 鈥?notes, engineering, tools 鈥?instead of one undifferentiated feed. One tree, one topic; internal links do not cross trees.

Where you can see it

The content forest in the AeoX workbench renders the theory as a zoomable graph: hubs, spokes, scheduled drafts, orphan circles, colors by status. It is the most honest documentation I have 鈥?not a diagram of the theory, but the theory itself, drawn from real data every time you open it.

One honest caveat, the same one I put on the product page: structure is a lever, not a guarantee. Root theory will not save content nobody wants, and SEO outcomes have many factors. But when the content is worth reading, the root system is what makes sure the water finds it.

Comments

Comments are powered by GitHub Discussions. Sign in with GitHub to leave one.

More in this category

NotesOct 11, 20267 min

The fusion: everything I run now lives on two domains

NotesJun 16, 20269 min

Pettivalpets.com — 2 months from launch to Google #7 on a real long-tail

← PreviousFine-tuning tiny models as the decision brain: the candidate list and where the training data comes fromNext →The fusion: everything I run now lives on two domains