Someone in the passenger seat says "hey Siri, find Thai food near me." The car reads back three names. Your restaurant is one of them, with a phone number from the previous tenant of your building, hours that were accurate in 2021, and no photo.
None of that comes from your Google listing. Apple maintains its own place database, and it is what every iPhone reads in Maps, Siri, Spotlight, and any address tapped in a text message. If you have never logged into Apple Business Connect, there is a record about your restaurant that you have never seen and did not write.
The two databases do not talk to each other
This is the part operators find genuinely surprising. Fixing your hours on Google does nothing to your Apple listing. Adding photos to Google does nothing to your Apple listing. They are separate systems with separate verification, separate data sources, and separate errors.
Apple builds its place data from a mix of licensed data providers, its own mapping work, and business-submitted information. For an unclaimed restaurant, that means the record is assembled from third parties, which is why the phone number on an unclaimed listing is so often wrong in a specific way: it is correct for whoever occupied the address before you.
The practical consequence is a class of missed calls you have no way to see. The customer dialed a number, got a disconnected tone or a nail salon, and moved on to the next result. That call never appears in any report you have. It is the invisible loss described in the real cost of a missed call, with an added twist: you cannot even fix it by answering the phone better, because the phone never rang.
Claiming it, and the one step that trips people up
The process is free and reasonably quick. You create a business account, search for your restaurant, and claim the listing. Verification happens through a call or email to the business, or through documentation if the automated path fails.
The step that catches people is the verification call. It goes to the phone number on record, and someone has to answer it during business hours. Restaurants that let the phone ring through to voicemail during a lunch rush regularly fail this on the first attempt and assume the tool is broken. Have someone available and expecting it.
If the number on the unclaimed record is wrong, the email or document route is the way through. Expect a few days rather than an hour.
What to fill in, and what to leave
Once you have control, the fields worth your time are short.
- The phone number, matched exactly to what your Google listing and your website say, for the reasons in name, address, and phone consistency
- Hours, including the closed days and any kitchen-closes-before-the-bar split, since Siri reads these aloud
- The pin location, which for restaurants in strip malls or on corners is frequently dropped in the parking lot or on the wrong side of the street
- Photos of the room and the food, taken recently, because the place card shows them at a size where a dark 2018 phone snapshot reads as a closed business
- Action links for your menu and online ordering, pointing at pages that work on mobile
The pin is the one people skip and regret. A pin fifty feet off puts a delivery driver in the wrong lot and a walk-in guest at the back of the building. That is a customer service problem that looks like a mapping problem, and you fix it once by dragging a marker.
Hours deserve one more sentence, because restaurants get this wrong in a way other businesses do not. If your kitchen closes at nine and the room stays open until eleven, the hours field is describing the room, and a guest calling at 9:40 for takeout is going to be disappointed by a listing that told them you were open. Either use the kitchen's hours or make the split explicit somewhere the guest will read it.
Apple also offers promotional cards you can publish to your place card. They are fine and they expire, which means they become another recurring task. Set them up only if you already have a person who will maintain them, and skip them entirely if your hours are still wrong.
Where this shows up beyond Maps
The reason to care goes past turn-by-turn directions.
Voice queries on an iPhone resolve against this data. So do the business cards that appear when someone texts a restaurant name, and the results in Spotlight when a guest types your name into their home screen. Each of those surfaces shows a call button pulled from the record you either control or do not, which is the practical mechanism behind voice search for near-me restaurants and part of what ordering through Siri and Alexa is built on.
There is also a downstream effect. Smaller apps and services license map and place data rather than building it, so a corrected Apple record tends to propagate outward over months. The same is true in the other direction for Bing Places, which feeds a different set of consumers.
Multi-location adds one real complication
Apple Business Connect supports managing several locations under one account, which works fine. The failure mode is the same one that ruins every other local listing effort for a small group: locations sharing a phone number or a name that does not match the sign on the door.
Each store needs its own local number and its own record, tied to its own page on your site. If your locations pages already do that properly, filling in Apple is mostly copying. If they do not, fix the site first, because otherwise you are copying an inconsistency into a new place.
The thing to check tonight
Take an iPhone, open Maps, and search your restaurant by name. Read what it says. Then tap the call button and let it dial.
If it rings your line, you are in better shape than most. If it rings something else, rings nowhere, or rings a phone nobody in the building answers after 8pm, you found the problem, and it is worth more than any amount of website work you had planned for this month. Claim the listing, fix the number, and then decide whether the line behind it is actually being answered when people call. Our contact page is there if you want to talk through the second half of that.