Give each post one search intent, put the direct answer in the first screen, write H2s that read like the questions people type, and link the post to the product and category pages it exists to support. Then make sure the CMS has not quietly undone any of it.
One post, one intent
Before writing a word, name the single question the post answers. Not the topic; the question. A post that tries to cover how long edibles last, how they are dosed, and which brands to buy is three posts wearing one URL, and it will lose to three competitors who each picked a lane. Worse, when you later publish those focused posts anyway, the old catch-all cannibalizes them. Check what already exists on your own blog for the query first; the fight you most often lose is against your own archive.
The answer goes in the first screen
Searchers, and the systems ranking for them, reward pages that resolve the query fast. Open with the direct answer in two or three sentences, then spend the rest of the post earning trust: the caveats, the mechanism, the edge cases. This is the answer-box pattern, and it also happens to be what gets quoted by AI search results. Burying the answer under 600 words of preamble was always bad writing. Now it is bad positioning too.
Headings that mirror real searches
H2s are the skeleton Google reads and the path a skimming reader follows. Write them as the sub-questions people search — how long do edibles take to kick in, can you fly with gummies — rather than clever section labels. Each heading becomes a doorway for its own long-tail query, and the post picks up rankings its title never targeted.
Internal links pay the rent
An informational post exists to collect authority and hand it to pages that sell. Link from the post body to the relevant category and two or three products, using their names as anchors, and add a link back from the category hub so the post is not orphaned. A post with no links to money pages is a favor to the whole internet except your store.
Check what the CMS did to it
Platforms sabotage posts in quiet ways. Auto-generated slugs with dates in them. Tag and category archives that create three duplicate URLs per post. The same post published twice during an import. A featured image with no alt text. After publishing, confirm the post has one URL, one canonical, one home in the site structure. That five-minute check regularly explains why an otherwise solid post never ranked.
A worked example
A client's post on storing live resin ranked page three with the answer in paragraph nine and zero links to the store. The rewrite moved the answer — airtight glass, cold, dark — into the opening lines, recut the H2s as the storage questions people search, and added four internal links: the concentrates category plus three in-stock products. Same information, same URL. It climbed to page one over the next several weeks and the concentrates category, newly linked, firmed up alongside it.
Frequently asked questions
How long should a cannabis blog post be?
As long as the intent requires. A dosing question can resolve in 400 words; a first-grow guide may honestly need several thousand. Padding a short answer to hit a word count buries the answer and helps nobody.
Do blog posts actually help product pages rank?
Yes, indirectly. Posts win the informational rankings and earn the links that product pages rarely attract, then pass that authority down through internal links with descriptive anchors. That transfer is most of the reason a store publishes articles at all.
Key takeaways
- One intent per post, and check your own archive for cannibals before writing.
- Direct answer in the first screen; the rest of the post is supporting evidence.
- H2s phrased as real sub-questions win long-tail queries on their own.
- Every post links to its category and products, and gets a link back from the hub.
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 ›