Mobile rendering: Google reads the phone version, and so do your guests.
Google switched to indexing the mobile version of every site years ago, and nearly every camper is on a phone. A crawl reads the HTML and cannot see that the book button is hidden under a sticky bar at 390 pixels wide. Someone has to look at it on a phone.
IN ONE PARAGRAPH
Google indexes and ranks the mobile version of a page, not the desktop one. If a menu, a button, or a block of text is hidden or broken at phone widths, Google treats it as missing. A plain crawl fetches the code and cannot see rendering problems: overlapping elements, text too small to read, buttons that a thumb cannot reach, tables that force the whole page to scroll sideways. We render every page at phone sizes in a real browser and look, because that is the only way to find these.
What mobile-first indexing means
When Google visits your site, it does so as a phone. What the phone version shows is what Google indexes. Content that only appears on desktop, or that is collapsed and never rendered on phones, may not count. Layout problems that make the phone version hard to use count against it. A site that was designed on a large monitor and checked only there is being judged on a version nobody at the park has looked at.
What breaks on park websites at phone widths
- The menu button does nothing, so the only way to reach the rates page is the footer.
- A sticky call bar covers the book button.
- A rate table wider than the screen makes the whole page scroll sideways, and the guest cannot tell.
- Text set at 12 pixels that needs pinching to read.
- Two buttons so close together a thumb hits the wrong one.
- A hero photo sized for desktop that takes the whole first screen and pushes the phone number below the fold.
- A booking widget that opens a window the phone cannot close.
What it costs a park
Google runs a mobile usability check and marks pages that fail. Those pages rank lower. More directly: the guest on a phone who cannot find the book button does not book. On every site we have taken over, the phone version had at least one of the problems above, and on most of them the owner had never looked at the site on a phone.
How to check your own site
- Open your site on your own phone, not on a desktop browser made narrow. Tap every button. Try to book. Try to call.
- Do it on a phone with a smaller screen if you have one; an older iPhone SE finds problems a large phone hides.
- In Chrome on a desktop, open the developer tools, click the phone icon, and step through the device sizes.
- Google Search Console reports mobile usability problems it found.
What we do about it
Every page we build is designed at phone width first and checked at three phone sizes and two desktop sizes in a real browser before launch, with the book button and the phone number reachable by thumb on every one. Nothing scrolls sideways. When we take over a site, the phone walk-through is the first thing we do, because it is where the bookings are being lost. Speed on a phone is the other half.
Questions about this.
Does Google rank the mobile or desktop version of my site?
The mobile version. Google indexes what a phone sees, so content or buttons that are hidden or broken at phone widths are treated as missing or as usability problems.
Why does my site look fine on my computer but not on my phone?
Because it was designed and checked on a large screen. Layouts that work at 1400 pixels wide often overlap, hide, or overflow at 390. It has to be checked on a phone.
How do I test my park website on mobile?
Open it on your actual phone and try to book and call. Then check a smaller phone if you have one. Chrome's developer tools can also emulate phone sizes.
Can a crawl or audit tool find mobile problems?
Not most of them. A crawl reads the code; rendering problems only show when the page is drawn at phone width. Someone has to look, or use a tool that renders the page.
Want this checked on your park site?
Send us the address. We run the full check and tell you what we found, in plain words. SEO for parks starts at $250 a month.
Part of the RV park SEO guide, section: What a script cannot see. Previous: Page speed and Core Web Vitals: your guest is on a phone with one bar. Next: Google Business Profile signals: the part of SEO that is not on your website.