Schema Markup for Dispensaries
The Complete Structured Data Guide

Search engines do not read your website the way a human does. A person visiting your dispensary homepage can immediately identify your business name, address, phone number, and operating hours from visual layout and context. Google's crawler sees HTML. Without explicit structured data telling it what each piece of information represents, Google is guessing, and guessing means your dispensary misses opportunities for enhanced search visibility that your competitors may already be capturing.

Schema markup is the standardized vocabulary that eliminates that guessing. It is code you add to your pages, invisible to visitors, that tells search engines exactly what your content means: this is a local business, this is its address, these are its hours, this is a frequently asked question and here is the answer. When implemented correctly, schema markup enables rich results in Google search, feeds AI search engines the structured context they need to cite your dispensary, and strengthens every other SEO signal on your site.

For cannabis dispensaries specifically, schema markup is not optional. It is one of the most important technical SEO investments you can make, and this guide explains exactly why and how to implement it.

What Is Schema Markup and How Search Engines Use It

Schema markup is a vocabulary of tags, maintained by Schema.org, that you add to your website's HTML to provide search engines with explicit, machine-readable information about your content. Instead of hoping Google can infer that "123 Main Street" is your business address, schema markup wraps that text in a structured format that says: this is a PostalAddress belonging to a LocalBusiness with this specific name and these specific coordinates.

The most common format for schema markup is JSON-LD (JavaScript Object Notation for Linked Data). JSON-LD is Google's recommended format because it is a standalone script block placed in your page's head or body section, completely separate from the visible HTML. You do not need to modify your page content or layout to add JSON-LD schema. It sits in a script tag and communicates directly with search engine crawlers.

When Google encounters valid schema markup, it can use that structured data to generate rich results: enhanced search listings that display additional information beyond the standard blue-link format. Rich results can include star ratings, business hours, FAQ dropdowns, breadcrumb navigation trails, product pricing, and more. These enhanced listings occupy more visual space in search results and consistently produce higher click-through rates than standard listings.

Schema markup also feeds Google's Knowledge Graph, the database of known entities (people, businesses, places, concepts) that powers the information panels appearing on the right side of search results. A dispensary with complete Organization and LocalBusiness schema has a significantly higher chance of generating a Knowledge Graph panel for branded searches than one relying on Google to piece together information from scattered sources.

Why Schema Matters More for Cannabis Than Other Industries

Every local business benefits from schema markup. But for cannabis dispensaries, structured data is disproportionately valuable because of the unique constraints the industry faces in digital marketing.

Cannabis businesses cannot run Google Ads. Google prohibits advertising for cannabis products across its entire advertising network: Search, Display, YouTube, Shopping. Meta restricts cannabis advertising on Facebook and Instagram to the point of near-impossibility. The paid advertising channels that most retail businesses use to dominate search results pages are unavailable to dispensaries.

That restriction means organic search results are the only Google real estate available to your dispensary. Within those organic results, rich results powered by schema markup are the highest-visibility format. A dispensary that earns FAQ dropdowns, breadcrumb trails, and business information panels in its organic listings captures significantly more attention and clicks than a competitor showing a plain blue link with a meta description.

AI search is replacing traditional results for many cannabis queries. Google AI Overviews, ChatGPT with browsing, Perplexity, and other AI search tools are increasingly answering cannabis questions directly. These AI systems rely heavily on structured data to identify authoritative sources worth citing. A dispensary with complete schema markup is providing these AI systems with machine-readable proof of what it is, where it is, and what it knows about cannabis. Dispensaries without schema are invisible to these systems.

Rich results are free real estate on the search results page. A dispensary that implements FAQPage schema can have its FAQ answers appear as expandable dropdowns directly in Google search results. That FAQ rich result pushes competitors further down the page while giving your dispensary multiple lines of additional visibility. No advertising budget can buy that position; only correctly implemented schema can earn it.

LocalBusiness Schema: The Foundation for Every Dispensary

LocalBusiness schema is the single most important schema type for any dispensary. It tells Google exactly what your business is, where it is located, when it is open, how customers can contact it, and what services it provides. This schema belongs on your homepage and on every location-specific page if you operate multiple dispensaries.

Essential LocalBusiness Properties

A complete LocalBusiness schema for a dispensary should include every property that Google can use to populate your Knowledge Graph panel and local search listings. Here is what each property communicates:

• @type: Use "LocalBusiness" as the primary type. You can add additional types like "Store" or "MedicalBusiness" if your dispensary holds a medical license, but LocalBusiness is the baseline Google expects for map pack and local search features.
• name: Your official business name exactly as it appears on your signage and business license. Do not add keywords like "Best Dispensary" or "Cannabis Store" to your schema name. Google treats name-keyword stuffing in schema the same way it treats it in Google Business Profile: as a policy violation.
• address (PostalAddress): Your full street address broken into structured components: streetAddress, addressLocality (city), addressRegion (state), postalCode, addressCountry. Each component in its own field, not a single concatenated string.
• telephone: Your primary business phone number in E.164 format with country code, such as +12125551234. This must match your Google Business Profile and all directory listings exactly.
• openingHoursSpecification: Your operating hours for each day of the week, specifying dayOfWeek, opens time, and closes time. Include separate entries for each day rather than grouping days, because Google can display individual day hours in Knowledge Graph panels.
• geo (GeoCoordinates): Your dispensary's exact latitude and longitude. This helps Google confirm your physical location and strengthens map pack relevance for nearby searches. Use coordinates accurate to at least four decimal places.
• areaServed: The geographic areas your dispensary serves. List specific neighborhoods, boroughs, and cities within your delivery or service radius. This tells Google which local searches your business is relevant for beyond your immediate physical location.
• priceRange: A general indication of your price level using dollar signs ($, $$, $$$). Google can display this in local search results to help users understand your positioning.
• paymentAccepted: List the payment methods your dispensary accepts: "Cash," "Debit Card," "ACH." Cannabis businesses have unique payment constraints that customers actively search for, so this property directly answers a common buyer question.

Additional Properties That Strengthen Your Schema

Beyond the essentials, several additional LocalBusiness properties can further improve how Google represents your dispensary in search results:

• sameAs: Links to your official social media profiles and directory listings (Instagram, Weedmaps, Leafly). This helps Google confirm your identity across platforms and can populate your Knowledge Graph panel with social links.
• hasMap: A direct link to your Google Maps listing. Reinforces the geographic connection between your schema and your map pack presence.
• image: A high-quality photo of your storefront. Google may display this image in Knowledge Graph panels for branded searches.
• description: A concise, keyword-rich description of your dispensary. Keep it factual and specific: what you sell, where you are, what makes you different.

FAQPage Schema: Turning FAQs Into Rich Results

FAQPage schema is arguably the highest-return schema type for dispensaries. When Google recognizes valid FAQPage markup, it can display your questions and answers as expandable dropdown items directly in search results. Each expanded FAQ answer adds multiple lines of text to your search listing, pushing competitors down the page and dramatically increasing your visual footprint.

Cannabis dispensaries have a natural advantage here because prospective customers have many questions about legal cannabis: What ID do I need? Is cannabis legal in my state? What payment methods are accepted? What is the difference between indica and sativa? Each of these questions is a FAQPage schema opportunity.

How to Structure FAQPage Schema

FAQPage schema requires a specific nesting structure. The page-level type is "FAQPage," and it contains a "mainEntity" array of Question objects. Each Question contains a "name" property (the question text) and an "acceptedAnswer" object with the answer text.

Best Practices for Dispensary FAQs

• Match your schema questions exactly to the visible FAQ content on the page. Google requires that FAQ schema content be visible to users, not hidden in schema only.
• Target questions people actually search for. Use Google's "People also ask" and autocomplete suggestions for cannabis topics to identify high-volume question queries.
• Keep answers between 40 and 150 words. Answers that are too short lack substance; answers that are too long get truncated in rich results and lose impact.
• Include 3 to 8 FAQ items per page. Google rarely displays more than 4 in rich results, but having additional FAQs on the page strengthens the topical depth signal.
• Use natural language that matches how people phrase questions. "What payment methods do dispensaries accept?" outperforms "Dispensary payment methods accepted" as a question format.

Article Schema for Blog Content

Every blog post and educational page on your dispensary website should include Article schema. This markup tells Google that the page contains editorial content and provides structured information about the headline, author, publisher, publication date, and modification date.

Article schema helps Google understand the recency and authority of your content. A blog post with Article schema showing a recent datePublished and dateModified signal is treated as current, relevant content. Without Article schema, Google must infer these signals from less reliable sources like HTTP headers or sitemap dates.

Key implementation details: The headline property should match your page's H1 tag. The datePublished should be the original publication date in ISO 8601 format (YYYY-MM-DD). Update dateModified whenever you make substantive edits to the content. The author can be an Organization or Person type depending on whether you attribute content to your brand or to individual team members.

For dispensaries publishing educational content about cannabis strains, legal information, or buyer guides, Article schema is especially valuable because it establishes your content as authored editorial work rather than anonymous web copy. Google and AI search systems prioritize content with clear authorship and publisher attribution.

BreadcrumbList Schema: Navigation Rich Results

BreadcrumbList schema defines the hierarchical path from your homepage to the current page. When Google displays breadcrumb rich results, the URL in your search listing is replaced with a readable navigation trail: Home > Blog > Schema Markup Guide. This makes your listing more visually informative and helps users understand where the page sits within your site structure before they click.

Breadcrumb rich results also reduce pogo-sticking (users clicking back to search results immediately) because they set clearer expectations about what the user will find. If a user sees "Home > Products > Edibles" in the breadcrumb trail, they know before clicking that they are going to a product category page, not a blog post or location page.

Implement BreadcrumbList schema on every page of your dispensary website. The structure should mirror your actual site navigation hierarchy. For dispensaries with multiple locations, breadcrumbs might follow: Home > Locations > Brooklyn > Menu. For blog content: Home > Blog > Article Title. The key is consistency: every page should have a breadcrumb path that reflects its position in your site architecture.

Organization Schema: Establishing Your Dispensary as a Known Entity

Organization schema tells Google that your dispensary is a recognized business entity with specific attributes: a legal name, a logo, contact information, social media profiles, and a physical location. This schema is distinct from LocalBusiness in that it focuses on your brand as an entity rather than your physical store as a place.

The most important function of Organization schema is connecting your dispensary's various online presences into a single, coherent entity in Google's Knowledge Graph. When you include sameAs links to your Instagram, Weedmaps, Leafly, and Yelp profiles, Google can associate all of those profiles with a single business entity, strengthening the authority and trustworthiness signals for all of them.

• name and legalName: Your official business name and registered legal entity name if different.
• logo: URL to your high-resolution logo image. Google may display this in Knowledge Graph panels.
• contactPoint: A structured object specifying your customer service phone number, contact type, and available languages.
• sameAs: An array of URLs to your official profiles on social media platforms, directories, and industry sites. This is how Google connects your web presence into one entity.
• foundingDate: When your dispensary was established. Longevity signals trustworthiness to both Google and users.

Place Organization schema on your homepage or about page. It should be implemented once per brand, not repeated on every page. If you operate multiple dispensary locations under a single brand, use one Organization schema for the brand and separate LocalBusiness schema instances for each physical location.

Product Schema: What You Can and Cannot Mark Up

Product schema is the most powerful schema type for e-commerce businesses. It enables rich results showing product names, prices, availability, and reviews directly in Google search listings. For most retailers, implementing Product schema is straightforward and high-impact.

For cannabis dispensaries, Product schema requires careful consideration because of Google's policies on cannabis-related content.

What You Can Safely Mark Up

• Non-cannabis merchandise: Accessories, apparel, branded merchandise, consumption devices, and storage products can use full Product schema with pricing and availability without compliance risk.
• Cannabis product categories: You can describe product categories (flower, edibles, concentrates) as general merchandise categories without specific pricing or purchase availability signals. Use descriptive text about the category rather than individual product listings.
• Brand and manufacturer information: Schema describing cannabis brands you carry, their origin, and their product philosophy is generally safe because it describes entities rather than purchasable products.

What to Approach Cautiously

• Individual cannabis product listings with specific pricing, SKUs, and "in stock" availability signals carry the highest compliance risk. These mirror the product advertising data that Google explicitly prohibits for cannabis.
• Offers schema (pricing and purchase availability) attached to cannabis products is the specific trigger that most commonly causes policy reviews.
• Review and AggregateRating schema on individual cannabis product pages can attract scrutiny if Google interprets them as product promotion.

The safest approach for most dispensaries is to focus schema implementation energy on LocalBusiness, FAQPage, Article, and BreadcrumbList, which carry zero compliance risk and deliver strong SEO value. Use Product schema for non-cannabis merchandise only, and monitor Google Search Console for any manual action notifications if you do implement Product schema for cannabis items.

AI-Specific Schema Signals: Feeding AI Search Engines

Traditional schema markup targets Google's structured data parser. But a growing share of cannabis search queries are now answered by AI systems: Google AI Overviews, ChatGPT with browsing, Perplexity AI, and Bing Copilot. These systems consume structured data differently from traditional search engines, and dispensaries can optimize for both audiences simultaneously.

How AI Systems Use Your Schema

When an AI search engine processes your page, it reads both the visible content and the structured data in your schema. The schema provides machine-readable context that helps the AI system understand:

• What type of entity created this content (Organization schema identifies you as a business, not an anonymous website)
• When the content was published and last updated (Article schema datePublished and dateModified)
• Where this business operates (LocalBusiness geo coordinates and areaServed)
• What questions this content authoritatively answers (FAQPage schema with specific Q&A pairs)
• How this page relates to the broader site structure (BreadcrumbList schema)

AI systems use this structured context to make citation decisions. When Perplexity is answering "what payment methods do dispensaries accept," a page with FAQPage schema containing that exact question and a well-structured answer is significantly more likely to be cited than a page where the same information is buried in a paragraph without structured markup.

Meta Tags That Work Alongside Schema for AI

In addition to schema markup, several meta tags can signal to AI crawlers that your content is available for citation:

• ai-citation meta tag: Specifies the canonical URL that AI systems should use when citing your content. Ensures citations link to the correct page.
• ai-content meta tag: Identifies the content creation method (human-written, AI-assisted, human-and-ai-collaborative). Transparency about content creation builds trust signals.
• ai-license meta tag: Indicates whether your content is available for AI training and citation, and under what terms.
• max-snippet:-1 in robots meta: Allows search engines and AI systems to use unlimited-length snippets from your content, maximizing the chance of detailed citations.

Testing and Validating Your Schema Markup

Implementing schema markup without testing it is like publishing a website without checking whether it loads. Schema syntax is strict: a missing comma, an incorrect property name, or a mismatched type can invalidate your entire structured data block, making it invisible to search engines despite being present in your code.

Google Rich Results Test

Google's Rich Results Test (search.google.com/test/rich-results) is the primary validation tool. Enter your page URL or paste your schema code directly, and the tool shows which rich result types your schema is eligible for, any errors that prevent rich results, and any warnings that may reduce effectiveness. Every schema implementation should pass this test with zero errors before going live.

Schema Markup Validator

The Schema Markup Validator (validator.schema.org) checks your markup against the full Schema.org vocabulary, not just the subset Google supports for rich results. This catches issues like deprecated properties, incorrect data types, and structural problems that the Rich Results Test may not flag. Use this as a secondary validation step.

Google Search Console Validation

After deploying schema to your live site, monitor the Enhancements section of Google Search Console. It shows how Google is processing your structured data across your entire site, including any pages with errors, pages with valid but enhanced schema, and counts of items detected. Check this weekly for the first month after implementation, then monthly thereafter.

Schema Implementation Strategy: Prioritized Rollout

Implementing schema across an entire dispensary website is a project, not a task. Trying to add every schema type to every page simultaneously leads to errors, incomplete implementations, and validation failures. A prioritized rollout produces better results.

Phase 1: LocalBusiness and Organization (Week 1)

Start with LocalBusiness schema on your homepage and any location pages. Add Organization schema to your homepage or about page. These two types establish your dispensary's identity in Google's Knowledge Graph and directly impact your map pack and local search visibility. Validate both in Rich Results Test before moving to Phase 2.

Phase 2: BreadcrumbList Site-Wide (Week 2)

Implement BreadcrumbList schema across every page of your site. If your site uses a CMS or template system, this can often be automated through the template. Breadcrumb schema is low-risk and low-complexity, making it an efficient second phase. It also helps Google understand your site structure, which benefits the crawling and indexing of all your other content.

Phase 3: FAQPage on Key Pages (Weeks 3 to 4)

Identify the 5 to 10 pages on your site that contain or should contain FAQ content: your homepage, location pages, product category pages, and any educational guides. Write 3 to 5 high-quality FAQ items per page targeting questions people actually search for. Implement FAQPage schema for each, validate, and deploy. This phase delivers the most visible rich results impact.

Phase 4: Article Schema for Blog Content (Week 5)

Add Article schema to every blog post and educational page. If your blog uses a CMS template, implement this at the template level so all existing and future posts automatically include Article schema. Include accurate datePublished and dateModified values for every post.

Phase 5: Ongoing Monitoring and Expansion (Continuous)

After the initial four-phase rollout, monitor Google Search Console for errors and opportunities. Add schema to new pages as they are published. Consider implementing Event schema for dispensary events, Review schema for testimonials, and expanding your FAQ coverage as you identify new question-based queries driving traffic.

Common Schema Mistakes Dispensaries Make

Schema markup implementation errors are common because the format is strict and the documentation is technical. These are the mistakes we see most frequently on dispensary websites:

1. Schema Content That Does Not Match Visible Page Content

Google requires that schema markup reflect content that is visible to users on the page. FAQ schema with questions and answers that do not appear anywhere in the page's visible HTML is a policy violation. Google will ignore the schema and may issue a manual action. Every FAQ in your schema must appear as visible text on the page.

2. Inconsistent Business Information Across Schema and Other Sources

Your schema markup business name, address, phone number, and hours must exactly match your Google Business Profile, your website's visible content, and all directory listings. Schema that says your hours are 9 AM to 9 PM while your GBP says 10 AM to 10 PM creates a conflicting signal that can suppress both your organic and local rankings.

3. Using Microdata or RDFa Instead of JSON-LD

Google explicitly recommends JSON-LD as the preferred structured data format. While microdata and RDFa are technically valid, they are embedded within your HTML and are harder to maintain, debug, and validate. JSON-LD lives in a standalone script tag, completely separate from your visual content, making it cleaner to implement and easier to update without risking layout changes.

4. Not Updating dateModified When Content Changes

Article schema includes a dateModified property that tells Google when the content was last substantively updated. If you update a blog post's content but leave dateModified unchanged, Google may not recrawl the page with the same priority. Always update dateModified in your schema when you make meaningful content edits.

5. Implementing Schema Without Validation

A single syntax error, a missing comma or an unclosed bracket, invalidates your entire JSON-LD block. Google silently ignores invalid schema. You will not see an error message on your page. The only way to catch these issues is to test with the Rich Results Test before deployment and monitor Search Console after deployment. Dispensaries that skip validation often have months of broken schema without realizing it.

6. Keyword Stuffing in Schema Properties

Adding keywords to your business name ("Best Cannabis Dispensary NYC | Your Store Name"), stuffing your description with keyword lists, or padding FAQ answers with unnaturally repeated search terms violates Google's structured data guidelines. Schema should be factual and descriptive, not optimized for keyword density. Google's systems are specifically trained to detect keyword manipulation in structured data.

Frequently Asked Questions

Where to Start

If your dispensary website currently has no schema markup, start with LocalBusiness schema on your homepage. This single implementation establishes your dispensary's identity in Google's Knowledge Graph, strengthens your map pack signals, and provides the foundation for all other schema types. It can be implemented in under an hour and tested with the Rich Results Test in minutes.

After LocalBusiness, add FAQPage schema to your most important pages. Identify the 5 most common questions your budtenders answer every day. Write clear, substantive answers. Add the FAQ content to your page as visible text, implement FAQPage schema, and validate. This combination of LocalBusiness and FAQPage covers the two highest-impact schema types with the least implementation complexity.

Schema markup is not a one-time project. It is infrastructure that should be maintained, expanded, and monitored as your site grows. Every new page should include appropriate schema. Every content update should include a dateModified update in Article schema. Every new location should get its own LocalBusiness instance. The dispensaries that treat structured data as an ongoing discipline, rather than a one-time technical fix, build a compounding advantage in both traditional and AI search visibility.