Every local shop I have talked to in the last month believes it already has a website: the Google Business Profile. It has photos, hours, reviews, a phone number and a pin on the map. What it does not have is a field for the four things a customer asks before walking in.
I build a one-page site generator for shops (MapToSite, free, no account), so this is the list I keep running into.
What a Google listing holds, and what it does not
| Customer question | In the Google listing | Reality |
|---|---|---|
| How much? | "Menu" link, often a PDF or a photo | No price field. A price list is a file, not data. |
| How long will it take? | — | No duration field. A 20-minute cut and a 3-hour colour look identical. |
| Can I just walk in? | — | No walk-in policy. The shop answers this on the phone, 40 times a week. |
| What if I cancel? | — | No deposit or cancellation terms. |
| Do you speak my language? | — | No language field. |
None of these are exotic. They are the questions that generate the phone calls a two-person shop cannot answer while serving the customer in front of them.
The "link in bio" page is not the answer either
Instagram captions cannot hold a clickable link, so a shop's bio link is the only tap a customer gets. Most of those links point at a link-list page: a vertical stack of buttons, priced per month, with no field for a price, a duration or a closing time.
So the customer taps twice — once to reach the list, once to reach the thing they wanted — and the second tap is where a meaningful share of them leave. If you build for shops, the highest-leverage fix is: one page, owned by the shop, that answers price, hours, location and phone before the visitor taps anything.
What that page needs, technically
Nothing complicated, which is why it is annoying that so few shops have one:
-
A
tel:link on the number, pinned where the thumb lands. A number in plain text costs the shop a copy-paste. - Hours in text, not an image. A photo of a sign is invisible to a crawler and unreadable on a cracked screen.
- Prices as text. A PDF menu is 4 MB of nothing for search and painful on a phone.
-
schema.org/LocalBusinesswithopeningHoursSpecification,priceRange,telephoneandaddress. This is what puts hours into the result instead of a link. - The listing's website field pointing at the shop's own page — not at Yelp, not at a link list, not at an ordering app. That field is a backlink the shop already owns and usually gives away.
- A URL the owner can say out loud and print on a receipt.
You can do all of that by hand in an afternoon. The reason shops do not is that "an afternoon" is not a resource they have, and the person who would do it is the same person covering the counter.
The 30-second version
The page I build takes the four facts the owner already knows — name, hours, prices, phone — and emits the six things above: tap-to-call, today's hours, a price list, directions, a share card, and LocalBusiness JSON-LD. Nothing to install, no account to view the result, and the free plan keeps a small footer.
- Try it on a shop you know: maptosite-app.pages.dev
- A finished example page, a taqueria: taqueria-fenix
It is early access, built solo in Busan, and it has no customer case studies yet — so I am not going to show you one. If you build for local businesses, the interesting argument is not whether shops need a page. It is that the listing and the bio link both look like the job is done, which is why nobody finishes it.
Disclosure: I work on MapToSite. Every price quoted is a platform's own published price, read in November 2026.
Top comments (0)