“Stubs create the AI-retrievable surface area. Full articles provide the depth that converts. Once both exist, they feed each other.” — Lou

Session context: 2026-01-29_Mastermind — Lou introduced this architecture during the GEARS Alpha intake walkthrough, in response to the question of how to create AI-legible content without compromising the depth and voice that makes content valuable for human readers.

Core Idea

There is a tension in GEO content strategy: the format AI engines prefer (short, structured, question-format titles, direct answers, FAQs) is different from the format that builds human authority and converts readers (long-form, voice-driven, narratively rich). Trying to optimise a single piece of content for both audiences produces mediocre results for both — too structured and sparse for humans, too conversational and unstructured for AI.

The two-tier architecture resolves this tension by separating the two functions into distinct content types:

AI-legible stubs are short, highly structured pages built for AI retrieval. They use question-format titles, deliver a direct answer in the first paragraph, include structured supporting points, and close with a FAQ section — exactly the format AI engines use to generate answers. Stubs are not primarily for human readers; they’re citation anchors. Their job is to own a specific territory in the AI knowledge graph and route any human traffic toward the full article. A stub of 200–400 words can own a citation territory that would take years to accumulate through general content publication.

Full human-facing articles are long-form, voice-driven, authoritative content that serves the human reader. These are where depth, narrative, distinctive voice, and conversion happen. They don’t need to be structured for AI retrieval in the same way the stubs are — because the stubs are handling that function and routing relevant traffic to them.

The architecture creates a virtuous cycle: stubs attract AI citations and route human traffic to full articles; full articles build conversion authority and generate the kind of substantive content that reinforces the stubs’ credibility. The two tiers are not competitors — they’re complementary layers of the same authority architecture.

The additional benefit: stubs can be created for topics before the full article is written. You can establish a citation anchor immediately, create the retrieval surface area, and write the full article when you’re ready. The stub functions as an article brief as well as a citation anchor.

Practical Application

Building your first stub:

  1. Choose one topic you’re an authority on but haven’t written a standalone page about.
  2. Write a question title (the question your ideal client would ask an AI engine).
  3. First paragraph (150–200 words): answer the question directly. Don’t hedge. Don’t frame. Answer it.
  4. Supporting section (3–5 bullet points or short paragraphs): the most important supporting considerations.
  5. FAQ section (4–6 questions and direct answers): the follow-up questions someone who read your answer would naturally ask.
  6. One sentence at the end: “For the complete guide to [topic], see [link to full article].”

Total length: 300–500 words. Publish it on your website as a standalone page (not a post). Give it a URL that matches the question title.

That’s a stub. It creates an AI citation anchor. The full article can follow when you’re ready to write it.

Evolution Across Sessions

This establishes the baseline for a two-tier content architecture in the vault. The GEO content strategy insights have focused primarily on what to create (topology, canon, laws, pillars). This insight adds how to structure individual pieces of content for dual-audience optimisation — AI retrieval and human conversion simultaneously. The stub-and-article architecture is a practical implementation layer beneath the content topology strategy.