All posts
SEO & AI search

Topical Authority for Startups: How Many Articles Do You Really Need?

How many articles build topical authority? A sizing method per subtopic, based on distinct buyer questions, instead of a magic number of blog posts.

By Mehdi Hassan7 min read

The short answer

Topical authority doesn't come from a fixed number of articles. You need one strong page for every distinct question a buyer asks inside a subtopic, plus a hub that ties them together. A narrow subtopic may need a handful of pages and a broad one several dozen, so finish two or three subtopics completely first.

Key takeaways

  • There is no magic article count. Size each subtopic by its distinct buyer questions.
  • One page per question that needs its own answer; fold the rest into sections or the FAQ.
  • Finish two or three subtopics completely before spreading thin across ten.
  • Internal links between the hub and its pages are what turn articles into a topic.
  • Money pages come first: a topic with no path to an offer is coverage, not authority.

Part of B2B Content Strategy That Generates Pipeline, Not Pageviews

What is topical authority, and why is there no magic number?

Topical authority is the trust a search engine or AI system gives a site because it has covered a subject completely and well, not just once. When your site answers every important question in a subtopic, engines learn to return to you for that subject, including for queries you never targeted directly.

The trouble with "you need 30 articles" advice is that subtopics differ wildly in size. "SOC 2 for startups" might have eight real questions behind it; "B2B content strategy" has dozens. A fixed number either leaves gaps in big topics or forces filler into small ones, and filler is exactly what Google's scaled content abuse policy targets. We cover how topics fit into a wider plan in our B2B content strategy guide.

So the right question isn't "how many articles". It's "how many distinct questions does this subtopic contain, and which of them deserve their own page". The rest of this article is a method for answering that.

How do you size a subtopic for topical authority?

You size a subtopic by listing every question a buyer asks about it, grouping questions that share one answer, and giving each group that needs more than a few paragraphs its own page. The count that comes out is your target for that subtopic.

  1. Name the subtopic narrowly

    Pick something a buyer would search as one theme, such as "Webflow migrations", not "websites". If you can't describe it in four words, it's probably two subtopics.

  2. Collect every question

    Pull questions from sales calls, support tickets, People Also Ask, Search Console queries and a few ChatGPT prompts. Write them as the buyer would say them.

  3. Group by answer, not by keyword

    Two questions belong together if the same page would answer both well. "Webflow migration cost" and "how much to move to Webflow" are one page; "Webflow migration cost" and "Webflow migration checklist" are two.

  4. Decide page or section

    A group gets its own page if its answer needs a table, steps or more than about 300 words. Smaller groups become an H2 inside a related page or an FAQ answer.

  5. Add the hub

    Every subtopic gets one hub page that answers the broad question and links to each spoke. The hub is the page you want cited for the head term.

  6. Map each page to a next step

    Note which offer or money page each article leads to. A page with no logical next step is a sign it belongs in a different subtopic, or nowhere.

Run this on a real subtopic and you get a number that fits it: small for a narrow theme, much larger for a broad one. That number is an output of the method, not a target to hit.

How do you build topical authority without spreading too thin?

Build topical authority by finishing a small number of subtopics completely before starting new ones. Three subtopics covered end to end beat ten subtopics with two posts each, because engines judge coverage per subject, not per site.

A practical order for a startup is: first the subtopic closest to your product and pricing, then the one buyers research just before they compare vendors, then the problem-awareness subtopic at the top of the funnel. Each finished subtopic also gives you a reusable topic cluster and pillar page structure for the next one.

This also keeps the work honest. Finishing a subtopic means writing the hard pages too: pricing, comparisons and objections, which are the ones that convert.

Which pages count toward topical authority?

Every indexable page on the subject counts, not only blog posts. Product pages, pricing, comparison pages, case studies, docs and glossary entries all tell an engine what you know and what you sell.

That matters more in AI search. TripleDart's Q1 2026 study of 28 B2B SaaS companies found homepages earned 31.9% of LLM citations and 81.7% of AI-attributed leads, while general blog posts drew 12,000 sessions and zero leads. Pricing comparisons and long-form deep dives were the only blog formats that converted. That's a strong argument for counting money pages as the core of a topic, with articles around them, and for reading our guide to bottom-of-funnel SEO for SaaS before you plan another top-of-funnel post.

Page type

Role in the topic

Build when

Product or service page

Defines what you sell

First

Pricing and comparison pages

Answers the decision questions

First

Subtopic hub

Owns the broad question

Before the spokes

How-to and guide spokes

Answer each distinct question

After the hub

Glossary entries

Define terms and link inward

Once spokes exist

Case studies

Prove the claims

Whenever you have one

How much content depth does each page need?

Each page needs enough depth to fully answer its question and the next two questions a reader will have, and no more. Content depth is about completeness for one intent, not word count.

A useful test: after reading the page, would the buyer need to open another tab to act? If yes, the page is shallow. If they'd skim past whole sections that answer a different question, the page is bloated and should be split. Answer the question in the first two sentences, then give the specifics: steps, numbers, trade-offs and a verdict. A good content brief forces these decisions before anyone writes.

Hypothetical example: sizing a "SOC 2 for startups" subtopic

For example, suppose a compliance startup lists 31 buyer questions about SOC 2. Grouping by answer gives 11 groups. Four are small ("is SOC 2 a law?", "who issues a SOC 2 report?") and become FAQ answers on the hub. Seven need tables or steps: cost, timeline, Type 1 vs Type 2, the readiness checklist, choosing an auditor, SOC 2 vs ISO 27001, and what to show customers. That's one hub and seven spokes, plus the existing pricing and product pages.

The team publishes those eight pages before writing anything about the next subtopic. The number 8 came from the questions, not from a target.

Internal links are what make separate articles read as one body of knowledge. Without them, ten posts on one subject look like ten unrelated pages.

  • Hub to every spoke, in a visible list or table near the relevant section, not buried in a footer.
  • Every spoke back to the hub, early in the page, with descriptive anchor text.
  • Spokes to their siblings where the reader's next question is answered elsewhere.
  • Spokes to the money page that matches their intent, so authority flows toward what you sell.

Audit this whenever you publish a new spoke. The most common gap we see is new posts that link out to older ones while nothing links in, which leaves them orphaned. An on-page SEO audit catches it quickly.

How do you know when a subtopic is complete?

A subtopic is complete when every question on your list has a home, each home links to the hub, and new questions from sales calls keep landing on pages you already have. At that point, new articles in the cluster add little, and refreshing existing pages adds more.

Watch three signals: Search Console shows your hub and spokes earning impressions for queries you never wrote for; prompt checks in ChatGPT and Perplexity start citing your pages for the subject; and sales stops hearing questions your site doesn't answer. When all three show up, start the next subtopic and put the finished one on a refresh schedule.

Frequently asked questions

How long does it take to build topical authority?
It depends on the subtopic's size and your publishing pace, but expect months rather than weeks. Engines need to crawl the pages, see the internal links and gather signals like impressions and mentions. Finishing one subtopic of eight to ten pages quickly usually shows movement sooner than publishing the same number of pages across many subjects.
Can a small site have topical authority?
Yes. Authority is judged per subject, so a 40-page site that covers one niche completely can outrank a large publisher that covers it with a single post. Small sites win by picking narrow subtopics, answering every real buyer question in them and linking the pages together tightly.
Do AI-written articles count toward topical authority?
Pages count if they're genuinely useful, however they were drafted. The risk is mass-producing thin pages, which Google's scaled content abuse policy targets regardless of how the text was made. Use AI to speed up research and drafts, then add first-hand detail, examples and a clear verdict before publishing.
What is a topical map?
A topical map is the planning document behind topical authority: every subtopic you intend to cover, the questions inside each, the page that answers each question and how the pages link. It's usually a spreadsheet or a diagram. The sizing method in this article produces one subtopic of the map at a time.
Should I delete old posts that don't fit my topics?
Not automatically. Posts outside your chosen subtopics can stay if they earn traffic or links, but stop adding to those themes. Thin, off-topic posts with no traffic and no links are candidates to merge, redirect or remove during a content refresh, which keeps the site's focus clear.

· CEO & Design Director

Copywriter, designer and developer, and founder of Designify Studio. Over five years, 60+ projects across 14+ industries, for startups that have raised $300M+.

Want this done for you? Monthly retainer, $6,000.

Your ongoing design and development team, for products that keep shipping. $6,000, per month, flat fee. Book a free 30-minute call to see if it fits.

Schedule Call