What "phone format wrong" means
This check fires when phone numbers on your international or localized pages are shown in a format that does not match the country you are targeting. A German visitor on your German page should see a number written the way Germans write numbers. A US visitor should see the US convention. When a French page displays a raw US style number with no country code, or a UK page shows a number that only dials from inside the US, the number is technically present but practically useless to the person reading it.
There are really two formats in play. There is the display format, which is how a human reads the number, and it follows local convention. And there is the machine format, called E.164, which is the international standard: a plus sign, the country calling code, then the national number with no spaces or punctuation, such as +14155550132. Get both wrong and you break humans and robots at the same time.
Why it matters
Phone numbers are a conversion element on service, local, and contact pages, so a broken number is a broken conversion path. The damage shows up in three places.
Calls that will not connect. A number missing its country code, or formatted for a different country, may simply not dial from the visitor's phone. On mobile, where a large share of "call now" intent lives, a number the dialer cannot parse is a dead end.
Broken tap-to-call. A tel: link needs a clean, unambiguous number to work reliably across devices. If the href holds a locally spaced number instead of the E.164 form, taps can fail silently. The number looks fine and does nothing, which is the worst kind of bug.
Rejected structured data and local signals. LocalBusiness and Organization schema expect a telephone value, and Google's guidance is to use the full international format. A malformed number can get your markup ignored, which weakens the local and entity signals that help these pages rank and appear correctly in Maps and knowledge panels.
How to detect it
- Extract every number with a crawl. Use Screaming Frog custom extraction (or Sitebulb) to pull the text of tel: links and any visible number patterns across the site. Now you have a list to audit instead of clicking through pages by hand.
- Compare against the target country per page. Cross reference each number with the locale of the page, using your hreflang or URL structure as the country signal. A number whose country code does not match the page's target is the flag.
- Check the href, not just the visible text. The number a user sees and the number inside the tel: attribute are separate. Inspect both. A pretty display number over a malformed href still breaks tap-to-call.
- Test on a real phone. Nothing beats tapping the link on an actual device in the relevant region and confirming the dialer fills in the correct number.
- Validate your schema. Run the Rich Results Test on pages with LocalBusiness or Organization markup and confirm the telephone value is accepted in full international format.
How to fix it, step by step
- Store the canonical number in E.164. Keep one clean machine version per location, plus sign, country code, national number, no spaces. This becomes the single source of truth.
- Render the display number in local convention. Format the human facing number the way people in that country expect to read it, including spacing and any leading zero conventions for domestic dialing context.
- Put E.164 in the tel: href. Always. The visible text can be locally styled, but the href should be tel:+14155550132 so every dialer parses it the same way.
- Use the right number per locale. If you run local numbers per country, serve the correct one on each localized page rather than a single head office number everywhere.
- Feed E.164 to your structured data. Set the schema telephone property to the full international format so LocalBusiness and Organization markup validates cleanly.
- Recrawl and retest. Confirm the extraction now shows matching country codes per locale and tap-to-call works on a device.
Format reference by locale
| Locale | Human display | E.164 for href and schema |
|---|---|---|
| United States | +1 415 555 0132 | +14155550132 |
| United Kingdom | +44 20 7946 0018 | +442079460018 |
| Germany | +49 30 901820 | +4930901820 |
| France | +33 1 40 20 50 50 | +33140205050 |
| Japan | +81 3 3213 1111 | +81332131111 |
- Store a canonical E.164 number per location
- Display numbers in each country's local convention
- Put the E.164 form inside every tel: href
- Serve the correct local number on each localized page
- Use full international format in LocalBusiness schema
- Show one country's format on every localized page
- Drop the country code and hope the dialer guesses
- Put spaced or punctuated numbers inside the tel: href
- Assume a nice looking number means the link works
- Skip testing tap-to-call on a real device
FAQ
What is E.164 and why does it keep coming up?
Can I show the pretty number but link the clean one?
Does phone formatting really affect SEO or just usability?
We only serve one country. Do I still need to worry?
Auditing every localized page for correct display formats, working tel: links, and valid schema across markets is fiddly, high value work. It is exactly what a thorough audit is built to catch.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
