Editorial policy
Useful guidance without manufactured certainty.
Navly's public pages should help a traveler make a better next decision. They should never create confidence with numbers, translations, or product promises that the underlying evidence cannot support.
Truthful claims
Say what the product and source support.
We remove legacy ratings, walk scores, crowd data, place and tour counts, prices, user counts, and claims such as 100% accurate or guaranteed. The absence of a number is better than a precise number with no reliable basis.
Product pages describe capabilities that exist in the current Navly workflow. Beta or partial surfaces are described with their boundary instead of being presented as universal coverage.
Page quality
Every page should answer a distinct travel question.
A destination page explains a place and its route context. A product page explains a real workflow. We do not create thin copies for spelling variants, locales without translations, or keywords that do not represent a distinct user need.
Titles, headings, descriptions, and body copy should use the same language and match what the page actually contains.
Routes and time
Editorial windows are frames, not live schedules.
A short, half-day, or full-day route window helps a traveler shape a plan. It is not a promise about transit duration, opening hours, queue time, or availability. Those changing details should be checked before the trip.
Route anchors are intentionally limited to a coherent day. Nearby does not always mean walkable or operationally adjacent.
Corrections
Evidence changes the page.
When a credible source shows that a statement is wrong or stale, we correct it, qualify it, or remove it. See the corrections page for the information needed to investigate a report.