What is the complete page inventory for an AI-ready website?
The standard business website page set (home, about, services, blog, contact) is organized around a buyer journey for humans. An AI-ready website adds a layer of architecture that doesn't exist in the standard model.
Here is the complete page inventory, organized by function:
Category 1. Architecture pages
| Page Type | What It Does | Schema |
|---|
| Homepage |
Declares overall identity, links to all pillars, establishes the site's purpose |
WebSite + Organization |
| Pillar hub (one per major topic) |
Introduces a major expertise domain, links to all 5 cluster hubs within it |
BreadcrumbList |
| Cluster hub (5 per pillar) |
Answers the cluster's core question, links to all 5 node pages beneath it |
BreadcrumbList |
Category 2. Content pages (node posts)
One page per specific query. Each node:
- Has an H1 that is the exact question as someone would ask ChatGPT today
- Opens with a TL;DR direct answer above the fold
- Contains 5+ H2 fan-out sections that deepen the topic
- Has full schema: BlogPosting + Author + FAQPage + BreadcrumbList
- Links to at least 3 related nodes across the directory
Category 3. Identity pages
| Page | AI Function |
|---|
| About page |
Author identity signals. Origin story, credentials, methodology, off-site profile links |
| Author bio page (optional, recommended) |
Dedicated author markup hub. Connects this site to all off-site authority signals |
Category 4. Conversion pages
These pages exist for humans arriving from AI recommendations, not for AI crawlers:
- Start Here / Free tool page. Captures interest from visitors who aren't yet ready to buy
- Offer pages. Detailed pages for each service or product, with clear conversion pathways
A full authority directory implementation includes all four categories. But the minimum viable version that begins generating AI recommendation is: a homepage, one pillar hub, five cluster hubs, and one complete cluster of five node pages.[1]
What does a pillar hub page need to accomplish?
The pillar hub page is often underbuilt. Many site owners create it as a table of contents. A page that just lists links to the cluster hubs beneath it. That's a mistake.
A pillar hub page has two jobs simultaneously:
- Declare the domain. Establish clearly what this major topic area is, who it's for, and what the reader will understand by exploring it
- Link to all clusters. Present each cluster hub as a card with a one-sentence description of what it covers
For AI purposes, the pillar hub is where the domain classification is confirmed. An AI reading /pillar-2/ and finding a page titled "Website Architecture for AI" with introductory content and links to five specific sub-topics has a clear signal: this site contains an organized body of expertise on this domain. That signal propagates to every page within the pillar.[2]
What does a cluster hub page need that a node page doesn't?
Cluster hub pages operate at a higher level of abstraction than node pages. Where a node answers a specific question in depth, a cluster hub answers the cluster's core question. The overarching question that encompasses all five node questions. In summary form, then links out to the nodes for full depth.
The critical distinction: a cluster hub is not a table of contents. It must contain substantive content that answers the cluster's core question before it lists the nodes beneath it. An AI reading a cluster hub page that has nothing but a list of links will not register it as an authoritative source. It will read it as navigation.
A cluster hub page needs:
- A TL;DR section answering the cluster's central question directly (2–3 sentences)
- A brief but substantive introduction (3–5 sentences) expanding on the answer
- Node cards. Each one presenting the node's question, a one-sentence teaser, and a link
- Related cluster links. Connecting this cluster to 2–3 adjacent topic areas
What makes the About page strategically important for AI recommendation?
AI recommendation is partly about content quality and partly about credibility confirmation. The About page is where most of the credibility infrastructure lives.
An AI-optimized About page includes:
- An origin story. Not just credentials, but the narrative of how you arrived at your specific expertise. Origin stories are the most contextually rich author signal an AI can read.
- Named methodology. If you have a proprietary method or framework, the About page is where you introduce it. This creates a named concept that AI can associate with you specifically.
- Credential specifics. Years of experience, results generated, clients served, and domains covered. In specific terms, not vague claims
- Off-site profile links. LinkedIn, industry organization memberships, podcast appearances. These are the verification links AI uses to confirm that the author identity on-site is confirmed off-site
- Person schema. Structured data that presents all of the above in machine-readable form
An About page with all five elements doesn't just help visitors trust you. it gives AI everything it needs to confidently recommend you by name.[3]
How do conversion pages fit into an AI-ready website?
Conversion pages serve a specific function that is separate from. But complementary to. The AI recommendation infrastructure. They exist for one purpose: to convert the visitor who arrives already pre-sold by an AI recommendation.
When someone asks ChatGPT for a recommendation and your name comes up, they arrive at your site already inclined to trust you. They are not arriving skeptical. They are arriving curious. The conversion page's job is to confirm their instinct, not overcome resistance.
This changes how offer and services pages should be written for an AI-driven business model:
- Lead with what's included. Be specific and complete. The visitor wants confirmation, not persuasion.
- Show the process. How does working with you actually work? Pre-sold visitors want to visualize the experience, not read social proof.
- Make the next step obvious. One clear call to action. The conversion page should not try to handle multiple audiences or multiple offers simultaneously.
Conversion pages do not need to be AI-optimized in the same way content pages do. They need to be human-optimized for a visitor who is one step from saying yes.[4]
The VCYL Perspective
The most common question I get from experts who want to build an authority directory is: "Where do I start?" The answer is always the same: architecture before content. Build the pillar pages. Build the cluster pages. Build the homepage. Wire all the navigation. Then write the nodes.
The reason this order matters: when you have the architecture in place, every piece of content you create lands in a complete, coherent structure from the moment it's published. AI crawlers indexing a new node page find it sitting in a fully built hierarchy with a pillar hub above it, a cluster hub above that, and a homepage at the top. The structural signal is strong from day one.
When you build without the architecture. When you just start publishing content. You end up with an expanding collection of pages with no coherent hierarchy. The content might be excellent. But AI can't classify it as the expertise ecosystem you intend it to be. The Authority Directory Method is, at its core, a building sequence: establish the skeleton, then fill in the substance. This site was built in exactly that order. The page you're reading right now is part of that skeleton.
