The short answer
Fix the route to the right store before creating more local content. Check the location page, current store facts and final menu destination together. Assign an owner to each problem, and keep menu clicks separate from verified purchases.
Follow the shopper beyond the location page
Start from a search result, a direct location link and the homepage. A path that works from one entrance can still send another visitor to the wrong store. Follow the handoff into the menu instead of stopping at the WordPress button.
Choose a real location
- Evidence
- The page names the selected store and makes switching locations clear.
- Watch for
- A generic page or old link leaves the store uncertain.
Confirm the visit
- Evidence
- Store-approved hours, address, directions and contact information are easy to find.
- Watch for
- A stale notice contradicts the current operation.
Open that store’s menu
- Evidence
- The final destination retains the intended store on desktop and phone.
- Watch for
- The link opens another store, loses context or fails to load.
Verify the outcome you can observe
- Evidence
- The provider’s order record establishes a purchase when reporting access supports it.
- Watch for
- A menu-button click is labeled as an order.
Also test changing stores and returning through a saved menu URL. Cart and selection behavior depend on the actual provider and implementation.
One real store. Answers a visitor can use.
A shared WordPress template can keep the design consistent while each store supplies useful local facts. Add verified parking, entrance or access details and answers to questions staff actually receive. Replacing a city name in generic copy does not make a useful new page.
Check the website and local profile together. Google’s Business Profile guidelines call for accurate real-world business information. Temporary notices need an owner, effective dates and a removal step.
Identify the store and action
Keep the store identity close to visit and menu controls so the next step has context.
Answer practical visit questions
Give address, contact and hours a consistent home. Operations must own their accuracy.
Explain the ordering path
Show what happens next. Check the connected menu instead of assuming the website explains the whole journey.
Keep these facts current
- Approved store name, address, hours and contact route.
- Correct menu destination and supported shopping path.
- Useful directions, parking or entrance details.
- Temporary notices with start, end and removal owners.
Inspect the menu connection you actually have
WordPress may manage the content website while another system owns menus, catalog data and transactions. A WordPress dispensary website is not automatically a WooCommerce store. Describe the systems and responsibilities accurately.
Document whether each journey uses an external link, an embed, connected catalog pages or a combination. Test direct arrivals, mobile loading, store switching and the return path. If the provider is unavailable, record what customers see and who responds.
Find the first point of failure: a wrong button destination may belong to WordPress; incorrect availability may originate in the menu or inventory system. Route the example to the team that can change it.
Inspect the URLs that matter to each store
List the location page, final menu destination and any catalog URLs the business expects people to find. Identify which system and team control each one.
Google’s JavaScript SEO guidance distinguishes discovery, rendering and indexing. Ask the relevant owner to inspect the important URLs and useful content. A customer-facing screenshot cannot establish indexing, and indexing cannot guarantee a ranking.
Use the result to choose the fix. A broken location link, an undiscoverable store page and a provider-controlled catalog problem require different work. Blanket claims about a menu platform are less useful than evidence from the affected URL.
Retain a short evidence record
- Public location URL and final menu destination.
- Team with access to inspect and change each URL.
- Observed indexing or destination issue, with date.
- Unverified areas and the next responsible owner.
Give every change a named owner
One location register should connect the approved fact, system, change owner and final check. A store-hours change may touch the website, profile and menu platform; a coordinator closes the loop across all three.
| Information or journey | Authority and change owner | Verification to retain |
|---|---|---|
| Store name, address, and hours | Store or operations approver; named website and profile editors. | Approved facts, effective date, and checked public destinations. |
| Menu destination and store selection | Operations confirms the store; website developer and menu provider own their respective settings. | Location page URL, final menu URL, selected-store behavior, and test date. |
| Catalog and availability information | The actual system and staff role that control the source data. | Affected record, where the discrepancy first appears, and escalation owner. |
| Temporary notices | Business approver and publisher, with an assigned removal owner. | Start and end dates, affected pages, and confirmation of removal. |
| Measurement | Measurement owner coordinates supported website and provider reporting. | Event definition, destination, coverage limits, and whether an order can be verified. |
| Access and provider changes | Business account owner and transition coordinator. | Access inventory, support contacts, recovery route, and accepted handoff. |
A menu click and a purchase answer different questions
Define each measure before reporting it. If measurement stops at the provider handoff, state that limit. Matching totals or timing alone does not prove that a website visitor became a purchaser.
Menu action
- What it shows
- A tracked button action from an originating page toward a named store and destination.
- What to verify
- Event definition, store context, duplicate firing and coverage under supported consent states.
- What it cannot establish
- A completed order, purchase value or fulfilled transaction.
Verified order
- What it shows
- An order in the provider’s reporting under the agreed completion definition.
- What to verify
- Order status, cancellations, refunds, location and reporting period.
- What needs another check
- Attribution to a website action requires a valid connection between the records.
Report by store where the data supports it
Keep discovery, visits, menu actions and verified orders separate. Add operational context such as a closure, changed hours or provider outage.
A completed example: fix the mismatch before adding pages
This hypothetical three-store review illustrates prioritization; it is not an AV Social Strategies client result. Leadership requests more local content, but the review identifies three operating problems first.
| Finding | Action and owner | Evidence to accept |
|---|---|---|
| Store A’s menu button opens Store B. | Operations confirms the correct destination; the website owner repairs the link. | Direct entry, mobile and store-switching tests all retain Store A. |
| Store B still shows an expired holiday notice. | The store manager approves current hours; the publisher corrects all affected surfaces and assigns notice removal. | Website, profile and menu agree with the approved current hours. |
| All menu clicks are reported as orders. | The measurement owner relabels clicks and checks provider reporting access. | Report separates menu actions from verified orders and states any attribution gap. |
Review the journey after changes, then on a regular rhythm
A monthly review is a practical starting point, not a universal rule. Store moves, new menu destinations, provider changes and temporary notices deserve their own checks. Keep the date, evidence, owner and unresolved issues together.
Monthly location-to-menu review
- Check each location's approved information against its public page and relevant profile.
- Follow the menu path from each location page and confirm the intended store.
- Review direct menu arrivals, mobile behavior, location switching, and known exceptions.
- Remove expired notices and confirm upcoming changes have owners.
- Inspect available measurement and label the boundary between clicks and verified orders.
- Assign every unresolved issue an owner, next action, and verification date.
How to use the review and client examples
The register is an operational review of your actual stores and systems. Google's sources support the profile and search-inspection guidance. Share and Maribis illustrate AV Social Strategies’ documented delivery responsibilities; neither is presented as a controlled test of one location page, menu provider, or SEO tactic. Keep historical project artwork separate from current store information, and use your store owners' approved facts for today's review.
Build an improvement plan around the stores you operate
Start with the stores you operate, their website and menu destinations, and the problems customers or staff repeat. Those inputs help separate content work from a broken handoff, an ownership gap or a measurement problem.
Explore our cannabis website approach, WordPress services or discuss the stores and systems involved. The next step is to define the scope and evidence needed for a focused improvement plan.
Sources and further reading
Google’s documentation supports the profile and search guidance. Share and Maribis are documented delivery examples; the three-store review is hypothetical. Historical artwork does not establish current store information or performance.
