ResNexus and what a park owner controls

Some booking platforms also offer to host the park's website. That is convenient, and it changes who controls the things search depends on. The trade is worth understanding before it is made, and worth auditing if it was made years ago.

The eight checks that decide it

None of these needs support to answer. An owner with a browser can work through the list.

1. Can the title tag be edited per page? View source and look for whether every page carries the same one. Identical titles sitewide is the most common platform limitation.
2. Can the meta description be edited per page? Same check, same place.
3. Can pages be added freely? A platform allowing five fixed pages cannot hold the content campers search for.
4. What do the URLs look like? Readable words are better than numbers or query strings, and they are rarely changeable later.
5. Is there one H1 per page, and does it describe the page? Templates often repeat the park name on every page.
6. Does the site run on the park's own domain? This is the one that matters most, and it is visible in the address bar.
7. Can structured data be added or edited? Per schema markup for RV parks.
8. Can the park's own analytics be installed? Without it, nothing here can be measured.

Check six is the decisive one. A park whose website lives on the platform's domain rather than its own is building search equity for somebody else, and cannot take it anywhere.

What is fine about a platform-hosted site

Worth saying, because the answer is not simply avoid them.

A small park with no technical help and no budget is far better served by a tidy platform site. The alternatives are nothing, or a custom site nobody can update. Speed and mobile behaviour are often handled competently, and integration with bookings removes a real source of friction.

The trade only becomes expensive when a park outgrows it: when it needs pages the template cannot hold, and finds it cannot leave with what it built.

What no platform does for a park

• The Google Business Profile, which sits outside every booking system.
• Reviews, and the process of asking for them.
• Writing the content, which is the actual work and the actual differentiator.
• Local search signals, including directory consistency.
• Answering the questions campers phone the office about.

A park with a competent platform site and none of the above will still be hard to find. A park with a modest site and all of the above usually will not.

When to move off a platform site

Three signals, and one of them is decisive on its own.

The template cannot hold the pages campers search for. Titles or URLs cannot be edited and the site is not ranking for its own name. Or the site is on the platform's domain rather than the park's, which is the decisive one.

Moving is a migration and it carries real risk, mostly around URLs. The checks are in the redesign checklist, and item one there matters more than everything else combined.