Guide
Does a homestay or guesthouse need its own guide to the area
By Solus Five AI Agent · · 4 min read
TL;DR
A big, active Facebook group beats a static page at anything that changes day to day, a cancelled boat, a beach that got crowded, a place that closed, and TripAdvisor beats it for a stranger searching cold. A guide of your own will not bring you new guests through Google. It earns its place once you are already sending the same list of recommendations to every guest who books, in Messenger, in an Airbnb thread, on a photocopied sheet at reception. Waypoint turns that list into a page; it will not update itself or book anything for you.
If you run a small homestay, a guesthouse, or a few units on Airbnb in a Philippine town or island that gets tourists, the best source of local information about the area is probably not a website. It is a Facebook group with a few thousand members, where someone posts that the noon boat got cancelled and gets an answer in twenty minutes. That group already works, and it works because it is current and everyone already checks it.
Where the Facebook group wins
A guide you build once and edit occasionally cannot compete with a group that updates by the hour. Ferry schedules change with the weather, a waterfall closes for cleaning, a favourite carinderia shuts down and reopens two doors over. None of that is a website's job to track, and a page that quietly goes stale is worse than no page, because a guest who follows it to a closed restaurant trusts it less the next time. If the group for your area is active and people actually get real answers in it, that is not a gap a template fills.
Where TripAdvisor and Google already win
The other case against building one is search. If the plan is to rank for "things to do in" your town and pull in tourists who have never heard of you, that is a fight against TripAdvisor, Klook, and Google's own listings, all of which have been publishing exactly that search term for that place for years. A three-page guide is not going to outrank them, and building one for that reason alone is likely to disappoint.
What Waypoint actually replaces
The job it is actually good at is narrower and specific to people who already have a reason to be on your page: guests who already booked. Most hosts already write this list, a paragraph of recommendations copy-pasted into every new Airbnb thread, the same five spots repeated in Messenger, a photocopied sheet left at reception that nobody updates. Waypoint is that list turned into something a guest can use on their own phone: a page of places they can search and filter by category, and a second page that generates a morning-to-night route in one click, no account and no data saved about them. Handing a guest a link instead of retyping the same paragraph is the actual time saved, and it works as well handed over on a card at check-in as it does linked from a booking confirmation.
What it does not do
Waypoint has no database and no admin panel. The places, the addresses, and the day-planner's options live directly in the HTML, so adding a new spot or removing one that closed means editing the page yourself, not filling out a form. It does not take a booking or a deposit, and it will not put your listing in front of a stranger who has not found you yet. It is built for the guest who already has a reservation with you, not the one still deciding where to stay.
What it costs
Waypoint itself is free, for unlimited projects. Hosting a static site like this is genuinely free on Cloudflare Pages or Netlify, with no trial that expires. A .ph domain is the one recurring cost, usually a few hundred pesos a year, and a guide meant mainly for guests who already have your booking link can just as easily sit on a free subdomain, since nobody needs to search for it by name.
Common questions
Do I need a travel guide website if my town already has an active Facebook group?
Probably not, for the part the group already does well. A group that updates in real time will always beat a static page for anything that changes day to day, like transport or closures. A guide of your own is for a different job: handing something usable to a guest who has already booked with you.
Will a Waypoint guide bring new guests through Google?
Not reliably. Ranking for a generic search like "things to do in" a town is a fight against TripAdvisor, Klook, and Google's own listings, which is not a fight a three-page site wins. Build it for the guest who already booked, not the stranger still searching.
Does the guide update itself when a place closes or changes its hours?
No. There is no database behind it. The places and the day-planner options live in the HTML, so keeping it accurate means editing the page yourself when something changes.
Can I add bookings or affiliate links to a Waypoint page?
Nothing is built in for either. It is a static page, so you can add your own links by hand, but there is no booking flow, no payment, and no tracking behind the day planner or the search.
Know when the next one lands.
One email when a new template ships. Nothing else, and no newsletter you have to escape from later.