Locale Negotiation Simulator
Simulates RFC 4647 lookup so you can see why a visitor gets a given language version.
Use the tool
Why this tool exists
When a French-Canadian visitor reaches a site with only fr and en, which one do they get, and why? The simulator walks through each language range in preference order, dropping subtags from the right until it finds one of your locales, and falls back to your default. An option also allows matching a different region of the same language.
CMSs and frameworks implement negotiation differently, so use this to understand the logic and then test your own stack.
How to use it
- Paste the visitor's Accept-Language header.
- List your locales; the first is the default.
- Run and read the matching steps.
- Tick the loose option to compare behaviours.
Frequently asked questions
Which algorithm is used?
The Lookup scheme from RFC 4647 section 3.4.
What about q=0?
Those ranges are skipped.
Does Google negotiate this way?
Google does not vary its crawler; use hreflang and links.
Can I test many visitors?
Run it once per header.