David Bain SEO: What the Method Is and What It Isn't

Created by David Bain - https://davidbain.com

Overview

David Bain SEO is a label for a content-led approach that combines four ideas: building topical authority in a defined subject area, grouping long-tail use-case queries into clusters, publishing niche pages at scale, and organising the site around FAQ pages that each answer one question. The label attributes the approach to David Bain, whose official site describes him as a podcast producer and content marketing expert who has published five books in the marketing genre, including a series of SEO books for Majestic. He hosts the Majestic SEO Podcast, a monthly panel of SEO experts debating current search issues, and is credited as the brainchild of [Majestic's SEO in 2024 (source) book and YouTube channel](https://artios.io/david-bain-seo-in-2024-majestic), which Majestic describes as a collaboration with Casting Cred and the wider SEO community. Treat the name as shorthand rather than a brand: the published record presents Bain as a practitioner, interviewer and curator of SEO advice, not as the author of a separately validated system.

The closest verifiable source trail is Majestic's SEO in 2023 Preview, published December 1, 2022, in which Bain hosts a discussion of content planning built on keyword research, topic clusters, search intent and content gaps, with subjects organised into top-level categories and subcategories. The same discussion argues that keywords help reveal clusters and that writers should cover the concepts and questions behind keywords rather than hit a fixed word count. The scale element traces to a separate Majestic programmatic SEO discussion, which defines programmatic SEO as the systematic creation of templated pages and calls it potentially the most scalable way to do SEO. Read together, these sources suggest a sequence of work in which each stage feeds the next and internal linking sends what you learn back into the map.

flowchart LR
  A[[Topical authority map](https://tryhamster.com/skills/building-topical-authority-maps)] --> B[Competitor gap audit]
  B --> C[Long-tail use-case clusters]
  C --> D[FAQ-based architecture]
  D --> E[Niche pages at scale]
  E --> F[Internal linking]
  F -->|refine| A

What the record does not show matters as much as what it does. The table summarises the attribution question for anyone who needs to reference the method in a strategy document.

Two consequences follow. First, do not promise stakeholders the results of a proven system, because no independently verified case study attributes rankings, traffic or revenue gains to this method. Second, judge each component by the evidence behind it: topic clusters and gap analysis come straight from the 2022 planning discussion, while the one-question-per-page structure echoes Jason Barnard's advice of one question and answer per page with FAQ schema markup rather than anything Bain published as his own rule.

No published head-to-head study compares this approach with editorial SEO, technical SEO, paid search or other named methods; a LinkedIn profile of a David Bain working as a senior SEO consultant lists enterprise SEO, migrations and audits but no controlled results, so any comparison is structural rather than measured. Against editorial SEO, which usually plans individual articles around target keywords, this approach plans the whole subject area first and treats each page as a slot in a map. Against technical SEO it is content-first, yet it leans on technical work at the scale stage, where the programmatic source stresses indexing, crawling, technical correctness, page structure and internal linking. Against programmatic SEO alone, it adds the topical map and FAQ structure that decide which templates are worth building. Against paid search, it trades speed for coverage that keeps working after publication, and nothing in the sources quantifies that trade.

Clustering is where teams most often cut corners. The SEO Handbook argues that manual grouping is more accurate than relying entirely on automated keyword clustering, and warns that automated grouping can merge unrelated intents or split one cluster into several artificial groups. A workable compromise is to let a tool produce a first pass, then have someone who knows the audience check every cluster boundary against the live results page before any page is briefed. Keeping the map, gap audit and cluster list in one shared workspace, such as Hamster Studio, means the people writing briefs see the same structure as the people who built it.

Core Principles

Own a defined subject area

Decide which subject you want to be known for before you research a single keyword. The planning discussion in SEO in 2023 Preview organises subjects into top-level categories and subcategories, and that hierarchy becomes the frame every later decision is tested against. Without it, gap audits and keyword tools will pull you toward whatever competitors happen to rank for. If your category list keeps growing with unrelated topics, the boundary was never set.

Cover concepts and questions, not word counts

Length is an output, not a target. The same 2022 discussion says writers should cover the concepts and questions behind keywords rather than produce a fixed word count. Brief each page with the questions it must answer and the concepts it must explain, then let the page be as long as that takes. Padding to hit a number is the clearest sign this principle has been dropped.

Group by intent before you write

A cluster is a set of queries a single page can satisfy because the searcher wants the same thing. Keywords that look alike can hide different intents, which is why The SEO Handbook favours manual grouping over fully automated clustering. Check the live results for each proposed cluster: if the ranking pages differ in type or purpose, split it. Creating a page per keyword is the opposite failure and dilutes coverage.

One question, one answer per page

FAQ-based architecture gives each specific question its own page with a direct answer near the top. Jason Barnard describes this as one question answer per page, a simple answer to a simple question, with FAQ schema markup. The structure makes pages easy for search engines and answer engines to extract and easy for readers to scan. It fails when answers are buried under preamble or when one page tries to answer five unrelated questions.

Scale only when each page adds unique value

Templated niche pages are the scale lever, and also the biggest risk. The Majestic programmatic SEO discussion says generated pages should provide something unique and target clear user intent rather than reproduce existing pages. Before building a template, name the data or insight that makes each instance different. If swapping the niche keyword is the only change between pages, you are producing thin content.

Measure long-tail results with care

The more specific the queries, the harder they are to track. The same programmatic SEO source notes that Google Search Console samples more data as queries become more long-tail. Judge clusters and page groups in aggregate rather than chasing individual query rankings. Report directional trends and avoid claiming precision the data cannot support.

Steps

1. Build the topical authority map Define the subject area you want to own and break it into top-level categories and subcategories. Inputs are your product, audience and the questions your customers ask; the output is a hierarchy every page will slot into. Keep the boundary strict so later research does not drag you into irrelevant topics. The detailed technique is on Building Topical Authority Maps for Niche Domination.

   You know it went wrong when you cannot say in one sentence what the site is about.

2. Audit topical gaps against competitors Compare your map and existing pages with the sites that actually rank for your target queries, including informational sites that sell nothing. Look for missing topics, weaker depth, missing formats and stale pages, not just missing keywords. Filter every finding against your map before adding it to the plan. Output a prioritised list tagged create, update or consolidate.

   See Auditing Topical Gaps Against Competitor Sites for the full workflow.

3. Cluster long-tail use-case keywords Collect specific use-case queries under each subcategory and group them by the intent behind them. Use a tool for a first pass, then review each cluster boundary by hand against the live results. Each final cluster should map to one page or one tight group of pages. Avoid creating a separate page for every variant.

   The method is covered in Clustering Long-Tail Use-Case Keywords into Content Silos.

4. Design the FAQ-based architecture Turn clusters into pages that each answer one clear question, with a short direct answer at the top and supporting detail below. Add FAQ markup where it fits and designate a canonical page that explains who you are and what you do. Decide URL patterns and where each page sits in the hierarchy before writing starts. Instructions are on Designing FAQ-Based Site Architecture for SEO.

   A page that needs three headings to reach its answer signals a structural problem.

5. Produce niche pages at scale Where a cluster repeats across many niches, build a template and populate it with data that makes each instance distinct. Check that every generated page has unique value, clean structure and a realistic chance of being indexed. Launch a small batch first and confirm indexing before producing the rest. Follow Executing Brute-Force Niche Content Targeting at Scale for templating and quality checks.

   If most of a batch stays unindexed, stop and fix the template before adding more.

6. Implement internal linking across clusters Link each category hub to its pages, link pages back to their hub, and add cross-cluster links only where a reader would naturally move next. Use descriptive anchors that tell users and crawlers what the destination covers. Plan links as a user journey, not as a density quota. See Implementing Internal Linking Structures Across Topic Clusters.

   Orphan pages found in a crawl mean this step was skipped.

7. Track coverage with a strategy template Record every category, cluster, page, status and next review date in one coverage matrix. Review it on a fixed cadence, for example quarterly, and feed findings back into the map. Judge performance by cluster rather than by individual long-tail query. Use Creating SEO Strategy Templates for Full Topical Coverage as the starting structure.

   A matrix nobody has updated in months means the plan has drifted from the site.

When to Use

• You operate in a niche with many specific use cases or questions, because the method's value comes from covering that long tail systematically rather than competing only for head terms.
• A competitor consistently outranks you across a subject you consider core, because a gap audit against a topical map shows whether the problem is missing topics, thin depth or missing formats.
• Your site has grown article by article without a plan, because mapping categories and clusters exposes duplicates, orphans and holes you can fix in one pass.
• You have structured data, such as locations, integrations or product variants, that can power genuinely distinct templated pages at scale.
• Your audience asks many discrete questions that support or sales teams answer repeatedly, because one-question-per-page architecture turns those answers into findable pages.
• You need a shared content plan that several writers can execute consistently, because the map and cluster list give everyone the same structure.

When Not to Use

• You need leads this month, because content coverage builds slowly and paid search or outbound will move faster.
• You cannot add unique value per page, because templated niche pages without distinct data or insight become thin content that may not be indexed.
• Your market has only a handful of meaningful queries, because a full topical map and FAQ architecture is overhead when a few strong pages cover demand.
• You must promise stakeholders proven results from a named system, because published sources contain no effectiveness studies or verified case studies for this method.
• Your site has unresolved crawl, indexing or migration problems, because adding many pages to a broken technical base multiplies the problem.