Writers covering cannabis need lineage, terpene, and grow data they can cite, and they will not cite a product page. A strain database built from lab results and breeder records gives them the reference, and gives you the links and topical depth that come with being one.
Reference pages earn what shop pages cannot
Nobody links to a checkout button. A journalist writing about a strain, a forum poster settling a lineage argument, a blogger comparing terpene profiles — all of them need a neutral page to point at. Leafly built much of its authority this way. You do not need to beat Leafly; you need the strains you actually carry documented more deeply than anyone else has bothered to, which is a much smaller hill.
Fix the fields before the first entry
Decide the template once: parents and lineage, breeder, indica-sativa classification with whatever caveats you attach to it, dominant terpenes, typical test ranges, flowering time, grow difficulty, and known aliases. Every entry fills every field or marks it unknown. The discipline is the product. A database where some entries have terpenes and others trail off into vibes reads like a blog wearing a costume.
Use data you can defend
Terpene and potency numbers come from your certificates of analysis, so ask your lab for full terpene panels and publish the dominant results with the test date attached. Lineage and flowering data come from breeder documentation, credited. Where sources disagree, say so on the page. Never fill a gap with an invented number; a single fabricated figure, caught once, costs the credibility the whole asset runs on.
Structure it like a database, not a blog
One entry per strain at a stable URL, a consistent template on every page, and a filterable index by type, terpene, or effect. Cross-link the genetics: each entry links to its parents and to its known crosses, so a reader can walk a family tree without leaving your site. Those internal paths also concentrate topical depth around genetics in a way scattered blog posts never manage, and they hand your strain-adjacent articles an obvious hub to link back to.
Promote it to people who cite things
An asset launches; it does not just appear. Show the database to the bloggers and reporters who cover strains. Answer strain questions in forums by citing the specific entry. Run dead strain URLs from defunct sites through Ahrefs and offer your entries as replacements to whoever still links there. Every one of those moves puts the database in front of someone whose job includes linking to sources.
A worked example and the upkeep
Say a dispensary starts with the 45 strains on its own menu. Each entry gets lineage from breeder records, terpene results from the last three certificates of analysis, and two sentences of honest grow notes from staff. New batch, new numbers, updated on arrival. Within a couple of quarters the database is the internal-linking hub for every blog post the shop publishes, a couple of local writers have cited entries instead of Leafly because the data is local, and the budtenders use it on the floor. That last part is worth noticing — an asset your own staff relies on tends to stay maintained, and maintained is what keeps it citable.
Key takeaways
- Writers cite neutral reference pages, never product pages; the database is the citable layer.
- Fix the entry template first and fill every field or mark it unknown.
- Terpene and potency data come from your COAs with test dates shown; no invented numbers.
- Cross-link parents and crosses so the genetics form a walkable tree.
- Depth on the strains you carry beats breadth you cannot maintain.
Frequently asked questions
How many strains do I need at launch?
Enough to look intentional, few enough to do well. Forty or fifty entries documented to full depth beat five hundred stubs, because a writer who lands on one thin page decides the whole database is thin. Start with what you actually sell and grow from there.
Where does terpene data come from?
Your own certificates of analysis. Ask your lab for full terpene panels, not just potency, and publish the dominant three or four per strain with the test date. Label batch results as batch results; averages presented as constants are how databases lose credibility.
Leafly already exists. Why bother?
Leafly and Wikileaf win on breadth, which leaves depth open. Your own lab numbers, local availability, breeder detail, and grow notes for your climate are things a national database cannot have. You are not outranking them everywhere; you are becoming the better source for your slice.
How do the first links arrive?
Push, then pull. Show the database to writers who cover strains, cite specific entries when answering forum questions, and offer entries as replacements for dead strain links you find in Ahrefs. After the first wave, entries start collecting citations on their own.
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 ›