To find the wrong phone number or address on one location page, compare each displayed detail and its link destination with an approved list for that specific restaurant. Check the page body, header, footer, and mobile view. A number can look correct on the screen while its tap-to-call link connects to another location.
The useful tool is a location contact reconciliation sheet: one row for each location and page area you check, with the approved details, what you found, and who will fix any mismatch. It gives you a way to spot copied details without relying on memory.
Build an approved location contact list
Start with one authoritative row for each physical restaurant. Ask the person responsible for that location to confirm its public phone number and full street address. Have a central owner or operations manager approve the final list, particularly where restaurants share similar names or sit on the same street.
Record the address as guests should use it to reach the entrance. Include the unit or suite where it matters, plus the city, state, and ZIP code. For the phone number, note whether it reaches the restaurant directly or an approved central line. A shared number is not automatically a mistake; it is a problem when the page promises a local number but connects elsewhere.
Give every location a short, unambiguous identifier in the sheet. “Downtown” and “North” may be easier to distinguish than two street names with similar spellings. Include the public location-page URL and the name of the person who can approve changes. Keep internal personal numbers out of the public contact list.
For each address, agree on a consistent display format. “Street” and “St.” may describe the same place, but a missing suite, wrong ZIP code, or neighboring street number can cause a real problem. The goal is not to flag every punctuation difference; it is to identify details that could direct a guest to the wrong place.
If a location has moved or changed its phone number, record when the new details take effect. Until then, mark the future details as pending rather than treating them as approved for the live page. This prevents a well-meant update from sending guests to an address that is not open yet.
Compare every page and footer
Make an inventory of the website pages that mention a location. Start with each location page, then check the contact page, locations index, ordering entry points, and any page with a shared header or footer. A footer that appears on every page deserves its own check: a location-specific phone number there may be correct for one restaurant and misleading for the rest.
Use the reconciliation sheet below to compare the approved record with each place it appears. Keep the page URL or a precise page name with every finding. “Wrong number on the website” is harder to fix than “North location page, footer phone link.”
Hypothetical example: A two-location restaurant has approved a different phone number and address for each site. The North page was copied from the Downtown page. The table shows a small portion of its review; the numbers and addresses are invented for this example.
| Page area | Approved for location | Found | Action and owner |
|---|---|---|---|
| North page, contact block | North: 202-555-0142; 18 Pine St., Suite B, Washington, DC 20001 | Phone and address match | No correction; North manager confirmed |
| North page, footer | North: 202-555-0142 | 202-555-0107, the Downtown number | Replace or relabel; website editor |
| North page, map link | 18 Pine St., Suite B | Link opens 18 Oak St., the Downtown address | Update destination; website editor |
| Downtown page, contact block | Downtown: 202-555-0107; 18 Oak St., Washington, DC 20001 | Phone and address match | No correction; Downtown manager confirmed |
In this example, the main North contact block is right, but two other elements still point guests toward Downtown. The editor should first establish whether the footer is shared across the site. If it is, replacing the number everywhere with the North number would simply move the mistake to the Downtown page. A clearly labeled central contact or location-specific footer may be a better choice, depending on the site.
Open pages on a phone as well as a desktop. Menus, sticky buttons, and footers can appear differently at smaller screen sizes. Check the visible text after scrolling to the bottom, not just the first screen. Also look at any location selector: confirm that choosing North leads to North details rather than a copied default.
If your online ordering starts from a separate button or page, follow that path far enough to see which restaurant is identified. A correct contact page does not help much if a guest is sent to the wrong location when trying to order. Do not place an order just to inspect the page.
Test phone and map links without disrupting service
Displayed text and link destinations are separate checks. On a phone, press the call link and inspect the number shown in the device’s call prompt before placing a call. Compare it with the approved record, then cancel. On a desktop, inspect the link destination where your browser allows it. Do not assume that editing the visible number also changed the underlying link.
If you need to confirm that a line actually reaches the intended restaurant, arrange a brief check with the location manager outside a busy period. That is a live call, not a simulation. Confirm who will answer and end the call promptly. Do not call repeatedly during service or use a guest’s number for the check.
For a map link, open the destination and compare the full address, including suite information, against the approved list. Look at where the pin lands and whether the destination label names the intended restaurant. A map result may use a shortened address or place the pin near a building rather than its entrance, so ask the local manager to resolve any ambiguity. Opening a map link does not prove that driving directions or parking instructions are suitable for every guest.
Return to the North example. The visible address in the contact block matched the approved record, but the map opened the Downtown address. The fix is to change the map destination, not just retype the displayed address. After the change, open the link again from the public page on a phone and confirm that it points to North. If the site has a preview or staging version, check there first, then repeat the non-disruptive check on the live page after publication.
For linked buttons, ask your website provider or editor how to change text and destinations separately. If you are considering a new platform, the restaurant website builder comparison can help frame questions about editing control. Also ask who can publish a correction and whether a shared footer can be changed for one location without affecting the others.
Assign corrections and schedule a review
For every mismatch, record the page area, approved value, current value, responsible editor, and date reported. Add a status such as open, awaiting approval, corrected, or verified. The person who found the mistake does not have to be the person who fixes it, but someone should own the handoff.
Send the editor enough detail to reproduce the problem: the page URL, whether the issue appears on mobile or desktop, the visible text, and the link destination if they differ. Avoid sending only a screenshot of the right address with a note to “fix the map.” The editor needs to know which link is wrong and what destination should replace it.
After publication, have a second person compare the live page with the approved list. Check both the changed element and any other pages that use the same header or footer. Record the verification date in the sheet. If the correction cannot be made promptly, decide whether to remove or clearly label a misleading link while the permanent fix is arranged.
Set a recurring review that fits your operation, and add an immediate review after a move, phone change, website redesign, or new location launch. The same contact list can guide updates wherever guests find the business, but keep the website check focused on phone numbers and addresses rather than turning it into a general hours audit.
If an outside provider manages the site, ask for the correction process, expected turnaround, and access available to your team. Check who controls the domain and account as well; the guide to restaurant website domain ownership covers questions to raise before a handoff becomes urgent.
Next step: Copy the reconciliation table into your working sheet, add every location and page area, and assign one person to confirm the approved details. If you are evaluating a replacement restaurant website, ask Fleksa about current US availability and how your team would update location contacts.
Frequently asked questions
How do I tell whether a duplicate phone number is wrong?
Compare it with the approved contact record for each location. A shared central number can be intentional, but label it clearly so guests do not mistake it for a direct line to a particular restaurant.
Should I check a phone link if the displayed number is correct?
Yes. The call link can contain a different number. Inspect the number in the call prompt and cancel; arrange a separate live call with the location manager only if you need to confirm where the line is answered.
Who should approve a location contact change?
Have the location manager confirm the local details and a designated operations owner approve the master list. The website editor can then publish the change, and another person can verify it on the live page.
