How to Build a Cannabis-Friendly WordPress Website

1. Plan the domain and site structure

Choose a domain that customers can spell, staff can say over the phone, and Google can associate with your brand or location. Map the first version of the site before design: home, menu or products, locations, about, blog or education, contact, policies, and campaign landing pages.

• Use city/location pages for dispensaries with local search intent
• Reserve product education pages for brands and where-to-buy journeys
• Document DNS ownership, registrar access, and rollback contacts before launch

2. Choose cannabis-friendly WordPress hosting

Generic WordPress hosting may be inexpensive, but the real question is whether the host understands cannabis content, age gates, menus, regulated claims, and migration risk. BakedPress is self-hosted WordPress infrastructure for cannabis operators, not an Automattic-hosted store constrained by the same product policy layer.

3. Install WordPress and choose a maintainable theme

Start with a clean WordPress install, SSL, backups, admin access, and a theme that is mobile-responsive, accessible, and easy for staff to update. Avoid heavy builders unless the team has a reason to own that complexity.

4. Install essential plugins deliberately

The typical cannabis stack starts with SEO, forms, analytics, age verification, security, caching, and menu integration. Keep the plugin list short and documented. Every plugin should have an owner, a reason, and a test path.

• Use the age verification guide before publishing regulated content
• Configure SEO titles, local schema, and XML sitemap submission
• Test contact forms, lead capture, and notification routing before launch

5. Plan menus and POS hand-offs

Dispensary menus can be embedded quickly, but native or proxy-backed menu integrations can help product pages live on the operator domain with better metadata and search value. Review Dutchie, Jane, Alleaves, and POS hand-offs before deciding on the menu architecture.

6. Configure ecommerce only after compliance review

WooCommerce can support catalog and order workflows, but regulated product sales require legal review, age verification, market rules, payment processor approval, product labeling, fulfillment rules, privacy policy, and staff workflow. BakedPress can plan the infrastructure; operators own compliance.

7. Build useful content and navigation

Create pages customers actually need: store hours, menus, pickup or delivery expectations, product education, events, FAQs, policies, contact paths, and location details. Keep navigation simple and write page titles around real customer searches.

8. Launch with QA, analytics, and Search Console

Before DNS cutover, test SSL, redirects, age gates, forms, menus, tracking, mobile layouts, page speed, login, backups, and rollback. After launch, submit the sitemap in Google Search Console and verify analytics events.

9. Maintain the site like an operating asset

WordPress is not one-and-done. Keep core, themes, and plugins updated; monitor uptime and forms; review menu behavior; publish useful local content; and revisit compliance language when markets or products change.