Resort website SEO: fixes from a real hotel site audit
Short answer Audits of resort websites keep finding the same few problems: a cookie banner covering buttons, links that say only "learn more", photos with no alt text and huge file sizes, a slow hero image, last season's offers still live, and FAQ markup that Google stopped showing in May 2026. Most can be found and fixed with free tools.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhat a resort website audit usually finds
Resort sites are photo-heavy, seasonal and often rebuilt every few years, so the same problems keep turning up. Work down this list with free tools: your phone, PageSpeed Insights, Search Console and the Rich Results Test.
| Problem | How to spot it | Fix |
|---|---|---|
| Cookie banner hidden behind a chat or "Contact" button | Open the site on your phone and try to tap Accept | Move the floating button, or raise the banner above it |
| Links that say "learn more" or "read more" | Read only the link words on a page | Name the page: "spa treatments and prices" |
| Broken links to retired pages | Search Console, Pages report, "Not found (404)" | Point the link at the current page, or redirect the old one |
| Photos with no alt text, or full-size camera originals | Right-click a photo, check its size and description | Describe each photo; resize to display size |
| Slow main photo or video | PageSpeed Insights, Largest Contentful Paint | Don't lazy-load it; compress it; delay non-essential scripts |
| Last season's packages and events still live | Search your own site for last year's dates | Update the page in place, or retire it with a redirect |
| Icons for social networks that no longer exist | Look at the footer | Remove them |
| FAQ markup added to show questions in Google | Rich Results Test | Leave it or remove it; it no longer shows |
Cookie banner covering buttons: why your numbers drop
A consent banner nobody can click quietly empties your analytics. Google's consent mode documentation says that in basic mode, when a visitor doesn't consent, "no data is transferred to Google at all – not even the consent status." In advanced mode, tags send only cookieless pings while consent is denied (Google Tag Platform: Consent mode overview). Either way, a blocked Accept button means you undercount visitors and bookings, and your reports look worse than reality.
On a phone, the usual culprit is a floating "Book now", chat or "Contact us" button sitting on top of the banner's Accept button. Test on a real phone, in both portrait and landscape.
A legally required banner is fine for Google. Its interstitials guide lists mistakes to avoid "unless they're legally mandatory," starting with "Don't obscure the entire page with interstitials" (Google Search Central: Interstitials and dialogs). So keep the banner small, and make it work.
"Learn more" links: what to write instead
Write link words (anchor text) that name the page they open. Google's link guide calls "Click here" and "Read more" too generic, and adds:
"Good anchor text is descriptive, reasonably concise, and relevant to the page that it's on and to the page it links to." (Google Search Central: Link best practices for Google)
Google's own test: read only the link words, out of context. If you can't tell where they go, rewrite them. On a resort homepage, three "Learn more" buttons under Rooms, Spa and Weddings become "See our rooms and suites", "Spa treatments and prices" and "Plan a wedding at the resort".
The same guide says "Every page you care about should have a link from at least one other page on your site." Check that the wedding, spa and seasonal package pages are linked from somewhere other than a buried menu. For photos used as links, Google reads the image's alt text as the link words, so a linked photo with no alt text is a link with no label.
Broken links and retired pages
A link to a page that no longer exists sends guests to an error and wastes the link. Google says a 404 tells its crawlers "the content doesn't exist," and if the page was indexed, Google "removes the URL from the index" (Google Search Central: How HTTP status codes affect Google's crawlers).
Find them in Search Console's Pages report under "Not found (404)"; for a crawl of your own links, any free link checker works. For each one: fix the link if the page moved, or redirect the old address to its closest current page. Resorts lose most of these during redesigns; see traffic dropped after a website redesign.
Resort photos: alt text, file names and size
Alt text and file names are two different things. Alt text is a short description in the page code that screen readers read aloud and Google uses to understand the photo. Google calls it "the most important attribute" for image metadata, and warns:
"Avoid filling alt attributes with keywords (also known as keyword stuffing) as it results in a negative user experience and may cause your site to be seen as spam." (Google Search Central: Image SEO best practices)
Good: "Infinity pool facing the lake at sunset." Bad: "resort pool lake resort best resort Ontario."
File names give Google "very light clues," the same page says. Name files plainly, such as lakeside-pool-sunset.jpg, not IMG00023.JPG. Google Search reads BMP, GIF, JPEG, PNG, WebP, SVG and AVIF.
Size matters more than names. Photographers often deliver camera originals many times larger than the screen shows. Export each photo at the size it's displayed, in WebP or AVIF where your site supports it, and let your site builder serve smaller versions to phones.
Page speed: the three fixes that matter on a resort site
Google's target is the main content showing within 2.5 seconds (Largest Contentful Paint, or LCP) (Google Search Central: Understanding Core Web Vitals). On resorts the main content is nearly always the hero photo or video, so:
- Never lazy-load the hero. Lazy loading delays images until the visitor scrolls near them. Good for gallery photos further down; bad for the first one. web.dev puts it flatly: "Never lazy-load your LCP image." Galleries further down the page can use `loading="lazy"` (web.dev: Browser-level image lazy loading).
- Shrink the hero. Resize and compress it as above. An autoplay video is usually the heaviest thing on the page; a still photo with a play button is lighter.
- Delay scripts that aren't needed at first. Booking widgets, chat, weather and review widgets often load in the page head and hold up everything else. Lighthouse flags scripts in the head without `defer` or `async` as render-blocking, and says to mark non-critical code with one of those attributes or remove what isn't used (Chrome for Developers: Eliminate render-blocking resources).
Browser caching, the server telling a visitor's browser to keep files for repeat visits with a Cache-Control header, helps returning guests (web.dev: HTTP Cache). Most hosts and site builders set it already; ask before paying anyone to do it. The full speed story is in Core Web Vitals.
Outdated content: old offers, events and dead icons
Old content hurts guests first. A "2024 Ski and Stay package" or a past New Year's gala tells a visitor nobody minds the site. Fix it page by page:
- Recurring packages and events: keep one permanent page and update dates and prices each season, instead of a new page every year. Links and rankings stay with that address.
- Amenities that closed: remove or reword them on every page, including room descriptions and the FAQ.
- Dead social icons: Google+ shut down for consumers in April 2019 (Google Keyword blog: Expediting changes to Google+). An icon for it, or for any account you abandoned, should go.
Don't change dates to look fresh. Google's people-first content checklist asks whether you're "changing the date of pages to make them seem fresh when the content has not substantially changed," and whether mass adding or deleting pages to seem fresh will help rankings: "(No, it won't)" (Google Search Central: Creating helpful, reliable, people-first content).
FAQ schema and breadcrumbs: what changed
Older audit checklists say to add FAQ schema so your questions show under your result. That no longer works for anyone.
| Date | What happened |
|---|---|
| August 2023 | Google limited FAQ rich results to "well-known, authoritative government and health websites" (Changes to HowTo and FAQ rich results) |
| May 7, 2026 | FAQ rich results stopped appearing in Google Search for all sites (Latest documentation updates) |
| June 15, 2026 | Google removed the FAQ rich result documentation |
Leftover FAQ markup is harmless. Google said in 2023 that such structured data "does not cause problems for Search, but also has no visible effects." Keep a visible FAQ section if guests use it; it answers questions about check-in, pets and parking whatever Google shows.
Breadcrumbs (the "Home › Rooms › Lake Suite" trail) still help visitors find their way. Starting January 23, 2025, Google rolled out a change to stop showing them in mobile results; they still show on desktop (Google Search Central Blog, January 2025).
To test any markup, use the Rich Results Test or the Schema Markup Validator (Google Search Central: Test your structured data). The old Structured Data Testing Tool moved to schema.org in 2020. More on what markup still does in local business schema markup.
Example
Illustrative scenarios, round numbers.
A 60-room lake resort with a broken banner
Analytics showed a third fewer visitors from phones than from desktops, while bookings came mostly from phones. The chat bubble sat on the Accept button. After moving it, phone visits in analytics roughly matched desktop the next month. The guests were always there; the counting was not.
A ski resort with a 9 MB hero video
LCP on phones was over 6 seconds. Replacing the autoplay video with a compressed photo and a play button, and adding `defer` to the weather widget, brought it under 2.5 seconds.
A beach resort with five years of package pages
Each year's "Summer Escape" lived at a new address. The resort kept the newest page, updated it each season, and redirected the four older ones to it.
FAQ
How often should a resort website get an SEO audit?
Before each peak season and after any redesign. Seasonal pages and offers go stale on that rhythm.
Do I need paid SEO tools for a resort audit?
No. PageSpeed Insights, Search Console and the Rich Results Test are free and cover everything above.
Should I delete my FAQ page now that FAQ rich results are gone?
No. Only the Google display ended. A visible FAQ still answers guests' questions; the markup can stay or go.
Does alt text help my photos rank in Google Images?
It helps Google understand them. Google uses alt text, the page's text and computer vision together, so place photos near text about the same thing.
Different for you?
- Your traffic fell after a new site launched: traffic dropped after a redesign.
- Your pages are slow even after fixing photos: Core Web Vitals.
- You want each room and package page to rank for its own searches: on-page SEO for service pages.
- You're unsure what markup to keep: local business schema markup.
- You'd rather have the site checked and fixed for you: SEO & GEO Agent.