How to Build a Cannabis WordPress Website That Can Actually Launch

1. Start with the site customers need

Choose a domain customers can spell, staff can say out loud, and Google can associate with the brand or location. Before design starts, map the pages customers will look for first: home, menu or products, locations, about, education, contact, policies, and campaign 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 hosting that accepts the category

Cheap WordPress hosting is easy to find. 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. Keep WordPress maintainable

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 real reason to own that complexity.

4. Install plugins with restraint

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. Decide how the menu should work

Dispensary menus can be embedded quickly, but native or proxy-backed 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. Add ecommerce only after 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 build the website path; operators own compliance.

7. Write pages for real shoppers

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

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. Treat 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.