Technical cannabis SEO

Cannabis site architecture divides into hub domain (brand authority), category pages (product grouping), and product pages (revenue generation). Hub domains should accumulate the most site authority, category pages should receive a meaningful share through internal linking, and product pages receive the remainder. This distribution prevents product page fragmentation and ensures category pages rank for broad keywords. URL structure should be /products/category/product-name/. Category pages should be /products/category/. Hub domain should accumulate all brand and authority content. This three-tier architecture prevents internal competition and concentrates authority where it matters most.

Cannabis URL structures must prevent duplicate content from product variants, filters, and marketplace listings. Use clean URLs without parameters: /products/flower/strain-name/ instead of /product?id=123&category=flower. Implement rel="canonical" on all variant pages pointing to primary product page. Use robots.txt to block parameter-based duplicate indexing. Manage marketplace data separately from the primary domain (menu platform data goes to Dutchie and Blaze, not the homepage). Canonical management requires monthly audits in Google Search Console identifying canonicalization issues.

Cannabis mobile optimization requires responsive design, touch-friendly navigation, readable text without zoom, and rapid load times. Test mobile experience with Mobile-Friendly Test and Lighthouse. Common cannabis site mobile problems include non-responsive category filters, unreadable product prices, broken checkout flows, and navigation menus that collapse incorrectly. Implement mobile-specific navigation patterns (hamburger menus, sticky headers, tap-friendly buttons). Test checkout flows on actual mobile devices and various browsers. Mobile optimization often requires site redesigns.

Cannabis structured data includes Product schema (product name, price, image, description, availability, SKU), Offer schema (price, currency, availability, seller information), Review schema (rating, reviewer name, review date, review text), and LocalBusiness schema (address, phone, hours, service area). Implement schema in JSON-LD format (most search engines prefer JSON-LD over RDF or Microdata). Test schema implementation with Google's Rich Results Test to verify validity. Cannabis sites commonly deploy incomplete schema or schema with incorrect field values. Monthly schema audits identify implementation gaps before they impact rankings.

Cannabis Product schema must include product name, description, price (current price only, no sale price markup unless on sale), image URLs (high-resolution images), product category, availability (in stock, out of stock, pre-order), SKU, and aggregate rating (only if genuine reviews exist). For cannabis products, include cannabinoid-specific properties: THC percentage, CBD percentage, cannabinoid profile. Markup must match the visible page, the menu, and the checkout. Missing images and mismatched prices weaken the page and erode shopper trust.

Cannabis data architecture requires centralized product information management feeding multiple destinations simultaneously. Implement a Product Information Management (PIM) system that updates the primary website, the Dutchie API, and the Blaze API. Each platform requires specific field requirements and data validation. Dutchie requires compliance fields (THC%, CBD%, cannabinoid profile) and state-specific pricing. Data errors prevent correct product display on the affected platform. Our cannabis regulatory mapping monitors data health and alerts on validation errors. Automated data management scales without manual intervention.

For cannabis products, put the effort into accurate Product and Offer markup on the dispensary's or brand's own product pages, clean product URLs, and price and availability that match the menu and checkout. Marketplace and menu platform listings (Dutchie, Blaze and similar) follow each platform's own rules. Eligible non-cannabis merchandise, such as apparel and accessories, follows Google's normal product rules.

Dutchie integration requires Dutchie Developer API access, authentication credentials, and product data mapping. Blaze integration requires similar API setup. Both platforms require real-time inventory synchronization (frequent, automated syncs) and pricing updates. Integration requires back-end development expertise. Manual feed updates cause inventory discrepancies. Incorrect mapping causes products to appear with wrong prices or availability. Both platforms provide integration documentation but implementation typically requires developer support.

Cannabis XML sitemaps should include all public product pages, category pages, and content pages. Sitemaps should be submitted to Google Search Console and included in robots.txt. Update frequency hints (weekly, daily) help search engines prioritize crawling. Sitemaps must be valid XML and include all required fields (URL, lastModified, changefreq). Large cannabis sites need sitemap indexes breaking products into smaller sitemaps. Automated sitemap generation prevents manual updates from breaking sitemap validity. Sitemaps with errors prevent search engines from discovering new products. Monthly sitemap validation prevents indexing delays.

Cannabis sites should minimize redirects to 1-2 hops maximum. Redirect chains (301 to 301 to final URL) waste crawl budget and degrade authority transfer. Track all 301 redirects and consolidate redirect chains. Temporary redirects (302) should be converted to 301s if permanent. Redirect audits identify chains for consolidation.

All cannabis sites must use HTTPS (not HTTP). Install valid SSL certificate covering all domain variations (www and non-www). Implement HSTS (HTTP Strict Transport Security) header forcing browser-level HTTPS enforcement. Test SSL configuration with SSL Labs. Monitor certificate expiration and renewal automatically. Mixed content (HTTPS pages loading HTTP resources) breaks HTTPS and triggers security warnings. Audit all image, script, and stylesheet URLs to verify HTTPS.