Editorial Policy

Travel content goes stale in predictable places: opening hours, ticket prices, transport fares, and event dates. Our approach is to keep guides evergreen wherever possible — describing the rhythm of a place rather than pinning a specific closing time — and, where a concrete figure genuinely helps, to check it against an official source and add a friendly nudge to reconfirm it near your travel dates.

We don't invent numbers. If we can't confirm a price or an opening time to a single, current value, we either keep it qualitative or give a range with a caveat and a link to the venue's own page. The most volatile facts we surface — fares, ticket prices and seasonal hours — are exactly the ones we tell you to double-check close to your travel dates.

We keep outbound links restrained and purposeful. When we link off-site, it's usually to the official page that is the most accurate place to verify time-sensitive details — a venue's own ticketing page, the city transport operator (Rīgas Satiksme), the train operator (Vivi), or the official tourism boards (LiveRiga and Latvia Travel). We try not to turn guides into link directories; the aim is to keep planning on-site and decisions simple, then send you to the source only for the detail that genuinely needs checking.

Our sources page collects these primary references in one place, grouped by what each is good for, alongside a short pre-trip checklist of the things most worth verifying.

Guides are attributed to the Love Riga editorial team as an organisation, not to a fabricated individual author. We do not create fake personas, fake bylines or fake credentials. Structured data on each guide names the publisher as an Organization for the same reason.

We write independently. Recommendations are based on how a place fits a real, walkable Riga day — not on commercial relationships — and we'd rather omit a place than oversell it.

Every guide carries a 'Last reviewed' date that reflects a genuine editorial pass over that page — not an automatic file timestamp that bumps whenever any unrelated code changes. When we do a substantive content review (rewriting sections, re-checking facts, adding depth), we update that date; small copy fixes don't reset it. This keeps the freshness signal honest rather than inflated.

We review the most perishable pages — transport, tickets, day-trip logistics and events — more often than evergreen background pages, because those are where information drifts fastest. If you ever find a 'Last reviewed' date that no longer matches reality on the ground, that's exactly the kind of thing we want flagged.

Events are the single most volatile category we publish: dates, venues and line-ups shift year to year. Where dates aren't fully confirmed, we say so and point you to the official organiser. Riga's recurring anchors — Midsummer (Jāņi/Līgo, around 23–24 June), the Christmas-market season, and the periodic Latvian Song and Dance Festival — are described as patterns, with a 'confirm the current year's dates' note rather than a hard-coded date that will age.

We'd rather be told we're wrong than leave a stale page up. If you find something that has changed on the ground — a venue that has closed or moved, a price that's out of date, a route that no longer runs — let us know and we'll fix it. The most useful reports include the page URL, what changed, roughly when you noticed, and an official source link if you have one.

When we make a meaningful correction, we update the page and its 'Last reviewed' date so the freshness signal stays honest. Small copy tweaks don't reset that date; substantive content reviews do.