# Cannabis Product Page SEO: Packaging, Compliance, and Search **Author:** John Morabito (Founder, /winston) **Published:** September 19, 2026 **Reading time:** 11 minutes **Canonical:** https://www.winstondigitalmarketing.com/playbooks/cannabis-packaging-and-product-page-seo/ A shopper opens their phone at nine at night and types something like "10mg gummies for sleep." Your product page says "Blackberry Chill 1:1, 100mg total THC, 10 pieces, batch 24B." Both of those describe the same jar. Only one of them is language a person would ever type, and the other is the language on the label, which came from compliance, which came from the state, which your point of sale inherited and your menu published without anyone deciding that it should. That gap is most of cannabis product page SEO. Packaging copy exists to satisfy a regulator and reads like it. Search queries exist because somebody wants something and often cannot name it precisely. The obvious fix, writing the page in the customer's words, is exactly where you walk into claims your license does not let you make. So the actual work is finding the version of the page that is useful to a shopper, findable for the queries they type, and still compliant. > **General information, not legal advice** > > This playbook is about search and content strategy. It is not legal advice. Cannabis labeling and advertising rules are set state by state and change often, and the federal position on health claims sits on top of all of them. Before you publish a product page template, have your own counsel review it, check your state regulator's current guidance, and read the FDA and FTC material on product claims and substantiation. ## What shoppers search, and what the label says The queries that reach a dispensary or brand product page come in a handful of shapes. The packaging serves one of them. - **Form factor and dose.** "10mg gummies", "half gram pre roll", "live rosin cart". Closest to label language and usually the easiest to serve well. - **Strain and cultivar.** "blue dream", "runtz", "wedding cake". Real volume, completely generic, and shared with every other menu in the state. - **Brand and product line.** Lower volume, highest intent of anything on this list, and the pages most menus never build. - **Effect and occasion.** "gummies for sleep", "something for a hike", "strongest edible on the menu". Where the money is, and where the compliance line runs right through the middle. - **Price and deal.** "cheapest ounce in [city]", "[brand] deals". Served better by category and promotion pages than by product pages. The label covers the first shape, and it covers it in units rather than in words. "100mg / 10pc" is not "10mg gummies," and a crawler is not going to do that arithmetic on your behalf. A product page that reproduces the label and stops is competing for its own SKU name, which it shares with the forty other menus carrying the same jar. ## The claims line, and where it actually sits The instinct on effect queries is to answer them directly: this one is for sleep. That sentence is where most cannabis product copy gets into trouble, and it is worth being precise about why, because the rule is narrower than the anxiety around it. The problem is not describing a product. It is claiming an outcome, particularly a health outcome. The federal position, which applies regardless of what your state permits, is that a product marketed as treating, curing, preventing, or mitigating a disease or condition is being marketed as a drug, and the FDA has issued warning letters on exactly that basis, most visibly across the CBD market. Separately, the FTC expects an objective claim in advertising to be substantiated before it runs. Put together, "helps with insomnia" and "reduces anxiety" and "relieves chronic pain" are decisions your compliance lead owns, and they are the kind you lose. States then layer their own rules on top: restrictions on therapeutic claims, on language or imagery that could appeal to minors, on depicting consumption, on comparative safety claims. Those vary enough that no portable national list exists, which is the part that makes a multi-state template hard and the part that sends you to your regulator's current rules instead of to a blog post. What is left is more than most operators assume. You can say what the product is, how it was made, what is in it and at what measured potency, what it smells and tastes like, how people commonly use it, what time of day it tends to get reached for, and how it sits next to the other things on your shelf. That is a product page. The move is to write the descriptive version of the answer rather than the diagnostic one. Not "for insomnia," but "a heavier indica-leaning gummy that most people save for the end of the night." The useful accident is that the descriptive version also performs. Not for "gummies for insomnia," which you were never going to win safely anyway, but for the long tail of how people describe what they are after, and for AI answers, which get assembled out of specific descriptive text far more readily than out of marketing claims. ## The elements that have to be on the page Alongside the copy sits a set of elements you do not get to choose, set by the state you operate in. The categories recur even though the details do not. - **Warning statements.** Most states mandate specific warning text, sometimes with prescribed wording, placement, or prominence. Treat that text as a fixed string handed to you by compliance, not as copy to be tightened. - **Age gating.** Whether a gate is required, what it must ask, and whether it must block the content or merely sit in front of it are all state-level questions, and they have direct search consequences. - **License and operator identification.** Many states require the license number and the legal entity to appear on the site, sometimes on the page itself. - **Potency and content disclosure.** Measured THC and CBD content, per serving and per package, taken from lab results rather than from marketing. - **Lab testing.** Where a certificate of analysis has to be available, and how it has to be linked. For search, the two that matter most are the age gate and the warnings. A hard gate implemented as a script that replaces the page content will, in a lot of implementations, leave a crawler looking at an interstitial instead of a product. The pattern that survives is a gate that renders the full page in the HTML and overlays the modal on top, so the content is in the source whether or not the visitor has clicked through. Test it the way you test anything else: fetch the URL with JavaScript disabled and look for your product copy in the response. Warning text creates the opposite problem. It is identical on every page by design, so on a 900 SKU menu the largest shared block of text across your entire catalog is a legally mandated paragraph. That is not a penalty in the way people mean it, because no such penalty exists, but it does mean the distinguishing content on each page has to carry more weight than it would anywhere else. ## The thin page problem at menu scale This is where most cannabis catalogs actually fail, and it has nothing to do with compliance. A dispensary carries several hundred to several thousand SKUs. The product data arrives from the point of sale with a name, a brand, a category, a potency, a price, and frequently a description written by the brand and shipped identically to every retailer carrying it. Publish that as a page and you have published a page that already exists elsewhere, many times over, with a different logo at the top. What you end up with is a catalog of pages that are individually thin, collectively near-identical, and expensive to crawl. Search engines work out fairly quickly that fetching your menu rarely surfaces anything new, and they slow down accordingly. The general mechanics of that failure, and the consolidate-or-improve decision it forces, are in [fixing thin and duplicate content](https://www.winstondigitalmarketing.com/playbooks/fixing-thin-and-duplicate-content/). The cannabis version has three practical answers. - **Do not give everything a page.** A product you stocked once, in one quantity, gone in a week, does not need an indexable URL. Depth belongs to the SKUs that persist: house brands, staples, the things you reorder. The rest can live in the menu without being a landing page. - **Write at the level that is stable.** The cultivar, the brand, the product line, and the category all outlast inventory churn. A real page about a strain or a house line, with genuine information on it, survives every individual jar and collects the links and citations that individual jars never will. - **Add the layer the brand description cannot have.** Your inventory notes, your budtenders' read, how it compares to the other three things in that price band on your shelf, what it pairs with, how fast it sells out. None of that is in the manufacturer's copy, and all of it is both useful and yours. That third one is the entire differentiator, and it is why a retailer can outrank a brand on the brand's own product. The brand can tell you what the thing is. Only the retailer can tell you what it is like compared to the rest of the case. ## Structured data, used honestly Product and Offer markup is how a machine reads your catalog, and in a category where a large share of the visible page is legal boilerplate, it carries more of the load than usual. The fields worth populating are the factual ones: name, brand, category, sku, image, description, and an offers block with price, priceCurrency, availability, and the URL that actually transacts. Two rules keep this out of trouble. The first is parity: everything in the markup has to be visible on the page that serves it. Markup saying a product is in stock at thirty-two dollars while the visible page says sold out hands a wrong answer to a machine that will go on repeating it. Price and availability drift is the common version, and because it is a sync problem rather than an SEO problem, it usually has no owner. The second is that structured data is not a place to launder a claim. A description property containing "relieves anxiety" is the same claim it would be in a headline, except machine-readable and easier to find at scale. The same goes for aggregateRating, which has to describe real reviews that exist and are visible on the page. The temptation in a category full of thin pages is to enrich the markup past what the page supports, and that is the fastest route to a catalog nothing trusts. Worth stating plainly: none of this makes a product eligible for shopping surfaces that exclude cannabis. The markup is for organic understanding and for the AI systems reading your catalog. It is not a workaround for a platform policy. ## The invisible menu All of the above assumes a crawler can see your products, and on the most common dispensary stack it cannot. The embedded menu from a point of sale provider either renders inside an iframe served from the provider's domain or assembles itself client side after load, which means the product names, prices, and descriptions never appear in your page's HTML. You can write the most useful compliant product copy in the state and publish it into a box that search engines read as empty. The diagnosis takes about a minute, and the three fixes ranked by cost are in [the Dutchie iframe SEO problem](https://www.winstondigitalmarketing.com/playbooks/dutchie-iframe-seo-problem/). The short version is that whatever content strategy you pick has to end in server rendered HTML on your own domain. As far as search is concerned, a product page that exists only inside the embed is a screenshot of one. ## Building it 1. Fetch your menu and one product page without JavaScript. If your products are not in the response, stop here and fix that first, because nothing downstream matters until they are. 2. Get the compliance elements as fixed strings from counsel or your compliance lead: warning text, license display, age gate behavior, lab result linking. Build them into the template once, so no page can be written without them. 3. Pull the queries you actually get. Site search logs, Search Console, and the questions budtenders field at the counter. That is your effect and occasion vocabulary, and for a local menu it beats any keyword tool. 4. Decide what earns a page. Persistent SKUs, house brands, product lines, and cultivars in. One-off drops out. 5. Write the descriptive version. Product, process, measured potency, sensory detail, how people use it, how it sits against the rest of your shelf. No outcome claims. 6. Mark it up in parity with the visible page, then check the price and availability sync on a schedule instead of only at launch. 7. Have counsel read the template, not just the first page. Templates are where mistakes scale. ## The point The product page is where the two halves of a cannabis business collide. One half is the packaging, written to survive a regulator and reading like it. The other half is a person searching for something they can only describe by how they want their evening to go. The page that works speaks the second language while respecting the first, and the operators who manage it end up with a catalog nobody else has, because everyone else published the same brand file. This is the content layer of a broader program, and it sits on top of the local and menu work in [cannabis dispensary SEO](https://www.winstondigitalmarketing.com/playbooks/cannabis-dispensary-seo-2026/). If you want a read on what a crawler and an AI engine currently see when they hit your menu, that is where our [cannabis marketing practice](https://www.winstondigitalmarketing.com/services/cannabis-marketing/) starts, and the [free AI visibility audit](https://www.winstondigitalmarketing.com/audit/) will tell you which of your products exist in the source at all. ## Frequently asked questions ### What can a cannabis product page legally say? In general terms, a product page can describe the product without claiming a health outcome. Naming the cultivar, the form factor, the measured potency from lab results, the ingredients and the process, the aroma and flavor, and how people typically use the product is description. Saying it treats, cures, prevents, or relieves a disease or condition is a health claim, and the federal position is that marketing a product that way makes it an unapproved drug, which is the basis on which the FDA has sent warning letters across the CBD market. States layer their own restrictions on top, commonly around therapeutic claims, appeal to minors, and depictions of consumption, and those vary enough that there is no single portable list. This is general information rather than legal advice, so confirm your template with your own counsel and with your state regulator's current guidance. ### Can you use Product schema on cannabis product pages? Yes, and it is worth doing, because in a category where much of the visible page is mandated boilerplate the structured data carries more of the factual load. Populate the factual fields: name, brand, category, sku, image, description, and an offers block with price, priceCurrency, availability, and the URL that actually transacts. Two constraints matter. Everything in the markup has to be visible on the page it describes, and price and availability in particular have to stay in sync with the live menu, because a wrong price in markup is a wrong answer handed to a machine that will repeat it. And markup is not a place to put a claim you would not put in a headline, since a description property is as readable as the page copy and easier to audit at scale. ### Why are dispensary menu products not showing up in Google? Usually because the menu is embedded rather than published. The common point of sale integrations render the menu inside an iframe served from the provider's domain, or assemble it client side after the page loads, so the product names, prices, and descriptions never exist in the HTML of your own page. A crawler fetching your menu URL sees a header, a footer, and an empty container. The test takes a minute: fetch the page with JavaScript disabled and search the source for a product you carry. If it is not there, no amount of product page copy will help until that content is server rendered on your own domain. ### How do you avoid duplicate content across a large cannabis menu? Stop publishing a page for every SKU, and stop shipping the manufacturer's description as your page body. The brand description arrives identically at every retailer carrying that product, so publishing it verbatim puts you in a set of near-identical pages competing with each other. Give indexable pages to what persists, meaning house brands, staple products, product lines, and cultivars, and let short-lived drops live in the menu without a landing page of their own. Then add the layer the brand cannot write: how the product compares to the others on your shelf in that price band, what your staff says about it, and how it sells. That retailer-specific context is the only part of a product page that is genuinely yours. ### Should cannabis product pages target strain names as keywords? Strain names carry real search volume, but they are shared with every other menu in the state, which makes them the wrong target for an individual SKU page. The better structure is one durable page per cultivar covering what the strain is, its reported profile, and which products on your menu currently feature it, with the individual jars linking to it rather than competing with it. That page survives inventory churn, accumulates links and citations, and gives search engines one clear answer for the strain instead of eleven near-identical ones. Pair it with brand and product line pages, which have lower volume and much higher intent, and which most menus never build at all.