Skip to main content
Deep Dive

AEO schema markup for cannabis businesses

AEO schema markup for cannabis: Google says no special schema is needed for AI Overviews. What markup still earns, FAQ and Product limits. Get a free audit.

9 sections
|9 min read
Get Audit
Overview

AEO schema markup is the structured data Bud Authority builds into cannabis websites so machines can read who the business is and what each page covers. Google says AI Overviews and AI Mode need no special markup. Structured data still helps with rich results. Organization, LocalBusiness for each store, Service and Article fit most cannabis sites; FAQ and Product markup carry Google limits.

Part 01

What Google says structured data does for AI answers

A dispensary owner who adds schema hoping to land in AI Overviews is solving a problem Google says does not exist. Its page on AI features and your website states: "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary." On markup in particular: "There's also no special schema.org structured data that you need to add." What stays in force is ordinary search work, because "The best practices for SEO remain relevant for AI features in Google Search (such as AI Overviews and AI Mode)." Whether a page can appear as a supporting link comes down to indexing and snippet eligibility, which our technical cannabis SEO page walks through, and where AEO parts ways with SEO is laid out in SEO vs AEO vs GEO.

Part 02

What schema still earns: rich results, entity clarity and clean extraction

Dropping markup would still cost a cannabis site something. The first job is rich results, the enhanced listings that only appear when a page's markup qualifies. Google's guide to optimizing for generative AI features says structured data is not required there, then adds: "However, it's a good idea to continue using it as part of your overall SEO strategy, as it helps with being eligible for rich results on Google Search."

The second job is identity. Google's Organization structured data documentation says that markup on a home page "can help Google better understand your organization's administrative details and disambiguate your organization in search results." In cannabis, a store name can also be a strain name, a product line or a dispensary in another state, so stating the company plainly in markup removes a guess.

For articles, Google says "you can add Article to more explicitly tell Google what your content is about", including who wrote it and what it is called.

The third job is the easiest to overstate. Slobodan Manic wrote in Search Engine Journal: "Your page might rank No. 1 on Google and still not get cited in an AI response if its content isn't structured in fragments that AI can extract." His point is about how the visible content is written. Markup cannot write a quotable passage. What it adds is a second, machine-readable copy of facts the page already prints: the business name, the service, the author, the date. Writing the passages themselves is the job of our AEO content strategy work, and the generative-engine view of the same markup is on GEO schema markup for cannabis.

What schema still earns

Rich results

Structured data helps with being eligible for rich results on Google Search

Enhanced listings when a page's markup qualifies
Identity

A store name can also be a strain name, a product line or a dispensary in another state

Organization markup that disambiguates the company
Article meaning
Who wrote it and what it is called
Machine-readable copy

The business name, the service, the author, the date

A second copy of facts the page already prints
Part 03

Which schema types a cannabis business can use

Our campaign's schema layer includes the types below, each on a specific kind of page.

TypeWhere it belongsWhat to know
Organization, with sameAs and areaServedThe home page or about page, written onceGoogle says "We recommend using the most specific schema.org subtype of Organization that matches your organization."
LocalBusiness, with hours and geoEach store's own pageGoogle's guidance is to "Define each local business location as a LocalBusiness type." Store records are covered on local schema for dispensaries.
ServiceEach service pageNames the service and points to the company that provides it
ArticleGuides, research and blog postsThe author named as a Person or Organization, matching the visible byline
FAQPageOnly pages that print the questions and answersThe Google rich result for FAQs has ended
ProductProduct and menu pagesGoogle's Product snippet guidelines exclude recreational drug content
HowTo, ItemList and DefinedTermStep-by-step pages, grouped lists and glossary entriesLabels a structure the page already shows
SpeakableSpecificationShort passages written to be read aloudMarks which passage answers the question

Review markup carries its own Google limit. The review snippet documentation states: "If the entity that's being reviewed controls the reviews about itself, their pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature." A dispensary or brand that marks up testimonials from its own site gets no stars for them. Our own rule is separate from Google's: nothing in a client's markup is fabricated, so no invented reviews or ratings.

Every type above has its own service page under our schema markup optimization work, and worked examples sit in our cannabis schema guide.

Illustration: Extreme close-up of a cyan brace curling around a lime kernel with light refracting through glass.
Markup restates what the page already prints, which is why schema still earns rich results and entity clarity without being a requirement for AI answers.
Part 04

Why FAQ markup no longer buys a Google rich result

The usual argument for FAQPage markup was the expanded list of questions under a search listing. Google narrowed that feature first. Its documentation changelog records that Google "Updated the FAQ structured data documentation to state that the feature is only shown for well-known, authoritative government and health websites."

Then it ended the feature for every site: "This feature will no longer appear in Google Search starting May 7, 2026." That date has passed. A dispensary, brand or agency page with perfect FAQPage markup gets no FAQ rich result today.

The change covers that one rich result, not FAQ markup as a vocabulary. The earlier announcement put the cost of leaving it in place plainly: "Structured data that's not being used does not cause problems for Search, but also has no visible effects in Google Search." We still mark up FAQ sections that are printed on the page, as a faithful restatement of visible questions and answers, never as a ranking bet. Which questions earn a place, and how to word them, is covered on our FAQ schema page.

Part 05

Product markup and the Google policy limit for cannabis

Cannabis menus run into a content rule that ordinary retail never meets. Google's Product snippet documentation sets guidelines for that rich result: "We don't allow content that promotes widely prohibited or regulated goods, services, or information that may facilitate serious, immediate, or long term harm to people." The following sentence lists what that covers: "This includes content related to firearms and weapons, recreational drugs, tobacco and vaping products, and gambling-related products."

Read the rule at its exact scope. It governs eligibility for the Product snippet result. It does not forbid the Product or Offer vocabulary on a cannabis page, and it says nothing about AI Overviews.

Our own menu measurement is as much about access as about markup. We measured dispensary menu URLs on October 27, 2026, one fetch per URL per method. Raw fetches to the 4 menus hosted on dutchie.com and the 3 on iheartjane.com returned HTTP 403 to both the GPTBot and the browser user agent. A blocked response cannot show what a served menu contains, so the zero Product, Offer or AggregateOffer nodes recorded for those two hosts say nothing about their markup. The GPTBot string was also sent from a non-OpenAI IP address, so a 403 may not match what OpenAI's crawler receives. Across 3 menus hosted on weedmaps.com, none of which returned a 403 to the GPTBot user agent, the median was 0 JSON-LD Product, Offer or AggregateOffer nodes in raw HTML and 1 after rendering. Across 3 Leafly-hosted listings, the median was 159 JSON-LD Product, Offer or AggregateOffer nodes in raw HTML. Samples that small show a pattern, not a platform-wide rate.

Those Leafly nodes describe Leafly's pages, not the store's own website, and a node count says where markup was, not whether Google showed a snippet for it. How menu rendering changes what a crawler receives is explained on our technical AEO page for menus, and the properties that describe a menu item honestly are on our Product schema page.

Part 06

Markup that does not match the visible page breaks Google's guidelines

The general structured data guidelines set the rule in two sentences: "Your structured data must be a true representation of the page content." And: "Don't mark up content that is not visible to readers of the page."

On a cannabis site, those two sentences rule out markup such as:

  • A Service node describing delivery, consultations or a service area that the page copy never mentions.
  • An Article node naming an author the page does not credit, or a modified date that differs from the date printed on the page.
  • A Product node still carrying a price or stock state that the live menu stopped showing.

The fix runs in one direction only. Either the fact goes onto the page, where a reader can see it, or it comes out of the markup.

Markup the page does not support

Service node for delivery the page never mentions
Article author the page does not credit
Modified date that differs from the printed date
Product price the live menu stopped showing
Part 07

How Bud Authority builds and checks the schema graph

The campaign's entity layer carries knowledge-graph sameAs and @id relationships, with one source of truth for name, address and phone across pages and schema. In JSON-LD, an @id lets one node point at another instead of restating it. A minimal graph looks like this, with example.com standing in for the business's own domain:

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "url": "https://example.com/",
      "sameAs": ["https://www.linkedin.com/company/example"]
    },
    {
      "@type": "Service",
      "@id": "https://example.com/services/delivery#service",
      "provider": { "@id": "https://example.com/#organization" }
    }
  ]
}

The Service node names its provider by reference, so the company's details live in one place. Before launch, a three-pass adversarial audit hunts for invalid schema and fabrication. Our Waxx Brandz case file describes the site we designed and built for the California cannabis brand as "Server-rendered Next.js, a full entity and schema graph, AEO/GEO structure".

Part 08

What schema markup cannot fix

Markup restates a page. It cannot supply what the page or the wider web lacks.

It cannot make a thin page worth quoting. A Service node on a page with two vague sentences labels two vague sentences.

It cannot correct facts somewhere else. sameAs links point a parser at the profiles a business controls. They do not change a marketplace listing or directory that shows old hours. The campaign's local work keeps site-to-profile parity for hours, name, address, phone, license and geo, and the wrong surface is the one that gets fixed.

It cannot stand in for the rest of AEO. Crawler access, answer-first writing and citation tracking all sit under answer engine optimization for cannabis businesses, and what AEO is and how it works covers the discipline from the start.

To start, request the free audit, an automated scan with the report card shown on screen. Engagements are quoted after an audit. To see the sites behind this work first, see the Book.

Part 09

Frequently asked questions

Is AEO schema markup different from ordinary schema markup?

It uses the same schema.org vocabulary, usually written as JSON-LD. What changes is the pages it describes. Our campaign's AEO layer builds entity-first pages that open with a citable factual statement, extractable question-and-answer blocks and key facts, and the markup labels those blocks for what they are: a question, an answer, a defined term or a service.

What does Microsoft say Copilot needs from a page?

Content it can take apart. Microsoft Bing product manager Krishna Madhavan writes that "Assistants like Copilot break content down, a process called parsing, into smaller, structured pieces that can be evaluated for authority and relevance." The same post warns that "AI systems may not render hidden content, so key details can be skipped." That is why every fact in our markup also sits in plain, visible text.

Does Organization schema need to go on every page?

No. Google recommends "placing this information on your home page, or a single page that describes your organization, for example the about us page." Its Organization documentation lists no required properties and suggests adding every relevant one. Other pages then refer to that single node by its @id instead of repeating it with slightly different details.

Does passing Google's Rich Results Test mean the markup is right?

It means one check passed. Its help page frames the tool this way: "Put structured data on your page to enable special features in Google Search results, then test it with the Rich Results test." It adds that "All page resources must be accessible by an anonymous user accessing the code from the internet." Matching the markup against the visible page is a separate comparison.

// deploy

Ready to Deploy This Protocol?

Start with a comprehensive audit. We'll map every opportunity and build your custom growth protocol.

> [ INITIATE AUDIT ]
BA://OS