Sample SEO Audit — Anonymous Boutique Inn

This is a real audit Paaseki produced for an actual client, with identifying details replaced with placeholders. It runs roughly 4,000 words across an executive summary, full strategic analysis, and a 90-day action plan with 30+ specific findings. This is what your audit will look like.

---

Executive summary

You own something rare: two historic buildings in central Virginia — the North Building and the South Building — operated under one brand, sitting between a major national park, the popular hike, and central Virginia wine country. That combination is a real edge. Historic boutique lodging is one of the few categories where independent operators can decisively beat Airbnb, Booking.com, and chain hotels, because the product itself is unique. A traveler searching "historic inn near the national park" or "where to stay before climbing the popular hike" is looking for exactly what you have, not a Hampton Inn off the interstate.

The problem is your website is doing almost nothing to communicate that edge to Google. Every page is missing a meta description. No page has a detectable H1. The homepage title is a generic "[Anonymous Inn]" with no keywords. There's a typo in a title tag ("[typo on this page]" on the South Building history page). One internal URL returns a 404. There's no structured data identifying the properties as lodging. There's no events page, no the popular hike basecamp page, no winery itinerary content, and no blog. The site is essentially invisible for the high-intent searches your edge is designed to win.

The opportunity is large and reachable. With roughly 25 focused fixes over 30–60 days, this site can plausibly capture a meaningful share of the area lodging traffic that currently routes to OTAs and competing inns in a neighboring town and a neighboring town. Most of the highest-impact fixes take an afternoon, not a quarter.

The rest of this report walks through what's wrong, what to fix first, and what to build over the next 90 days. Findings are referenced inline by ID (F001, F002, etc.) and detailed in the structured findings list that accompanies this report.

Scope and methodology

This audit crawled the 12 indexable URLs on [client domain]: the homepage, both property pages, both history pages, About, Things To Do, Area Dining, Availability, Contact Us, the Cart page, and one orphan URL (/south-building-old) that returns a 404. For each page we captured the title tag, meta description, heading structure, body content signals, and on-page link patterns.

The audit applies several standard SEO frameworks against the crawl:

• On-page fundamentals: title tags, meta descriptions, heading hierarchy, internal linking, image alt text, canonical signals.
• Technical health: HTTP status codes, redirects, sitemap and robots.txt, indexability of utility pages, Core Web Vitals (Squarespace handles most of this well by default).
• Structured data: schema.org markup, particularly LodgingBusiness, Organization, FAQPage, and aggregateRating.
• Local SEO: NAP (name, address, phone) consistency, Google Business Profile signals, local content depth.
• Competitive positioning: where this business can plausibly win against direct competitors, OTAs, and content aggregators.
• Hidden revenue analysis: search demand the site is not currently capturing despite having the product to satisfy it.

Two important data gaps to flag. First, this audit did not have access to your Google Search Console or Google Analytics, so I can't tell you which queries are currently driving impressions or where you rank today. Setting up Search Console (if you haven't already) is finding F026's underlying recommendation. Second, several pages — /availability, /contact-us, /about, /area-dining — returned little crawlable body content, likely because content is loaded inside Squarespace blocks the crawler couldn't fully render. I've flagged where this matters and made conservative assumptions; in some cases ground-truth verification by you is needed before action.

Throughout the report, finding IDs in parentheses (like F003) point to the structured findings list at the end. That list contains the exact current state, the exact recommended state, and Squarespace-specific instructions for every issue.

Platform and technical health

You're on Squarespace, and that's fine. For a two-property historic inn, Squarespace is a reasonable choice: it gives you mobile-responsive design out of the box, built-in SSL and CDN, decent Core Web Vitals without effort, first-class per-page SEO fields, and per-page Code Injection blocks for things like custom JSON-LD. Nothing about this audit suggests you should move platforms.

That said, Squarespace has constraints worth understanding. It auto-appends your site title to every page title (" — [Anonymous Inn]"), which eats roughly 30 characters of your 60-character budget — so your "real" title text needs to be tight. Page-level meta descriptions live behind a gear icon in Page Settings > SEO, easy to miss and easy to forget. Image alt text must be set per-image with no bulk tools. URL changes don't auto-redirect; you have to add 301s manually under Settings > Advanced > URL Mappings. None of this is a dealbreaker, but it explains how your site got into its current state: the SEO controls aren't broken, they're just easy to skip during a launch.

The technical findings break into a few groups.

A 404 leaking link equity. /south-building-old returns a 404 (F003). This is almost certainly an old URL that was renamed to /south-building when the site was reorganized, and the redirect was never created. Anyone who bookmarked the old URL, linked to it, or cached it in search results hits a dead end. The fix is one line in Settings > Advanced > URL Mappings.

An indexable cart page. /cart returns a 200 and was crawled (F030). Cart and checkout pages serve no SEO purpose and dilute the site's topical signal. Mark it noindex.

Sitemap and Search Console. Squarespace generates /sitemap.xml automatically, but you should verify it loads cleanly, that it excludes /south-building-old after you redirect it, and most importantly that it's submitted in Google Search Console (F026). If you don't have Search Console set up, that's the first technical step — without it you're flying blind on what Google is actually doing with your site.

URL slug awkwardness. /south-building drops the word "Inn" — the actual keyword (F024). I'd consider /south-building as the cleaner canonical slug, but only change it once and add 301s. URL churn is more damaging than a slightly suboptimal slug.

Brand consistency. Your domain compresses the brand to "[client brand]" while titles use "[Anonymous Inn]" and informal references probably use "[Anonymous Inn]" (F027). Pick one canonical brand string and use it identically across the site, Google Business Profile, Facebook, Instagram, Yelp, and Tripadvisor. Inconsistencies fragment the entity signals Google uses to recognize you as one business.

What you don't have to worry about: page speed, mobile responsiveness, HTTPS, basic crawlability, or template-level Core Web Vitals. Squarespace handles those, and the crawl confirmed nothing is broken there.

On-page SEO and content

This is where the gap between what you have and what you should have is widest, and also where the fastest wins live.

Every page is missing a meta description. All 11 indexable pages returned no meta description (F007). Google is fabricating snippets from whatever on-page text it can find. For a homepage this is a CTR tax. For property pages — your highest-converting pages — it's the single most expensive small mistake a lodging site can make (F004, F005). A traveler comparing your search result to a competitor's sees their crisp, persuasive 160-character pitch and your snippet of nav text. Meta descriptions don't drive ranking directly, but they directly drive click-through rate from the rankings you do have, and that's the entire point.

This is also the highest-leverage afternoon of work in this audit. Eleven descriptions, 140–180 characters each, three to four hours of careful writing, and the entire site improves overnight.

Title tags need work, starting at the top. Your homepage title is just "[Anonymous Inn]" (F002) — pure brand, no differentiator, no targeting. The homepage is the strongest-authority page on your site. Its title is supposed to do work. Here's the comparison:

Page	Current	Recommended
Homepage	[Anonymous Inn]	Historic Inns in central Virginia | [Anonymous Inn] — the North Building & the South Building
South Building history	History of the South Building Buiding — [Anonymous Inn]	History of the South Building Building, [the town] VA | [Anonymous Inn]
the North Building	Historic the North Building — [Anonymous Inn]	(current is acceptable; ensure meta description carries the keywords)

That typo on the history page — "[typo on this page]" instead of "Building" — is showing in browser tabs and search results today (F006). It's been there long enough that it's been crawled. For a property whose entire pitch is restoration, craft, and care for detail, a visible typo on a tab is a small credibility leak that costs nothing to fix.

No detectable H1s anywhere. The crawler couldn't find an H1 on any page (F008). This may partly be a Squarespace template choice — some templates wrap banner subtitles in spans rather than H1s — but the practical effect is the same: search engines have to guess each page's main topic from weaker signals. Open each page in the editor, ensure the top textual heading is set to "Heading 1" (not Heading 2 or banner styling), and verify by viewing the page source in your browser. On the property pages, the H1 should include the property name and the location: "The Historic the North Building: A Restored Home in central Virginia."

Several pages are likely thin. /availability, /about, /contact-us, and /area-dining all returned essentially no body content to the crawler. Some of this is a rendering limitation, but where it reflects reality, it's worth fixing.

• The Availability page is bottom-of-funnel — people who land here are ready to book (F016). It shouldn't be just an embedded calendar widget. Add a paragraph naming both properties with rate ranges, two photos, and "book direct" benefits (no fees, best rate guarantee) above the calendar.
• The About page is your E-E-A-T page (F021). On owner-operated lodging sites, Google looks here for evidence that real, accountable people are behind the business. Tell the operator story, the restoration story, why [the town]. 400–600 words and a photo of you.
• The Contact page must show full NAP — name, address, phone — for both properties in plain HTML text (not in an image), with embedded Google Maps for each (F017). This is foundational local SEO.
• /area-dining and /things-to-do should be expanded into genuine local-content hubs, not name-only lists (F020, F028). Two to three sentences per restaurant; for Things To Do, restructure into sections (Hiking, Wineries, Dining, Events) that each link out to deeper pages once those exist.

Internal linking between history and booking is unclear. You have history pages (real moat content) and property pages (booking pages), and they should be tightly cross-linked (F019). Every history page should end with a "Stay at the [property name]" CTA. Every property page should link to "Read the history of the [property name]" in-content. The history content is what makes a curious traveler want to book; close the loop.

Property pages need a clear primary CTA. Above the fold on each property page, a single high-contrast "Check Availability" button (F029). On mobile, consider a sticky version. CTA prominence is the largest single conversion lever on lodging property pages after photos.

Local SEO and competitive landscape

You're competing in a layered market and the strategy needs to match.

For pure "[the town] VA lodging" searches, your direct competition is a small handful of local B&Bs and vacation rental listings on Airbnb and VRBO. For broader searches that include the national park or the popular hike, the competitive set widens to inns in a neighboring town (gateway to the central park entrance), a neighboring town, a neighboring town, and a neighboring town — places with established inns that have years of content, reviews, and link equity behind them.

Here's the honest assessment of who you can outrank and who you can't.

Plausibly outrankable in 6–12 months: other independent the area B&Bs and vacation rentals, generic Airbnb listings (which can't rank for branded historic-property queries by design), and aggregator pages with thin content. The branded long-tail — "historic inn [the town] VA," "the South Building," "the North Building [the town]" — is yours to own once the on-page basics are fixed.

Not realistically outrankable in the short term: Booking.com, Tripadvisor, Airbnb category pages, the National Park Service. Don't try to fight them on generic terms like "the national park hotels."

The strategy this implies: dominate long-tail queries that combine "historic," "[the town] VA," and a specific intent (the popular hike, wineries, weddings, dining, events). Win the geo-qualified searches that OTAs are too generic to rank for. Don't fight head-to-head on broad terms.

That brings us to local SEO, where the biggest single lever is off-site.

Google Business Profile is probably the highest-impact thing not on your website. No GBP signals are visible on the site — no review widgets, no GBP links, no review schema (F018). I can't verify GBP status without access, but for local lodging searches GBP often outweighs the website itself in driving bookings. Two well-managed listings (one for each property, assuming distinct addresses) will move more bookings than any single on-site change in this audit.

What "well-managed" means concretely: claimed and verified, complete hours, full address, accurate phone, 20+ photos including exterior/interior/rooms, every amenity field populated, weekly Posts (yes, weekly), Q&A section seeded with real questions, booking link integrated, and review velocity actively managed. Add the GBP review URL to your site footer and to your post-stay email — review accumulation is what compounds local rankings over time.

NAP consistency. Whatever address and phone format you use on your GBP, use the exact same format on your Contact page, in schema markup, and across every directory citation (Yelp, Tripadvisor, Facebook, etc.). Inconsistent NAP fragments your entity signals.

Local content is sparse. A traveler researching the area lodging gets very little local context from your current site. The /area-dining and /things-to-do pages exist but are thin (F020, F028). There's no winery content (F014), no the popular hike content (F013), no event content (F012). Each of those is both a hidden revenue opportunity (covered below) and a local relevance signal that helps you rank for the geo-qualified queries that OTAs can't win.

Structured data

Schema markup is how you tell Google "I am the same kind of entity as the inns you already know how to rank." For lodging, this matters more than for most categories because Google has lodging-specific result features (rate displays, availability badges, star ratings) that only fire when the structured data is in place.

You currently have none of it on the property pages (F009). Both /north-building and /south-building should carry LodgingBusiness JSON-LD (or BedAndBreakfast, if that's the more accurate type) with at minimum:

• name, url, image (multiple high-quality photos)
• address (street, city, state, postal code, country)
• geo (latitude, longitude)
• telephone
• priceRange (e.g., "$$" or a numeric range)
• amenityFeature (WiFi, parking, breakfast, etc.)
• checkinTime and checkoutTime
• numberOfRooms
• aggregateRating once you have 5+ reviews aggregated

The homepage should carry an Organization or LocalBusiness schema block tying brand to address, phone, logo, and sameAs links to your social profiles (F010). This goes in Settings > Advanced > Code Injection > Header so it applies sitewide.

For the Contact page and parts of Things To Do, FAQPage schema is worth adding once you create FAQ content (F011) — questions like check-in time, pet policy, parking, kid-friendliness, distance to the popular hike, distance to the scenic drive. FAQ rich results take additional SERP real estate and capture long-tail question queries that often have high booking intent.

In Squarespace, all of this goes into per-page Code Injection blocks under Page Settings > Advanced > Page Header Code Injection as <script type="application/ld+json">…</script>. Validate each block with Google's Rich Results Test after you publish.

This is roughly a half-day of work for someone who's done it before. Once it's in place it doesn't need ongoing maintenance, except to update aggregateRating as your review count grows.

The event-venue gap

Now to the largest hidden-revenue opportunity in this audit, which the rest of the recommendations build toward.

Two historic properties under one brand is an unusual asset. It's a natural fit for wedding parties, family reunions, milestone birthdays, corporate retreats, and small group bookings where guests want to be co-located but in two distinct, characterful buildings. [the town] sits in the middle of a wedding-venue corridor — multiple wineries and farm venues within a 20-minute drive host weddings every weekend in season. Wedding parties searching "lodging near [venue name] [the town] VA" right now have nowhere on your site to land.

There is no events page. No "book the whole property" page. No wedding-accommodations page. No reunion landing page (F012). This is a significant gap because group bookings drive 3–7x the revenue of a one-night transient stay, and they convert from a much longer, planning-stage search journey — meaning content has time to do its work.

What this looks like in practice: a /weddings page (or /events, or /book-the-whole-property — pick one and own it) that targets queries like "wedding accommodations [the town] VA," "reunion lodging near the national park," "book entire property [the town] Virginia." It needs to cover total capacity across both properties, your approach to whole-property bookings (rate structure, minimum nights, deposit terms — even directional), 2–3 sample itineraries (rehearsal dinner Friday, ceremony Saturday, brunch Sunday), inquiry form with the right qualifying questions, and a few photos that suggest "this is a place you'd put your in-laws and your college roommates and feel good about both."

The secondary opportunity is the wine-and-outdoor itinerary traveler (F013, F014). the popular hike is one of the most-searched hikes on the East Coast, and [the town] is a credible basecamp — closer to the trailhead than most a neighboring town lodging, and 30 minutes from the east entrance to the national park. A page targeted at "lodging near a popular hiking destination" and "where to stay before climbing the popular hike" with content covering distance to trailhead, the parking permit requirement, pre-hike breakfast options, and tips for early-start hikers would capture seasonal traffic that converts well — hikers usually book multi-night stays with a buffer day on either side of the climb.

Same logic for wineries. the county is in the heart of Virginia's central wine corridor — a regional winery, another regional winery, and others within 20 minutes. A /wineries page or expanded section on Things To Do that lists the wineries with drive times from each property, plus a sample 2-day itinerary, captures planners who are searching "lodging near a regional winery" and similar venue-named queries.

These three content investments — events, the popular hike, wineries — are the strategic core of the next 90 days of work. They are the pages that will earn long-tail traffic Google currently sends to OTAs and aggregators because no one in your micro-geography is bothering to write them well.

Recommendation: rebuild vs. fix in place

Fix in place. Don't rebuild.

This is a Squarespace site with reasonable bones, decent design, working booking flow, and no fundamental architectural problems. The issues this audit identifies are content and configuration issues, not platform issues. None of them require a redesign. None of them require migration to WordPress or a custom build. Almost all of them are field-edit tasks: writing meta descriptions, fixing a typo, adding redirects, pasting JSON-LD into Code Injection blocks, expanding thin pages, creating new pages.

A rebuild would cost you 2–3 months of momentum, several thousand dollars, and the loss of whatever indexing equity the current URLs have built up. You'd come out the other side with the same content problems unless you also did the writing work — which is the actual work.

The one thing worth flagging: if you ever do consider a future rebuild (say, in 18 months when you've outgrown the template), the things to look for would be (a) a platform with better structured-data tooling so you don't have to maintain JSON-LD by hand, (b) a more sophisticated booking integration if your direct-booking volume grows, and (c) a proper blog/CMS so the content cadence becomes routine. None of that is urgent. The current site can carry you well past your current revenue level if the gaps in this report are filled.

What I'd recommend instead of a rebuild: treat the next 60 days as a focused content and configuration sprint, then evaluate based on Search Console data what to do over the following six months.

Action plan

The findings break into two phases: things to ship this week (configuration changes, fast content writes) and things to build over a 60–90 day compounding period (new pages, schema buildout, GBP discipline, blog cadence).

Phase 1 — Ship this week. These are mostly low-effort, high-impact configuration and copywriting tasks. A diligent owner-operator can get through this list in 8–12 hours of focused work; with AI assistance for the copywriting drafts, less.

• Write and add meta descriptions for all 11 pages (F001, F004, F005, F007). This is the single biggest lever on the list.
• Update the homepage title to lead with "Historic Inns in central Virginia" (F002).
• Fix the "[typo on this page]" typo on the South Building history page (F006).
• Create a 301 redirect from /south-building-old to /south-building (F003).
• Mark /cart as noindex (F030).
• Add Organization JSON-LD sitewide via Code Injection (F010).
• Verify /sitemap.xml is clean and submit it in Google Search Console; if Search Console isn't set up, set it up first (F026).
• Add NAP and embedded Google Maps to the Contact page (F017).
• Pick one canonical brand string and align site, GBP, and social profiles (F027).
• Upload high-quality social share images per page (F023).

By end of week one, every page has a description, the homepage has a real title, the typo is gone, the 404 is fixed, the cart is deindexed, the sitemap is submitted, and your brand entity signals are consistent. None of that is glamorous. All of it compounds.

Phase 2 — Compounding period (30–90 days). These items take more work and produce returns over weeks and months as Google recrawls, indexes new pages, and travelers respond to them.

• Add LodgingBusiness JSON-LD to both property pages (F009).
• Build out the property pages: H1s, expanded body content, alt text on every image, prominent "Check Availability" CTAs above the fold (F008, F015, F029).
• Improve the Availability page above the calendar widget (F016).
• Expand the About page to 400–600 words with the operator and restoration story (F021).
• Tightly cross-link history pages and property pages with descriptive anchors (F019).
• Restructure /things-to-do as a hub and expand /area-dining (F020, F028).
• Build the events/weddings/groups page (F012) — the highest-revenue new page.
• Build the the popular hike basecamp page (F013).
• Build the winery itinerary content (F014).
• Add FAQ content with FAQPage schema on Contact and/or property pages (F011).
• Surface 3–5 testimonials on the homepage and property pages; add aggregateRating to schema once 5+ reviews are aggregated (F025).
• Claim, verify, and fully populate Google Business Profiles for both properties; establish a weekly Posts cadence (F018).
• Launch a /journal blog and commit to 1–2 posts per month: seasonal the popular hike content, wine country itineraries, local events, restoration stories from each building (F022).
• Optionally clean up the /south-building slug to /south-building — but only once, with redirects (F024).

A few honest notes on timeline. Configuration changes and on-page edits show up in Search Console within days to weeks as Google recrawls. New pages typically take 3–8 weeks to find their footing in rankings, sometimes longer for competitive queries. Google Business Profile changes can take a week or two to propagate, and verification by postcard (if Google requires it for either property) can add another week. Reviews and the rankings benefit they confer accumulate over months — there's no shortcut.

AI tools can dramatically accelerate the writing tasks here: meta description drafts, title tag variants, page copy first drafts, FAQ content, JSON-LD generation. What AI can't do quickly is the original ground truth — the year each building was restored, the actual room counts, your real check-in policy, the specific stories that make each property feel like a real place. Plan to spend a few hours feeding that information in once, in a single document; everything else cascades from there.

The site has good bones and a real moat. Most of what's wrong is cheap to fix, and the content investments that aren't cheap are the ones that build the durable advantage. Start with this week's list. The rest follows.