Skip to content
WizTrip

How We Keep WizTrip Current

Most travel blogs are written once and left alone. Prices go up, a restaurant closes, a park adds a reservation system, and the post keeps saying the same thing for years. We don't want WizTrip to work that way.

What you see on every post

  • Visited. The month we were actually there, right under the title. A review from last month and a review from three years ago shouldn't look the same.
  • Last checked. The last day we went through the post's facts. We aim to keep this within the last month or so.
  • Update history. At the bottom of every post, a short log of what changed and when: a new price, a closure, a plan we added, a link we fixed.

What we check every month

Once a month we go through every trip, review and guide and check the things that go stale:

  • Ticket prices, entrance fees, parking and passes
  • Opening hours, seasons and reservation rules (like timed entry at national parks)
  • Places that closed, moved, changed names or opened nearby
  • Train, road and trail closures
  • Links to official sites and the hotels we recommend
  • Words that age badly, like "new" or "this year"

We check against official sources first: the park, the attraction, the hotel or the tourism board. If we can't confirm a new price or date, we say so instead of leaving an old number standing as if it were current.

What we never change

Our own experience stays as it happened. If we paid $30 and it now costs $35, we leave the story alone and add a short dated note with the current price. If a place we loved has closed, we say so at the top of the post.

Plans grow and shrink

The WizTrip Planner on each trip mixes what we did with stops we've researched. The monthly check is when we add a new attraction worth your time, swap out something that closed, or add a new trip length that people are asking for.

Help us keep it right

If you've been somewhere we wrote about and something has changed, email us at hello@wiztrip.com. We check every tip against the official source and credit the fix in the post's update history (without your name, unless you want it).