A cannabis knowledge base is a library of short, direct answers organized by subject: one page per question, grouped into hubs that each own a topic. The structure is most of the SEO. This site runs on that model — 500 guides sorted into 12 clusters, every page reachable from its hub.
A knowledge base is not a blog
A blog is a stream. Newest first, organized by date, built for readers who already follow you. A knowledge base is organized by subject and built for someone who arrives from a search with one question. Each page answers that question near the top, covers what follows from it, and links sideways to the next thing the reader will wonder about. Google's people-first content guidance describes the target well: the visitor should leave satisfied instead of clicking back to the results. Blogs age. A knowledge base, maintained, does not.
Source the questions before you write anything
Pages should map to questions real people ask, and those come from four places. Search Console shows queries your site already surfaces for. Google autocomplete and People Also Ask show what people around your topic type next. Reddit grower and buyer threads hold the questions people hesitate to ask out loud. And if you run a counter, your budtenders hear the rest every shift. Pull from all four before opening a document. The list will run to hundreds, and that is the point — a knowledge base of forty pages is a category page wearing a costume.
Structure it before you scale it
- Group the question list into subjects. A full cannabis vertical usually yields ten to fifteen groups.
- Give each group a hub page that defines the subject and links to every page inside it.
- Publish one page per question, answer first, detail after.
- Cross-link related pages within a hub, and link every page back up to its hub.
Flat URLs and folder URLs both work. What matters is that a crawler, or a reader, can get from any page to its hub and its siblings in one click.
The worked example: this library
The library you are reading is the model applied. Five hundred guides across twelve clusters: fundamentals, local SEO for dispensaries, ecommerce, content marketing, and so on. Every guide links up to its cluster page, and the sidebar on each guide links across to siblings in the same cluster. When Search Console surfaces a question no guide answers, that question gets a page and a slot in a cluster. The per-page overhead stays small because the structure existed before the first fifty pages did. Retrofitting structure onto a few hundred unorganized posts is a much worse week.
Stay on the right side of the scale
Google names scaled content abuse as a spam policy: many pages produced primarily to rank, adding little for the person who lands on them. A large knowledge base resembles that description by size alone, so the defense has to live in the pages. Each one should answer a question the others do not. When two pages drift toward the same answer, consolidate them and redirect the loser. Keep a human review step in the loop too — a wrong answer about state possession limits does more damage than a missing page.
Key takeaways
- A knowledge base is organized by subject for searchers with one question; a blog is organized by date for followers.
- Source pages from Search Console, autocomplete, People Also Ask, and Reddit before writing. Hundreds of questions, one page each.
- Hub-and-spoke structure decided up front keeps a 500-page library navigable; bolting it on later is painful.
- Size invites scaled-content scrutiny, so every page must earn its slot with a distinct, correct answer.
Frequently asked questions
What is a cannabis knowledge base?
A library of pages organized by subject rather than date, each answering one question a searcher actually asks. Pages group into hubs, one per topic, and the hubs interlink, so readers and crawlers can move from any answer to the related ones.
How many pages does a knowledge base need?
Enough to cover the questions your market asks, which usually means hundreds, not dozens. Start with the subjects Search Console and People Also Ask surface most, publish in batches, and let real queries drive what gets added next.
Will Google penalize a large knowledge base?
Size alone is not the trigger. The scaled content abuse policy targets pages produced mainly to rank, so a library stays safe when every page gives a distinct, correct answer and near-duplicates get consolidated rather than left to pile up.
Want this done for your brand?
We build cannabis & CBD search visibility with full transparency, for dispensaries, brands, and MSOs.
Get a free cannabis SEO audit ›