---
title: "Central Entity Selection: the First Step in Topical Authority"
description: "The single naming decision that decides whether a B2B SaaS topical map can plausibly be earned — pick the entity narrow enough to own, broad enough to matter, and one or two queries away from the page that converts."
url: "https://serpnaut.xyz/playbook/topical-authority-for-saas/central-entity-selection"
verifiedAt: "2026-06-09"
canonical: "https://serpnaut.xyz/playbook/topical-authority-for-saas/central-entity-selection"
---

# Central Entity Selection: the First Step in Topical Authority

> TL;DR — The central entity is the one named topic your SaaS site is trying to be the source on. SERPNAUT's is 'B2B SaaS SEO' — narrow enough that a six-month-old site can win it in 6–12 months. Picking 'SEO' instead would have meant competing with Backlinko (DR 91) and Search Engine Journal (DR 92) on a SERP with no peer-sized sites in the top 20.

In plain English: Central entity selection is the upfront naming decision that decides whether a SaaS topical-authority project can succeed. The right entity is narrow enough that a small site can plausibly become the source, broad enough to contain real commercial intent, and verifiable by a peer-sized site already ranking in the top 20.

## Key takeaways
- The central entity is a single noun phrase the ICP would recognise — not a product category, tagline, or sentence.
- If you cannot list 5–8 sub-topics on one sheet of paper, the entity is too narrow.
- If page one of the head term has no peer-sized site in the top 20, the entity is too broad — pick a sub-segment.
- Test commercial proximity: any sub-topic should be at most two links from the page that converts.
- Defer all other candidate entities in writing — splitting attention on day one stalls most topical-authority projects.

## Definition
The central entity is the single named topic a topical map is built around — narrow enough that a small site can plausibly become the source, broad enough that the queries inside it match real commercial intent for the product.

## Why it matters
Most failed topical SEO projects fail at this step, not at writing. Founders pick an entity that is either too broad (no realistic path to source-of-truth status) or too narrow (no commercial intent inside it). A correctly chosen entity makes the next nine months of work compound; a wrong one means every page you publish reinforces a topic Google has no reason to associate with your product.

## What 'central entity' actually means
A central entity is the noun phrase your site is trying to become the answer for. It's the topic Google should associate with your domain when a user types a head term into search. For SERPNAUT it is 'B2B SaaS SEO'. For Invoicemonk it is 'invoicing for freelancers'.
It is not your product name, your category, or a tagline. It is the topic underneath which every page on the marketing site can plausibly sit. If a page on the site would feel off-topic next to the entity, the entity is too narrow or the page shouldn't exist.

## The three tests every candidate has to pass
Test 1 — can you list 5–8 sub-topics on one sheet of paper? If yes, the entity has enough structure to map. If you can only think of three, it's too narrow; if you list twenty and they leak into unrelated areas, it's too broad.
Test 2 — does the SERP for the head term contain at least one site your size? Search the head term. If page one is wall-to-wall billion-dollar publishers and there is no peer-sized site in the top 20, pick a more specific entity.
Test 3 — is there a believable two-link path from any sub-topic to the page that converts? If a sub-topic article would have to make four lateral hops to mention the product, the entity is too far from commercial intent.

## The most common mistake: picking the broadest entity
Founders default to the broadest plausible topic because it sounds more ambitious. 'SEO' instead of 'B2B SaaS SEO'. 'Invoicing' instead of 'invoicing for freelancers'. The broader topic has more search volume but is unwinnable — the SERP is already saturated by sites with 10× the backlinks.
The narrower entity has less volume per query but a realistic path to the top of page one within months. Total traffic from a well-mapped narrow entity beats partial rankings on a broad entity, every time.

## What to do when two entities both look right
Pick the one closer to commercial intent and build it first. The other is your second map, 6–9 months later, after the first sub-topic ranks. Splitting attention between two entities on day one is the second-most-common reason topical-authority projects stall.
Document the deferred entity in writing so the team doesn't drift toward it accidentally. Topical authority is built by saying no to adjacent topics for longer than feels comfortable.

## Quick answers
### Is the central entity the same as my product positioning?
(https://serpnaut.xyz/playbook/topical-authority-for-saas/central-entity-selection#qa-vs-positioning)
No. Positioning describes what the product does for a buyer ('the simplest invoicing tool for freelancers'). The central entity describes what topic the site is trying to be the source on ('invoicing for freelancers'). They're related but not interchangeable — positioning lives on the home page; the entity governs every blog URL.

### What does a central entity look like for a SaaS company?
(https://serpnaut.xyz/playbook/topical-authority-for-saas/central-entity-selection#qa-saas-examples)
SERPNAUT's is 'B2B SaaS SEO'. Invoicemonk's is 'invoicing for freelancers'. Notion's would be 'connected workspace'. Each is a real noun phrase the ICP recognises, narrow enough that a single map can plausibly cover it, and tied directly to what the product sells.

### How do I know my central entity is too broad?
(https://serpnaut.xyz/playbook/topical-authority-for-saas/central-entity-selection#qa-too-broad)
Three signs: (1) you can't list its sub-topics on one page without leaking into a second entity, (2) page one of the head term has no peer-sized site in the top 20, (3) a typical sub-topic article would need four lateral hops before it could naturally mention your product. Any one means re-scope narrower.

### Can I change the central entity after I start publishing?
(https://serpnaut.xyz/playbook/topical-authority-for-saas/central-entity-selection#qa-change-later)
Technically yes, in practice it costs 6–12 months because every page, link, and schema reference has to be re-aligned. Spend the extra week picking the right one upfront — the entity decision is the highest-leverage choice in the whole project.