Blue Wave Pools & Spas

Built on Hibu's proprietary CMS — a closed platform the builder doesn't own and can't control. Cannot install SEO plugins, cannot optimize code, cannot add custom schema, and cannot migrate content without rebuilding the entire site from scratch.

Rebuild on an open platform like Next.js or WordPress where the builder owns their code and content. This unlocks full control over SEO, performance, schema, and design — with no vendor lock-in.

Mobile performance score is 56/100. The Largest Contentful Paint is 7.1 seconds (nearly 3x Google's 2.5s threshold), Total Blocking Time is 720ms (3.5x the 200ms threshold), and Time to Interactive is 21.8 seconds. There's 760ms worth of unused JavaScript and 310ms of unused CSS loading on every page.

Rebuild on a modern framework with static generation, optimized images (WebP/AVIF), code splitting, and zero render-blocking scripts. Target a mobile performance score of 90+.

Ranks #15 for "pool builder scottsdale" — literally one position from being on page 1 where homeowners actually click. Not ranking at all (outside top 100) for 4 other high-intent Scottsdale keywords: "custom pools scottsdale az," "pool company scottsdale," "swimming pool contractor scottsdale," and "pool builder near me scottsdale."

Optimize the Scottsdale landing page with proper H1 targeting, internal linking, and supporting content. Create dedicated pages for each high-intent keyword variation. Build topical authority with blog content targeting Scottsdale pool searches.

The Scottsdale service area page lives at /contact/custom-pool-builder-service-area/scottsdale-az — a deeply nested URL under the /contact/ path. This tells Google this is a contact sub-page, not a primary service page. The page has decent content (~1,200 words) but the URL structure undermines its authority.

Move the Scottsdale page to a top-level URL like /scottsdale-pool-builder/ or /scottsdale-az/. Use proper internal linking from the homepage and navigation. This signals to Google that Scottsdale is a primary market, not an afterthought.

Has basic LocalBusiness and BreadcrumbList schema, but no FAQPage schema for common questions and no Service schema for their pool building services. No way for Google to surface rich results or for AI search engines to cite specific services and pricing.

Add FAQPage schema with common pool building questions and answers. Add Service schema for each service offered (custom pools, spas, renovations, etc.) with descriptions, pricing ranges, and service areas.

No llms.txt file, no GEO-optimized content blocks, no entity declarations. When someone asks ChatGPT, Perplexity, or Google AI Overview "best pool builder in Scottsdale" or "pool builders in Mesa AZ," Blue Wave won't be cited because AI engines have no structured way to discover and reference the business.

Create llms.txt and llms-full.txt with service descriptions, pricing (pools starting at $33,600), service areas, project timelines, and FAQs. Add GEO-optimized content blocks with entity declarations throughout key pages.

5 gallery sections with photos but no filtering by pool type, no project descriptions, no location tags, no cost ranges, and no before/after comparisons. Homeowners browsing the gallery can't find projects similar to what they want or understand the scope and investment of each build.

Add filterable project galleries with detailed case studies: pool type, location, approximate cost range, features, timeline, and before/after photos. Each project becomes a mini landing page that ranks for long-tail keywords.

6 of the 50 crawled pages have noindex meta tags — including video splash pages and an engineering menu page. These pages consume Google's crawl budget without contributing any SEO value, and they dilute the site's overall crawl efficiency.

Remove noindex tags from pages that should be indexed, or remove the pages entirely if they serve no user purpose. Consolidate video content into proper landing pages that can rank. Use robots.txt to block truly internal-only pages.

Siteliner analysis found 33% duplicate content across 89 pages, with only 28% unique content and 39% common content. The text-to-HTML ratio is just 2% (27th percentile) — meaning the vast majority of each page is code, not content. Despite having 958 average words per page, much of it is repeated boilerplate across pages.

Rewrite duplicate service area and service pages with unique, city-specific copy. Each page should have original content tailored to the specific service or neighborhood — not copied and pasted with only the city name swapped. Reduce boilerplate footer and sidebar content that inflates the common content percentage.

No blog, no educational content, no keyword-targeted articles. The site is completely missing the informational search funnel where homeowners research pool building costs, timelines, materials, and design ideas before they ever contact a builder.

Launch a blog targeting high-volume informational keywords: "how much does a pool cost in Arizona," "best pool finishes for Arizona heat," "pool building timeline Phoenix." Publish 2-4 long-form posts per month (1,500+ words) to build topical authority.