FAQ-Based Site Architecture as an On Page SEO Strategy

Structure a site so each page answers one audience question up front, carries matching FAQ markup and links back to a single entity home.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

This skill turns a site into a set of single-purpose answer pages. Instead of long pages that try to rank for everything, each page takes one question a reader would ask, answers it immediately, and backs the answer with detail and machine-readable markup. For where this sits in the wider approach, see the David Bain SEO method page; this page covers only how to do the architecture work.

The core rule comes from Jason Barnard, speaking in a talk on generative AI in search: one question answer per page, a simple answer to a simple question, covering every question your audience might be asking, with FAQ schema markup. Each part of that sentence is a design decision. One question per page sets the unit of the architecture. A simple answer sets the page format. Every question sets the scope of the inventory. FAQ schema sets the markup layer.

The markup is not a decoration added at the end. A Majestic podcast on entity optimisation advises practitioners to take schema.org into account so they get used to thinking in data structures, because what you explain through machine-readable markup needs to be translated to human content. In practice that means you design the question, the answer and their relationship as structured data first, then write the visible page so it says the same thing.

The last piece is the entity home. Barnard's contribution to the SEO in 2026 (source) collection describes creating an entity home by designating a canonical URL, such as the About page on your own site, as the point of reconciliation for your brand's digital footprint. In an FAQ architecture, every answer page is a claim made by your brand, and the entity home is where those claims resolve to one identity.

What you produce:

• A question inventory, deduplicated and grouped by topic
• A page template with a question heading, a short answer, supporting detail and schema
• A schema pattern that mirrors the visible question and answer
• A designated entity home that every answer page links to

You can tell the architecture has gone wrong when several pages answer the same question, when answers are buried below introductions, or when the markup says something the visible page does not.

How It Works

The architecture works because it makes the page, the question and the answer the same unit. When a page answers exactly one question, there is no ambiguity about what it is for. A reader lands and finds the answer in the first lines. A crawler or answer engine parses a heading that states the question, a short passage that resolves it, and markup that labels both. Barnard frames this as a simple answer to a simple question, repeated for every question your audience might ask, which makes the inventory of questions, not a list of keywords, the blueprint for the site.

Every answer page is built from the same small set of elements. The template is what lets you scale the architecture without each page drifting into its own format.

The order matters. The short answer sits directly under the heading because it is the part most likely to be extracted and shown out of context. If it depends on a paragraph above it to make sense, it fails as a standalone answer. Supporting detail comes after, so readers who only need the answer can stop and readers who need depth can continue.

The schema layer follows the design habit described in a Majestic entity-optimisation podcast: think in data structures, because what the markup explains must translate into human content. The practical test is agreement. The question in the markup should be the question in the heading, and the answer in the markup should be the answer a reader sees. When the two diverge, you have two versions of the page and neither can be trusted.

The entity home holds the whole structure together. Barnard describes it as a canonical URL, like the About page, that serves as the point of reconciliation for everything that talks about your brand. A large set of single-question pages can look like scattered fragments unless each one clearly belongs to the same source. Linking every answer page to the entity home, and keeping the entity home's description of who you are consistent with what the answer pages imply, gives search engines one place to confirm the identity behind the answers.

Signs the mechanism is breaking: two pages rank against each other for the same question, the opening lines are an introduction rather than an answer, markup is generated from a template that ignores the page's actual text, or the entity home says one thing about your expertise while the answer pages claim another.

Step-by-Step Guide

Step 1: Collect the audience's questions

Gather the questions your audience actually asks from search results, support tickets, sales calls and on-site search. Write each one in the reader's words, as a full question rather than a keyword fragment. Aim for the breadth Barnard describes, every question your audience might be asking, within the subject area you have chosen to own. Record the source of each question so you can later judge how real the demand is.

The output is a raw question list, not yet deduplicated.

Pro tip: Keep the reader's phrasing in a separate column from your cleaned-up version, so the heading can stay close to how people really ask.

Step 2: Assign one question to one page

Merge questions that ask the same thing in different words, then give each distinct question a single target page. Where a question is genuinely different, even if related, it gets its own page. Where two phrasings would produce the same answer, they share one page and one heading. Map each question to an existing URL if one already answers it, or mark it as a new page.

This mapping is your guard against pages competing for the same question.

Pro tip: Test a merge by writing the short answer for both phrasings. If the answers are identical, it is one page.

Step 3: Write the short answer first

Under a heading that states the question, write a short answer that fully resolves it in the opening lines. The answer must make sense with no introduction above it, because it may be read on its own. Avoid scene-setting, definitions of obvious terms and promises of what the page will cover. If the honest answer is conditional, state the condition inside the answer rather than deferring it.

Only once the short answer stands alone should you move on.

Pro tip: Read the short answer aloud to someone who has not seen the page. If they need to ask a follow-up to understand it, rewrite it.

Step 4: Add supporting detail beneath

Below the short answer, add the reasoning, steps, caveats and examples a more involved reader needs. Keep all of it in service of the one question the page answers. If a section starts answering a different question, move it to that question's page and link to it. Use subheadings so a reader can scan to the part they need.

The page ends when the question is fully handled, not when it reaches a target length.

Step 5: Mark up the question and answer

Add FAQ schema that labels the page's question and answer, using the same wording that appears on the page. Design the markup as a data structure, following the Majestic advice to think in data structures and translate the markup into human content. Generate the markup from the same fields that render the visible heading and short answer, so they cannot drift apart. Validate the markup after publishing and after any template change.

A mismatch between markup and visible text is a defect, not a style choice.

Pro tip: Store the question and short answer as named fields in your content model, and render both the page and the schema from them.

Step 6: Designate and connect the entity home

Choose one canonical URL, typically your About page, as the entity home, as Barnard recommends for reconciling your brand's footprint. Make sure it states clearly who you are and what you are qualified to answer. Link every answer page to it, for example from the author or publisher block in the template. Check that claims of expertise on answer pages match what the entity home says.

Revisit it whenever you add a new question area.

Pro tip: Put the entity home link in the page template, not in individual articles, so no new answer page ships without it.

Best Practices

• Build the site from the question inventory, not from a keyword list. Questions define what a page must resolve, while keywords only describe what people type, and pages built from questions are easier to keep single-purpose.
• Keep the question heading as close to the reader's phrasing as possible. The heading is the signal of what the page is for, and a heading in internal jargon breaks the match between what was asked and what was answered.
• Render visible text and FAQ schema from the same source fields. This follows the Majestic advice to think in data structures that translate into human content and makes drift between markup and page impossible by design.
• Write every short answer to survive being read in isolation. Answer engines and snippets lift passages out of context, so an answer that leans on an earlier paragraph will be shown incomplete.
• Treat the entity home as the root of the architecture. Barnard describes it as the point of reconciliation for your brand's digital footprint, so every answer page should link to it and none should contradict it.
• Maintain a question-to-URL register and check it before publishing. The register is how you stop a new writer from creating a second page for a question that is already answered.

Common Mistakes

• Stuffing several questions onto one long FAQ page with an accordion of short answers.: Give each distinct question its own page, as in Barnard's rule of one question answer per page. A shared FAQ page can still exist as a navigation hub that links out to the individual answer pages.
• Opening the page with an introduction and burying the answer several paragraphs down.: Put the short answer directly under the question heading. Move context and background into the supporting detail, where readers who want it can find it.
• Writing FAQ schema that paraphrases, extends or differs from the visible answer.: Generate the markup from the same fields as the visible heading and answer. The markup should describe the page a reader sees, not a different or better version of it.
• Creating separate pages for trivially different phrasings of the same question.: Merge phrasings that produce the same answer onto one page. Keep the alternate phrasings in your inventory as notes for the heading and supporting detail rather than as new URLs.
• Publishing many answer pages with no consistent link to an entity home.: Designate a canonical entity home, such as your About page, and link to it from the page template. Without it, the answer pages look like disconnected fragments rather than claims from one identifiable source.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: David Bain SEO

Related Skills

• Auditing Topical Gaps Against Competitor Sites
• Building Topical Authority Maps for Niche Domination
• Clustering Long-Tail Use-Case Keywords into Content Silos
• Executing Brute-Force Niche Content Targeting at Scale
• Creating SEO Strategy Templates for Full Topical Coverage
• Implementing Internal Linking Structures Across Topic Clusters

Sources

• Learn How to Tackle Generative AI in Search - With Jason Barnard - The Brand SERP Guy
• Key SEO Tactics for Entity Optimisation (Live Podcast)
• SEO in 2026: 117 of the Very Best Guests from Digital

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.