Your own domain
Point your address at your TrailsIQ pages and they serve from it. Visitors never see ours, and the certificate is handled for you.
Your public site
One record, read by your crew and by your visitors
Conditions drift because the person who knows and the page that tells people are usually in different systems. Here your public site is fed by the work your team is already doing.
The site itself
Pages you assemble, not a theme you fight
Blocks you drop onto a page — a map, a trail list, conditions, a gallery, text, a call to action — arranged without touching code.
Live trail conditions, without an edit
The status your crew set from the trailhead is what the page shows. Nobody has to remember to update the website after a storm.
Search and share previews you control
Title, description, share image and favicon per page, so a link posted to a community group looks like yours rather than like a bare URL.
News, written where the work is
Post an update about a closure or a work day from the same place you manage the trails, and have it appear on the site and in the feed.
Events with signups, waivers and waitlists
Run a volunteer day: people sign up, sign the waiver, get a reminder, and roll off a waitlist when somebody drops. You get a list to work from.
QR codes for signs and print
Branded codes pointing at a trail, a network or your report page — for a kiosk, a trailhead sign or the back of a printed map.
Closing the loop
Visitors are part of the system, not an audience
The people using your trails see more than anybody on your crew does. The site is where that becomes useful to you.
01
They report what they find
A trail user opens your report page on their own phone, marks where they are, adds a photo and describes it. No account and no install.
02
It waits for somebody on your team
Reports land in a review queue, not in your crew's work list. Approve one and it becomes an ordinary maintenance item; reject it and it is gone. Nothing goes live unreviewed.
03
They can follow you
Somebody who cares about a network gets a push when a condition changes or you post the day's report — rather than checking a page that has not moved since Tuesday.
04
And the day gets written up
A daily report collects the day's condition changes, work and notes into one page your visitors can read — assembled from what already happened rather than typed out again.
In the documentation
How this works, in detail
Step-by-step guides for setting each of these up.
Stop maintaining the same facts twice
Build a public page on the free plan and point your own domain at it when you are ready.