The Ghost TOC: It's There. Google Just Can't Exploit It.

There's a subtle thing happening on most authority content pages that's quietly handing your answers away.

You worked hard to write a comprehensive piece. Google crawls it. An AI engine reads it. And instead of attributing the answer to your page — it surfaces the fragment.

yoursite.com/topic/#what-is-x

Not your page. A piece of your page. And in AEO, that distinction is everything.

Here's what's actually happening:

Traditional Tables of Contents use anchor jump links.

<a href="#section-2">Why This Matters</a>

That's not just a navigation convenience. That's a separately addressable URL. Google can — and does — treat page.com#section-name as its own addressable entity. AI answer engines crawling for citation sources see the same thing.

So when someone asks a question your H2 perfectly answers, the engine doesn't necessarily cite your page as the authority. It cites the fragment — the anchor — as the answer source.

You wrote the content. The fragment gets the credit.

That's a canonical leak hiding in plain sight.

The Ghost TOC fixes this without removing anything the reader needs.

Your TOC still lives on the page. Readers still see the section list. The structure is still visible and scannable.

The difference: no anchor jump links.

It's a static section list — a clean visual reference to what's inside — with the canonical pointing exclusively to the base URL. No fragments. No addressable anchors. No ambiguity about what page owns this content.

When Google or an AI engine reads the page now, there is only one address that can receive authority, citations, and answers:

Your URL. The whole page. As you intended.

Why this creates a competitive advantage:

Almost every SEO plugin, every content template, every "optimized post structure" guide defaults to anchor-linked TOCs. It's baked into Yoast, RankMath, every WordPress block theme.

Which means almost every competitor you have is leaking their canonical signal the same way — and they don't know it.

The sites running Ghost TOC structure are consolidating authority onto a single URL while everyone else is fragmenting it across a dozen anchor variants of the same page.

In a world where AI engines are deciding what to cite and surface — and they're increasingly choosing full-page authority over fragment matches — this is not a small edge.

The doctrine in plain terms:

Use descriptive H2 headings that are self-navigating. If the page genuinely needs a section reference (5,000+ word pillar), use a static HTML section list — visible, readable, helpful — with zero anchor jump links. Canonical points to the base URL. Always.

The TOC is there. Google just can't use it against you.

And here's where it gets real for this community:

Ghost TOC isn't just a doctrine you have to implement manually and hope your developer follows.

We're building it directly into the CortexMCP → WordPress integration layer.

The CortexMCP WP Draft system — which is currently in final debugging and going live soon — will handle Ghost TOC structure automatically on output. Every draft that comes through the pipeline will be built this way from the jump. Correct section structure. No anchor links. Clean canonical. Done.

You won't have to think about it, audit for it, or fix it after the fact.

It's doctrine baked into the machine.

That's what separates a content system from a content process. Processes rely on people remembering. Systems make the right thing the only thing.

Stay tuned — the WP Draft integration is close, and Ghost TOC ships with it.

This is what "Membership has Privileges" actually means — not just knowing the doctrine, but having it built into the tools working for you.

1 comment