Building a Cannabis FAQ Hub for Search Visibility

Mine questions from three places

Skip the brainstorm. The questions are already written down for you. People Also Ask boxes on Google show what searchers around your target queries want next — type your city plus "dispensary" or a product category and expand the boxes a few levels deep. Your Google Business Profile Q&A tab holds questions real customers asked your actual store, and most dispensaries never open it. And your budtenders field the same fifteen questions every shift; ask them to write down a week's worth.

If you sell online, add the support inbox. Every "do you ship to" email is an FAQ entry somebody else will search for next month.

Decide between one page and many

A single FAQ page works while answers stay short — payment types, ID rules, hours, parking, purchase limits. The moment an answer needs 300 words and its own subheadings, it has stopped being an FAQ entry and become a guide. Give it a URL of its own and link to it from the hub. A hub with thirty tight answers plus links out to a dozen full guides beats one bloated page trying to do both jobs.

Write answers people can lift

Lead with the answer, then qualify it. "Yes, we take debit — there is a $3.50 terminal fee" beats two sentences of throat-clearing. Keep most answers under 60 words. That length reads fast on a phone, fits a featured snippet, and gives AI search tools a clean passage to quote. Longer context can follow, but the first sentence has to stand on its own.

Know what FAQPage schema still buys you

Google restricted FAQPage rich results to well-known government and health sites back in 2023, so a cannabis FAQ will not get the expandable dropdowns in search results. Add the markup anyway. It costs nothing, it maps each question to its answer for search engines and AI assistants, and machine-readable question-and-answer pairs are exactly what generative results pull from. Keep the schema matching the visible text word for word — a mismatch is the fastest route to a manual action.

A worked example

Take a Colorado dispensary building its hub. The GBP Q&A tab supplies "is there an ATM," "can I pay with a card," and "do you accept out-of-state IDs." People Also Ask around "recreational dispensary Colorado" adds purchase limits and whether menu prices include tax. Budtenders contribute "what is the difference between live resin and distillate" — too big for the hub, so it becomes a linked guide instead. The result is roughly 25 short answers on one page, three linked guides, and FAQPage markup across the lot. It gets reviewed quarterly, because payment rules and purchase limits change without notice.

Frequently asked questions

Do FAQ pages still get rich results for cannabis sites?

No. Google limited FAQPage rich results to well-known government and health sites in 2023, and dispensaries do not qualify. The markup is still worth adding because it hands search engines and AI assistants clean question-and-answer pairs to work from.

How many questions should an FAQ hub cover?

Enough to cover what customers actually ask — for most dispensaries that lands between 20 and 40. Cut anything nobody asks, and move any answer that needs its own subheadings out to a full guide with its own URL.

Where do I find the questions customers really search?

Expand the People Also Ask boxes around your core queries, read the Q&A tab on your Google Business Profile, and have budtenders log a week of counter questions. Your support inbox fills in the rest.