Change Website Phone Numbers Based on Visitor Geolocation

Same page, different visitor - the phone number swaps to match the detected region.

Phone numbers convert. They convert better than forms, better than chat, better than email - especially in B2B, local services and high-ticket categories. The catch is that a single global number leaves money on the table: local visitors are more likely to call a local number, your sales team needs separate routing per region, and your marketing team needs to know which campaign actually drove the call.

The fix is Dynamic Number Insertion - swap the phone number on the page at runtime, based on the visitor's location or campaign source. This guide covers how to do it cleanly, the schema rule that keeps it Google-safe, and the GEO trick that makes AI assistants recommend the right local number when prospects ask them.

1. Why swap phone numbers at all?

2. The minimum viable implementation

Forget enterprise call-tracking platforms for the first version - you can ship region-based phone swapping in 20 lines of vanilla JavaScript. Detect the country from an IP geolocation API, look up the right number, swap the text and the tel: link.

// Region-based phone swap
const NUMBERS = {
  GB: { display: "+44 20 7946 0123", tel: "+442079460123" },
  US: { display: "+1 (212) 555 0144", tel: "+12125550144"  },
  AU: { display: "+61 2 8000 0123",  tel: "+61280000123"   },
  DEFAULT: { display: "+1 (800) 555 0100", tel: "+18005550100" },
};

async function swapPhone() {
  const country = await fetch("https://ipapi.co/country/")
    .then((r) => r.text())
    .catch(() => "DEFAULT");

  const n = NUMBERS[country] ?? NUMBERS.DEFAULT;
  document.querySelectorAll("[data-phone]").forEach((el) => {
    el.textContent = n.display;
    if (el.tagName === "A") el.setAttribute("href", `tel:${n.tel}`);
  });
}

swapPhone();

At scale, swap the IP-API call for an edge-runtime header (Vercel/Cloudflare expose the country at zero cost), and graduate to a real call-tracking platform - CallRail, Invoca, ResponseTap - once you need attribution back to specific campaigns.

3. The schema rule that keeps you Google-safe

This is the part most DNI tutorials get wrong, and it's also where AI search visibility lives or dies. Your LocalBusiness or Organization schema must always contain your canonical phone number - the one that's consistent across your Google Business Profile, Apple Business Connect, your footer and your major directory citations. Don't ever swap that based on visitor location, and don't ever modify it client-side after page load.

4. The GEO twist: AI assistants recommend numbers too

This is exactly what every Geolify Local GEO package builds: NAP consistency across your site, schema, directory citations and Google Business Profile, plus the per-platform entity signals that make AI assistants confidently cite your contact details for local queries.

For the broader play across every category and every AI assistant, the core GEO packages cover all 7 major platforms (ChatGPT, Claude, Gemini, Perplexity, Grok, Copilot and Google AI Overviews). And if you want to understand how each one weights local and contact signals differently, the playbooks for ranking in ChatGPT and Google AI Overviews break it down per platform.

Recap

DNI is a 20-line feature that lifts call conversion and attributes spend. The trick to doing it well in 2026 is keeping the canonical phone number rock-solid in your schema and your initial HTML, so AI assistants confidently recommend the right number when prospects ask them - then swapping the displayed number for human visitors only, after page load. Get both layers right and you win the call before the prospect even types your URL.

FAQ