The one link that hides map traffic
Every location listing on Google carries a website link. Many also carry a menu link and one or more food ordering links. When a guest taps one of those from Maps or Search, the visit lands on your site with Google as the referrer and nothing else attached. Analytics files it as organic search, right next to every guest who typed your brand name into a search box.
So the traffic is there. You just can't see it. Map clicks, brand searches and everything else blend into one line, and the per-store question, which listings actually send orders, has no answer. That's our framing from practice, not a measured figure, but it's the pattern we keep finding when we open a restaurant brand's analytics.
The fix is cheap: three checks and one naming rule.
Check 1: audit three listings
Pick three locations: your busiest store, a quiet one, and one a franchisee manages. Open each listing in Google Maps and look at every link a guest can tap.
- Website. The main link on the listing. Copy the URL exactly as it appears.
- Menu. Google lets a profile carry a single menu link.
- Food ordering. Google's help center says a profile can carry up to 10 links per category, and that food ordering links from third-party providers can appear on a listing automatically (Manage your local business links).
An untagged link is a bare address: your homepage or a store page, with no question mark and no campaign values after it. A tagged link carries values such as utm_source, utm_medium and utm_campaign. If all three listings are bare, every click from them is landing in organic search.
Note any third-party ordering links while you're there. Google lets you hide a third-party food ordering provider from the listing, but you can't tag that provider's link, so those clicks never reach your analytics at all.
Check 2: one tagging rule for every location
The values matter less than the rule. Pick one spelling and use it on every listing, because analytics treats a lowercase value and a capitalized one as two different sources. Google's own URL builder guidance makes the same point.
Here's one rule a brand could choose. It's an example, not a standard:
- Source: the business profile, for example
gbp. - Medium: the link type, for example
website,menuororder. - Campaign: the store ID.
The store ID is the part that matters. Use the same key your ordering platform and POS use for that location, not the listing's name. If those systems don't agree on a key yet, settle that first. One Store, One Key walks through it.
Google Business Profile also has a store code field. Google lists it under the profile's Advanced settings and describes it as a way to keep multiple profiles organized (Manage advanced profile settings). Setting the store code to the same key keeps the listing, its links and your order records in step.
Then paste the tagged URL into each link field. After saving, open the listing the way a guest would and tap every link to confirm it still loads the right page.
Check 3: survive the hop to ordering
Most restaurant sites send the guest from the brand site to an ordering site on another domain or subdomain. That's where campaign values most often get lost.
Test the whole path on one store. Tap the tagged order link on the listing, pick the store if you're asked, add an item, and place a test order (or stop at the last step if test orders cost you money). Watch the address bar on every page. A few hours later, find that session in analytics and confirm it's credited to your source and campaign values.
If the values vanish on the ordering domain, the usual causes are a redirect that drops everything after the question mark, or analytics on the ordering site that isn't set up to carry the session across from the brand site. Your Restaurant Website Is Not One Website covers those handoffs.
Watch the store choice too. If the guest arrives tagged for one store and the ordering site resets them to a default location, the order lands on the wrong row of your report.
The month-one table
After a month, build one table with one row per store:
- Store ID.
- Website clicks from the listing, as Business Profile's own performance view reports them.
- Sessions in analytics with your business profile source.
- Orders credited to that source.
- Orders per session.
Don't expect columns two and three to match. Business Profile and your analytics count differently, and an interaction on a listing isn't the same thing as a session on your site. Use the profile numbers as a rough sense of reach and your analytics for what happened after the click.
Then read the gaps. A listing with plenty of sessions and few orders is sending browsers: people checking hours, the menu, or whether you're open on a holiday. That isn't a failure. A listing with few sessions and a steady run of orders is pulling more weight than its traffic suggests. Either way, you now know which is which, store by store.
Limits
- Edits you didn't make. Franchisees, agencies or platforms with access can overwrite a link, and Google can update profile information too. Check the links after any profile change, and on a schedule.
- Bulk tools. If your listings are managed in bulk, set the rule there, or the next sync replaces your tagged links.
- Calls and directions. A guest who calls or asks for directions never touches the website, so none of this measures them.
- Third-party ordering links. They go wherever the provider sends them, without your tags. Orders placed that way are a different kind of record anyway, as Your Own Orders vs Marketplace Orders explains.
- Catering. A catering request that starts from the listing needs its own completion event before any of this can credit it. The Catering Order Nobody Counts covers that path.
None of this needs new software. It's a naming rule and an hour of checking. If you'd like a second pair of eyes on the whole path from listing to order, book a data and tracking audit. To see what loads on your own site before a guest makes a choice, request a free privacy scan; we review each request within 48 hours.
Rawsoft provides technical implementation and analysis, not legal advice. Please confirm any regulatory interpretation with your counsel.