Digital visibility audit

What we found, and why it matters

We examined harborsideyacht.com, the site trading as HarborSide Yacht Services, to determine whether its visibility problem is technical, structural, or reputational. It is mostly the third. The website itself is unusually well engineered for a service business of this size.

We reviewed the live site, its raw HTML and response headers, machine-readable files, structured data, and public third-party records. Where a source could not be reached or a claim could not be verified, this report says so rather than filling the gap with an estimate.

The diagnosis

The platform is not the primary problem. The material constraints sit in credibility, legal and tracking governance, navigation, and the absence of independently verifiable proof.

18 indexable URLs 12 are location pages

7 location pages outside global navigation reachable from the sitemap, not the menus

0 editorial or legal URLs no blog, privacy policy, or terms page

5.0 / 42 rating declared by the site not corroborated by a public platform

The short version

The technical foundation is a strength. All 18 sitemap URLs return 200, titles and descriptions are hand written, canonicals are clean, redirects are single-hop, and the site runs as static HTML on Cloudflare Pages.
The rating claim is the highest-risk issue. A 5.0 score across 42 reviews is asserted in structured data and repeated on nine pages, but no independently readable source examined in this audit verifies it.
The site has built depth without building discovery. Twelve location pages carry real local substance, yet seven of them are absent from global navigation and there are no guides or editorial pages.
The governance layer is incomplete. Google Tag Manager is requested twice, there is no Content Security Policy, and tracking runs without a published privacy policy or terms page.
The off-site footprint is too thin to support the on-site claims. Only Yelp and Facebook were confirmed as citations; Yelp shows the business as new with no public review count.

What this means: the company is carrying credibility and governance risk that a technically strong website cannot offset. The evidence does not support blaming the platform for the visibility gap.

Section 1 · Diagnosis

The site is not the constraint

Most audits of small service businesses uncover a weak platform and thin pages. This one is inverted. The code, delivery, and local copy are strong. The weaknesses begin where the company has to be verified by someone other than itself.

01

EngineeringStatic, fast to deliver, no CMS attack surface

Strong

02

On-page SEOClean titles, canonicals, redirects, and local depth

Strong

03

Trust & reputationSelf-declared rating; two verified citations

Constraint

04

GovernanceNo legal pages; duplicate GTM request; no CSP

Constraint

05

Content architectureGood pages, weak navigation, no editorial layer

Unbalanced

06

MeasurementPrivate analytics and field performance not available

Unknown

What is working

Assets worth protecting

No CMS to defend. WordPress probes return 404, assets are first party, and there is no plugin or core-update treadmill.
Clean on-page fundamentals. The sampled pages have unique titles, descriptions, and self-referencing canonicals.
Real local substance. Harbor pages contain market-specific reasoning rather than city-name swaps.
Deliberate AI readability. A hand-authored llms.txt covers scope, pricing, locations, contact, and 16 key links.
Good delivery discipline. One external stylesheet, critical CSS inlined, zero webfonts on the business site, and no chat or booking bloat.
Useful structured data. LocalBusiness, FAQPage, founder, coordinates, offers, hours, and service pricing are present.

What is holding it back

Missing or contradictory proof

The review claim does not meet the public record. The site says 5.0 / 42; the audit could not verify that figure externally.
Seven location pages are orphaned from global menus. The largest content tier is not fully connected.
No editorial or legal pages exist. There is no top-of-funnel content, privacy policy, or terms page.
Local identity is incomplete. No street line appears in the public NAP or PostalAddress schema.
Site claims disagree. “44 marinas” does not reconcile with roughly 27 named across market pages.
Tracking and QA defects are visible. GTM is requested twice, four H1s lose a space, and every sitemap URL shares one lastmod date.

Audit conclusion: no evidence in this review identifies the static platform as the primary constraint. The highest-severity findings sit in verifiable reputation, governance, and internal connection.

Section 2 · Reputation

The claim and the record do not meet

This is the report’s widest gap and its highest-severity finding. The business presents itself as review validated, but the cited proof is not visible on a platform an outside party can independently check.

What the site declares 5.0 / 42

In LocalBusiness structured data and in copy repeated across nine pages.

versus

What the audit verified 0

Publicly countable Yelp reviews. The listing is marked “New on Yelp” and shows 13 photos.

Public Yelp review footprint

Comparable local businesses observed in the source material carry between 25 and 492 publicly countable Yelp reviews.

Comparable local peer · low25

Comparable local peer · high492

HarborSide Yacht Services0

Why this matters now

Policy and conversion risk

Self-serving aggregate ratings—claims sourced only from the company’s own site—are outside search engines’ structured-data rules. Even if the 42 reviews exist elsewhere, the current report could not locate a readable source. Without visible corroboration, the markup invites scrutiny and the copy asks prospects to trust a number they cannot inspect.

Identity risk

The brand term is contested

At least two other “Harborside” yacht businesses occupy the same search space: a similarly named Southern California cleaner and a Connecticut marina and yacht dealership with stronger public channels. HarborSide does not yet own its name cleanly in search.

Platform-by-platform record

Platform	Status	Verified metric	What it means
Instagram	Active	384 followers	Visible channel; last observed post June 1, 2026.
Facebook	Exists	Not retrievable	Login wall prevented a readable count.
Yelp	Exists	0 reviews	“New on Yelp”; 13 photos.
Google Business Profile	Implied	Not verified	Maps URLs appear in schema, but rating and count were unreadable.
Directories	Absent	2 confirmed citations total	No BBB, Angi, Thumbtack, Nextdoor, or confirmed marine-directory listing found.

Why this matters: the site asks prospects and search engines to accept a reputation claim they cannot independently inspect. That creates both credibility risk and structured-data policy exposure.

Section 3 · Architecture & content

Good pages, weak connection

The site is a compact local-service system: one homepage, three service pages, twelve place pages, and two company pages. The local copy is substantive. The problem is that the largest tier is only partly exposed to visitors and there is nothing between “not searching yet” and “ready to buy.”

12321

12 location / harbor3 service2 company1 homepage0 editorial0 legal

Strength

The location tier is not boilerplate

Harbor pages sustain real depth and local reasoning. Burnham Harbor discusses Chicago’s seasonal haul-out cycle—a point that cannot be pasted into a year-round San Diego page. That value is limited by weak internal distribution, not weak writing.

Constraint

Seven of twelve place pages are outside global navigation

Shelter Island, Harbor Island, Point Loma, Mission Bay, Coronado, Oceanside, and Burnham Harbor are present in the sitemap but absent from the header and footer menus.

Structure

Flat sitemap

All 18 URLs sit in one urlset. That is appropriate at this size; no sitemap index or taxonomy is needed yet.

Heading QA

Outlines are inflated

Eyebrow labels are marked as H2s next to the real heading, pushing some inner pages to 19 H2s.

Template QA

Four broken H1 joins

Orange County, Chicago, Shelter Island, and Coronado render with no space before “Yacht.”

What the content system is missing

Gap	Observed evidence	Why it matters
No editorial layer	0 blog, guide, or article URLs across the site.	No page is designed for a prospect researching maintenance, pricing, oxidation, timing, or ownership questions before requesting a quote.
No legal layer	0 privacy or terms URLs while GTM and Facebook resources are requested.	Tracking runs without a published explanation of data collection and use.
Unclear market hierarchy	The homepage says San Diego; other pages sell Orange County and Chicago.	The brand’s primary and secondary markets are not stated consistently.
Conflicting coverage claim	“44 marinas” site-wide versus roughly 27 named across market pages.	Internal contradictions weaken trust and make the service footprint harder to understand.

Why this matters: the site has already paid the cost of producing substantial local pages, but its navigation does not consistently surface them and its content system has no research-stage layer.

Section 4 · Machine readability & delivery

Built deliberately, with a few sharp gaps

The machine-readable layer is the site’s strongest surface. It looks hand assembled rather than inherited from a plugin. The remaining issues are targeted: unsupported rating markup, incomplete entity schema, a meaningless freshness signal, and two tracking defects.

AI & crawlability

What is already right

llms.txt is present and useful. Six sections, 16 links, pricing, service areas, contact, scope, and an explicit negative-scope note.
robots.txt allows ten named AI crawlers. GPTBot, OAI-SearchBot, Claude, Perplexity, Google, and Apple agents are explicitly addressed.
Sitemap and canonicals are clean. All 18 sitemap URLs return 200 and sampled canonicals self-reference.
Structured data is richer than average. LocalBusiness, FAQPage, OfferCatalog, founder, coordinates, opening hours, and pricing are present.

What remains

Gaps in an otherwise strong layer

aggregateRating is unsupported by public evidence. The 5.0 / 42 figure is not externally corroborated.
Entity-level schema is incomplete. Organization, WebSite, and BreadcrumbList are absent.
The freshness signal is not meaningful. Every sitemap entry shares 2026-06-09 as lastmod.
Language and market signals are incomplete. Homepage html lang and hreflang are absent.

Platform and delivery

Surface	Observed state	Judgment
Platform	Custom static HTML · Cloudflare Pages · no CMS	Strength
Rendering	Server-rendered HTML · no hydration shell	Strong
Assets	1 external stylesheet + inlined critical CSS · system fonts	Lean
Redirects	HTTP and www to apex in one 301 hop	Clean
Security headers	HSTS, X-Frame-Options, nosniff, referrer and permissions policies	Good
Content Security Policy	Absent	Gap
Tag management	`GTM-N3LC9SB6` requested by eager and deferred loaders	Risk
Legal pages	Privacy policy and terms absent	Absent

What the evidence rules out

Platform weakness is not demonstrated

The absence of a CMS removes plugin vulnerabilities, abandoned themes, forced upgrades, and common render-blocking bloat. The audit found no platform defect that explains the trust and visibility findings.

What to verify later

Field performance and search demand

PageSpeed Insights returned 429 and Ahrefs was unavailable. No Lighthouse, Core Web Vitals, keyword, backlink, or competitor-SEO conclusion is made here.

Section 5 · Severity & business impact

Where the exposure concentrates

The findings are ranked by the consequence of leaving them unresolved—not by how they should be fixed. Severity reflects credibility, policy, discoverability, measurement, and operational risk observed in the evidence.

Findings by severity Ten findings are ranked by observed consequence. Four sit in the high-severity band.

Critical1

High4

Medium3

Moderate2

Critical and high-severity findings

Material exposure

Severity	Finding	Observed evidence	Business impact
Critical	Unsupported public rating claim	5.0 / 42 appears in schema and on nine pages; no readable third-party source corroborated it.	Structured-data policy exposure and an immediate credibility gap for prospects.
High	Tracking without a published legal layer	GTM and Facebook resources are requested; privacy and terms pages do not exist.	Governance risk around data collection and a visible trust omission.
High	Thin independently verifiable reputation	Two confirmed citations; Yelp shows zero public reviews; Google rating was unreadable.	The business cannot substantiate the trust position its own site presents.
High	Seven location pages outside global navigation	7 of 12 place pages appear in the sitemap but in neither header nor footer.	The largest content tier is harder for visitors and crawlers to discover contextually.
High	Brand-name collision	Two other similarly named marine businesses compete in the same search space.	Brand searches can resolve to the wrong entity, weakening ownership of the company name.

Medium and lower-severity findings

Compounding drag

Severity	Finding	Observed evidence	Business impact
Medium	Duplicate GTM request path	The same container is requested by eager and deferred loaders.	Potentially inconsistent measurement and duplicate initialization.
Medium	No editorial layer	Zero blog, guide, or article URLs across the 18-page site.	The site has no surface for prospects who are researching before requesting a quote.
Medium	Market and coverage claims do not reconcile	San Diego, Orange County, Chicago, and “44 marinas” are described inconsistently.	Prospects and search engines receive conflicting signals about the operating footprint.
Moderate	Incomplete entity schema	Organization, WebSite, BreadcrumbList, language, and street-line signals are absent.	An otherwise rich knowledge layer does not fully define the business entity.
Moderate	Freshness and template QA defects	One lastmod date across all URLs; four broken H1 joins; inflated H2 outlines.	Weak freshness semantics and visible quality defects compound the larger trust issue.

Severity is not a remediation plan. This ranking tells the reader where the business is exposed and why it matters. It intentionally does not prescribe the implementation sequence, platform configuration, or corrective work.

Section 6 · Conclusions & boundary

What this audit can—and cannot—conclude

The evidence supports a clear diagnosis without pretending to supply an implementation scope. The website’s strongest layer is technical. The material exposure sits in public proof, governance, entity clarity, and how the existing content is connected.

Supported conclusion

The platform is not failing

The site is static, crawlable, structurally clean, and delivered through a modern CDN. No CMS or hosting defect observed here explains the trust and visibility findings.

Supported conclusion

The reputation layer is not independently legible

The site’s strongest trust claim cannot be verified in the sources available to an outside prospect, while the broader citation footprint remains thin.

Supported conclusion

The content system is incomplete

Substantial local pages exist, but seven are outside the global menus and no editorial or legal tier exists at all.

Supported conclusion

Measurement confidence is limited

Duplicate GTM loading is observable, but private conversion performance and field speed were outside the available evidence.

Unresolved business facts

Questions the public record cannot answer

The public source, if any, behind the 42-review claim.
The company’s authoritative legal and trading identity.
Whether the business is strictly service-area or operates from a commercial address.
The true priority order of San Diego, Orange County, and Chicago.
The current marina count and exact service footprint.

Open questions

What this audit does not answer

Organic demand: Ahrefs was unavailable, so traffic, rankings, backlinks, and competitor gaps were not measured.
Performance: PageSpeed Insights returned 429 on six attempts; no Lighthouse or CWV score is claimed.
Conversion: there was no GA4, Search Console, ad account, or CRM access.
Exact content size: word counts are extraction estimates, labelled ±20%.
Walled platforms: Facebook and some directory pages could not be read directly.

Engagement boundary: this report intentionally stops at diagnosis, evidence, severity, and business impact. It does not include a remediation sequence, technical specifications, copy changes, platform configuration, directory selection, review-program design, analytics setup, or implementation instructions. Those belong to a separate strategy and implementation engagement.

Appendix A · Page inventory

The underlying page sample

Word counts are text-extraction estimates (±20%). “In global nav” describes the header/footer exposure observed during the audit.

URL	Tier	~Words	H2s	FAQ	Global nav
`/`	Homepage	2,100	10	8	Yes
`/san-diego-boat-detailing`	Location · metro	2,300	10	4	Yes
`/boat-cleaning`	Service	2,200	10	6	Yes
`/boat-detailing`	Service	2,200	9	6	Yes
`/point-loma-boat-detailing`	Location · harbor	2,100	9	6	No
`/oceanside-boat-detailing`	Location · harbor	2,100	9	5	No
`/burnham-harbor-boat-detailing`	Location · harbor	1,850	10	4	No
`/chicago-boat-detailing`	Location · metro	1,800	19	4	Footer
`/shelter-island-boat-detailing`	Location · harbor	1,800	9	6	No
`/contact-us`	Company	1,250	10	4	Yes
`/dana-point-harbor-boat-detailing`	Location · harbor	1,300	9	4	Footer
`/about-us`	Company	475	7	0	Yes

Evidence-based conclusion

Depth is not the weakness

The sampled commercial and location pages commonly fall between roughly 1,300 and 2,300 extracted words, with market-specific detail. The weakness is distribution and connection rather than depth.

Interpretation

Heading counts overstate complexity

Several section kickers are marked as H2s next to their actual headings. The count is therefore partly a semantic-template issue rather than evidence of rich document structure.

Observed business profile

Trading name: HarborSide Yacht Services
Founder: Jake Vavala
Model: Mobile · service at the slip
Markets: San Diego · Orange County · Chicago
Phone: (619) 780-7647
Email: contact@harborsideyacht.com
Services: Boat cleaning · yacht and boat detailing
Street address: Not published

Appendix B · Machine-readable evidence

What was present, absent, and unavailable

Machine-readability files

robots.txt	Present · 10 AI crawlers · Allow: /
llms.txt	Present · 6 sections · 16 links
XML sitemap	Present · 18 URLs · flat urlset
Canonical tags	Self-referencing on sampled pages
llms-full.txt	Absent · 404
site.webmanifest	Absent · 404
hreflang / html lang	Absent on homepage
Sitemap lastmod	2026-06-09 on all 18 URLs

Structured data

LocalBusiness	Present
FAQPage	Present · 8 Q&A pairs
OfferCatalog	Present · 2 services
Person	Present · Jake Vavala
GeoCoordinates	Present
PostalAddress	Locality only · no street line
AggregateRating	5.0 / 42 · self-declared
Organization	Absent
WebSite / BreadcrumbList	Absent

Source ledger

Architecture & on-page: Live crawl of 18 sitemap URLs · raw HTML
Platform & stack: HTTP headers · asset paths · CMS probes
Machine readability: robots.txt · sitemap.xml · llms.txt
Structured data: Homepage JSON-LD blocks
Brand palette: Site CSS custom properties · logo sample
Reputation & citations: Public web search · listing metadata
Organic search performance: Unavailable · Ahrefs not reachable
Core Web Vitals: Unavailable · PageSpeed API returned 429
GA4 / Search Console: No access · none claimed
Backlink profile: Unavailable · none estimated

Method: this was an external, third-party assessment. Every claim in the report comes from a live crawl, raw markup and response headers, or a public source an independent party can re-check. Missing telemetry was omitted rather than modeled.

Measured

All sitemap URLs, redirects, sampled head and body markup, headers, robots, sitemap, LLM files, CMS probes, structured data, public citations, and visible social presence.

Not measured

Private traffic and conversions, keyword and backlink performance, runtime network waterfalls, exact word counts, and Core Web Vitals.

Reader’s rule: “unverified” means the evidence was not available to this audit. It does not mean the underlying claim is necessarily false; it means the report refuses to treat it as confirmed.