On-page SEO is the most-written-about topic in the SEO industry. Most of what's been written is generic enough to apply to any vertical, which means it's calibrated for none of them. For hospitality sites specifically, the standard advice often produces sites that are technically correct but commercially mediocre — pages that rank for low-value queries while missing the high-intent travel research patterns that produce actual bookings. This post is the on-page SEO working checklist calibrated specifically for hospitality, with the rationale for each item.
Title tags — write for two readers.
Title tags are read by both Google's ranking algorithms and by humans deciding whether to click. For hospitality, the human reader is usually deciding between 5-8 properties in their consideration set. The title tag that wins both audiences:
- Includes the property's primary keyword (typically "[property name]" or "[trip type] in [destination]")
- Includes a positioning element ("boutique resort," "adults-only," "family-friendly")
- Stays under 60 characters to avoid truncation in search results
- Uses the property's actual name rather than a marketing tagline
Bad: "Welcome to Paradise — Book Now"
Good: "Hotel Indigo Asheville — Boutique Mountain Lodging"
The bad version optimizes for nothing. The good version captures both branded queries and the broader category queries.
For destination guides and blog content, the pattern is different. The title should match the exact query a traveler would type:
- "Best Things to Do in Asheville This Weekend"
- "Asheville with Kids: 12 Family-Friendly Activities"
- "Where to Stay in Sonoma for Couples"
Each of these matches the natural language travelers actually use. Generic titles like "Asheville Travel Guide" get less click-through and rank for fewer specific queries.
Meta descriptions — earn the click.
Meta descriptions don't influence rankings directly but they significantly influence click-through rates from the SERP. For hospitality, the meta description should:
- Repeat the primary keyword (matched to user search shows in bold in search results)
- Include one specific factual hook (a number, a distance, a unique amenity)
- End with a soft action prompt that doesn't read like marketing spam
Bad: "Experience the magic of our resort. Book your dream vacation today!"
Good: "40-room boutique resort in downtown Asheville, three blocks from the Blue Ridge Parkway. Rooftop terrace, on-site spa, dog-friendly rooms available."
The bad version generates no information. The good version answers "what's actually there" in 25 words and earns clicks from travelers who care about those specifics.
H1 — one per page, query-aligned.
Each page should have exactly one H1 tag, and it should be the primary on-page signal of what the page is about. For property pages, the H1 is typically the property name plus its category positioning. For blog and destination content, the H1 should match the query format travelers use.
The single most common H1 mistake on hotel sites: using the H1 for a marketing tagline ("Where Memories Begin") rather than a search-aligned positioning statement. The H1 should be a search signal first and a brand signal second.
For the property's main page:
- Bad H1: "Where Memories Begin"
- Good H1: "Hotel Indigo Asheville — Boutique Mountain Lodging"
For a blog post about local activities:
- Bad H1: "Discover the Magic of Asheville"
- Good H1: "12 Best Things to Do in Asheville This Fall"
H2s and H3s — question-format wherever possible.
Subheadings (H2 and H3 tags) do double duty in 2026 hospitality SEO. They structure the page for human readers, and they signal to AI extraction systems what specific questions the page answers.
The most powerful subheading pattern is question-format. "What's the parking situation?" outperforms "Parking" as an H2. "How far is the property from the airport?" outperforms "Location." The question format matches the natural language travelers use when researching, and AI systems extract the answer paragraph beneath a question-format heading at much higher rates.
Practical rule: at least 50% of H2 and H3 tags on a hotel page should be in question format. The other 50% can be descriptive when the section doesn't lend itself to a question framing.
URL structure — short, descriptive, stable.
Hotel URLs should follow three rules:
- Short. Under 60 characters. Avoid trailing query strings, session IDs, and unnecessary subdirectories.
- Descriptive. The URL should give a clear signal of the page's content. /asheville-things-to-do is good. /post?id=4471 is bad.
- Stable. Once a URL is published, don't change it. Every URL change requires a 301 redirect and potentially loses some ranking signal.
The most common hospitality URL mistake: booking-engine pages with extensive query parameters that produce dozens of duplicate URLs for the same property. These need careful canonicalization (rel="canonical" tags pointing to the primary version) or Google indexes them as separate pages and dilutes ranking signal across the duplicates.
Internal linking — five per post, contextual.
Every new piece of content should link to at least 5 existing pieces, and ideally be linked to from at least 2 existing pieces within 30 days of publication. The internal linking pattern signals to Google which pages are most important within a topic cluster.
The right way to internal-link:
- Use natural anchor text describing what the linked page is about ("the schema markup framework" rather than "click here")
- Link from contextually relevant locations within the article (mid-paragraph, where the link adds real value)
- Build hub-and-spoke patterns: pillar pages get linked from dozens of related posts; the pillar pages link back to a curated subset
What not to do:
- Footer link dumps ("see also: 50 other articles") — these don't carry the same authority signal as in-content links
- Linking only to the homepage from every post (over-concentrates signal)
- Orphan pages — content with no internal links pointing to it usually gets de-indexed over time
Schema markup — Hotel, LocalBusiness, FAQ, Place.
Hospitality sites need (at minimum):
- Hotel schema on property landing pages — includes name, address, telephone, image, priceRange, starRating, amenityFeature
- LocalBusiness schema as a foundation for local SEO — overlaps with Hotel schema but extends to operational hours and review aggregation
- FAQPage schema on FAQ sections — the single highest-leverage schema implementation for AI extraction
- Place schema on destination guides — helps Google understand the geographic relationships in the content
- Review/Rating schema where the property has authentic on-site reviews
Schema validation matters. Use Google's Rich Results Test and Schema.org's validator on every page that implements schema. Broken schema doesn't help and can hurt — Google explicitly de-emphasizes pages with markup errors.
Image optimization — three specifics most hotels miss.
Hotel sites are image-heavy by nature. Image SEO done well produces 15-30% of organic traffic on most hospitality sites. Three patterns most properties miss:
1. File names and alt text describing the actual content. Not "IMG_4471.jpg" or generic "boutique hotel room." Use descriptive names: "asheville-boutique-resort-king-suite-balcony.jpg" with alt text reading "King suite with private balcony overlooking the Blue Ridge Mountains, Asheville boutique resort." This serves both visually impaired users and image search ranking.
2. Lazy loading with proper width/height attributes. Images should lazy-load (loading="lazy" on the img tag) but with explicit width and height to prevent layout shift. Cumulative Layout Shift (CLS) is a Core Web Vitals metric that meaningfully affects hospitality rankings.
3. Modern formats (WebP or AVIF) with fallbacks. Modern image formats compress 30-50% smaller than JPEG at equivalent quality. The performance improvement matters for both rankings and conversion.
Mobile experience — beyond responsive.
Mobile-first indexing means Google evaluates hospitality sites primarily by their mobile experience. Two patterns most hospitality sites get wrong:
Booking widget on mobile. The desktop booking widget that works well shrinks badly on mobile. Date pickers become unusable on small screens, guest selectors stack awkwardly, room type selection becomes confusing. The mobile booking widget needs separate design — not just responsive layout.
Image galleries on mobile. Desktop galleries with 30+ images crash mobile browsers or scroll endlessly. The mobile gallery should show 5-8 hero images with an obvious "see all photos" option, not the desktop gallery shrunk down.
The compounding effect.
Individually, each on-page SEO element produces small improvements. Aggregated across 100+ pages of a hospitality site, the cumulative effect compounds. Properties that implement the full checklist on every new page they publish — and audit existing pages against it every 6 months — sustain meaningfully higher organic visibility than properties that treat on-page SEO as a one-time setup task.
The checklist isn't exotic. It isn't proprietary. It's the standard work most hotel sites haven't actually done.
If you want an on-page audit of your property's most important pages — homepage, primary rooms page, top blog posts — that's part of every Digital Fox engagement. Free, no commitment.