Place names in the form a native speaker would use
If you have ever seen a travel page bend a foreign place name into a case or plural that no local would recognize, you know the small jolt it causes. Our rule is simple: a place name appears in the grammatical form a native speaker would actually use, and nothing in our pipeline is allowed to reshape it. This is how we hold that line, and where it gets hard.
- Core rule
- Do not inflect or modify place namesNames are used only in the supplied native form
- Failure mode guarded against
- Silent reshaping by templates and translation layersNo error is thrown, so the mistake reaches publication
The decision this solves
The reader is not thinking about grammar. They are scanning a page to decide whether a destination is worth their time, and a mangled place name tells them, quietly, that nobody who knows the place wrote this. That is the trust we are protecting.
So the working rule sits upstream of everything else we publish: the name is fixed in its native form first, and every sentence is written around it. We do not decline it, pluralize it, or force it into a possessive because English grammar wants one.
What 'native form' actually means
Many languages inflect nouns, and place names are nouns. A name that looks like one word in a dictionary can take several endings depending on whether you are in it, going to it, or speaking of its features. A native speaker switches between those forms without thinking.
Our standard is that the form we publish is one a native speaker would use in that exact sentence position, supplied to us as a fixed string. We treat that string as data, not as text to be conjugated. If we need the name in a different grammatical role, we ask for that specific form rather than generating it.
Why software gets this wrong
Automated text tools are built to make sentences read smoothly, and that is exactly the instinct that damages a place name. A template that adds an apostrophe-s for possessives, or a translation layer that normalizes endings, will happily rewrite a name it does not recognize as fixed.
The failure is silent. Nothing throws an error, the sentence still parses, and the mistake only surfaces when a reader who speaks the language notices. By then it is published. We treat any process that can reshape a name as a defect, not a feature.
How the name gets into the page
Names reach the page as explicit fields, separated from the prose. The writer receives the form to use and is instructed not to construct alternatives. Where a sentence needs a case or preposition combination, that combination is supplied whole rather than assembled from parts.
This is deliberately unglamorous. The safest way to avoid inflecting a name incorrectly is to never inflect it at all, and to make the correct form the only one available.
The prohibition that makes it stick
A guideline that says 'be careful with names' fails, because care erodes under deadline. What holds is an absolute rule: do not inflect or modify place names, full stop. If the supplied form is 'in der Türkei', that is what appears, and no writer builds their own case ending from it.
Turning a soft preference into a hard prohibition is the whole point. It removes the judgment call at the moment of writing, which is exactly the moment judgment is weakest.
Where it genuinely gets hard
The hard cases are the ones where good English style and the native form pull against each other. English wants a possessive; the language of the place may not form one that way. English wants a smooth relative clause; the name may need a form we were not given.
When that happens, we rewrite the English sentence rather than the name. It depends on what the sentence is trying to do: if the name needs a form we do not hold, we restructure around it, and if that is impossible, we flag it as a data gap rather than guessing.
Who this rule is not for
If you are producing high-volume content in a single language where names do not inflect, this discipline will feel like overhead you do not need. English place names in English pages rarely trigger the problem, and building a fixed-form pipeline for them is effort spent on a risk that is not there.
The rule earns its cost when you publish across inflecting languages, or about destinations whose names change shape in the target language. That is where a small structural safeguard prevents a steady drip of errors that no spellchecker will catch.
How you can check our work
Read any place name on our pages back in the sentence and ask whether a person from that place would say it that way. If it reads as a dictionary headword forced into a slot, that is a mistake, and we want to hear about it.
We would rather publish a slightly less fluent English sentence than a name no local would recognize. That trade-off is the standard, and it is one we hold on purpose.
What works
- Place names appear in a form native speakers actually use, not a machine-generated one
- A hard prohibition removes the judgment call at the weakest moment, under deadline
- Names are handled as fixed data, separated from editable prose
- Errors that spellcheckers miss are prevented structurally rather than caught later
What does not
- English sentences sometimes read less smoothly to protect the name
- Requires supplying multiple grammatical forms as data, which is extra upstream work
- Overhead is wasted on single-language, non-inflecting content
Who should go somewhere else
single-language English publishers — English place names rarely inflect, so the risk this guards against mostly is not present
Instead: a lightweight style note rather than a fixed-form pipeline
Questions people actually ask
why do travel sites get foreign place names grammatically wrong
Automated text tools are built to smooth sentences, so they add possessives or normalize endings on names they do not recognize as fixed. Nothing flags the change, so it publishes silently. The fix is to treat the name as fixed data and never let the writing process reshape it.
what does keeping a place name in native form mean
Many languages change a noun's ending depending on its role in the sentence, and place names are nouns. Native form means using the ending a local speaker would actually use in that position, supplied as a fixed string rather than constructed by us on the fly.
how do you handle a place name when English needs a possessive
We rewrite the English sentence rather than force an ending onto the name. If the sentence needs a form of the name we were not given, we restructure around it. When that is impossible, we flag it as a data gap instead of guessing at a form.
do English place names need this rule
Rarely. English names seldom inflect, so a fixed-form pipeline is usually overhead you do not need. The discipline earns its cost when you publish across inflecting languages, or about destinations whose names change shape in the target language.