What is an answer hub?
An answer hub is a part of your own domain where every question your market asks has its own page: the question as the title, the answer in the opening lines, and the detail beneath. It is a knowledge base built to be found rather than to be searched once somebody is already inside.
Most companies already have the material. It is in the reply an account manager writes four times a month, the objection handled on every second call, the specification a support engineer keeps re-explaining. None of it is published anywhere a search engine or an assistant can reach, because it lives in inboxes.
An answer hub is the place that material goes when it is finally written down once. What makes it a hub rather than a blog is that each page settles exactly one question and is titled with that question in the words people use.
How is it different from an FAQ page?
| FAQ page | Answer hub | |
|---|---|---|
| Addressing | One URL for forty questions | One URL per question |
| Purpose | Reduce support volume | Be found by people who do not know you yet |
| Length per answer | Two lines | As long as settling it honestly takes |
| Linkable | Only to the page | To the exact answer |
| Quotable by a machine | Rarely, because forty answers compete | Yes, because the page is about one thing |
The addressing difference is the whole difference. A question that cannot be linked to cannot be cited, shared in a message, or sent by a salesperson as a reply. Forty answers on one page means thirty-nine of them are invisible.
How is it different from a blog?
A blog is organised by date and written for a reader who is browsing. A hub is organised by subject and written for a reader who arrived with one question and will leave when it is answered. A blog post ages; a hub page gets revised. Most companies need both, and confusing them produces a blog full of undated evergreen pieces nobody maintains.
A blog is published. A hub is maintained.
What a hub needs to work
A subfolder or a subdomain you control. A hub on somebody else's platform builds their authority with your knowledge, and disappears when you stop paying.
The slug should be the question, readable and stable. Changing it later costs you everything that pointed at it.
Forty to sixty words that settle the question outright, before any context.
Subheadings written as the questions they answer, so a machine can lift a section and a reader can skim to theirs.
Question and answer schema that matches what the page actually says, with an author and a revision date.
Grouping by subject, a search box, and where you can manage it, an agent that answers from the published pages rather than improvising.
Which questions belong on it
Start from the questions you already answer rather than from keyword research. Three sources, in this order of usefulness:
- What sales and support answer repeatedly. Highest intent, already written somewhere, and nobody else publishes it because it feels too obvious.
- What your own site search and any on-site assistant is asked. These are people who came to you specifically and did not find an answer.
- What search data shows being asked in your subject. Broadest reach, weakest intent, and the place everybody else starts, which is why it is the least differentiated.
Questions this settles
Twenty well-chosen questions is a working hub. The number matters much less than whether each page settles one question in its opening lines.
A subfolder is the simpler default because it inherits the authority of the main domain. A subdomain is defensible when the hub is a separate product surface or a separate brand.
Usually the FAQ page becomes the index: a short list linking to each answer's own page, rather than the place all the answers live.