Scottsdale Pools

They own scottsdalepools.com — arguably the best possible exact-match domain for a Scottsdale pool builder. Yet the site doesn't rank in the top 100 for ANY Scottsdale pool keywords: "pool builder scottsdale," "scottsdale pool builder," "custom pools scottsdale az," "pool company scottsdale," and "swimming pool contractor scottsdale" all return nothing.

Build a comprehensive SEO strategy worthy of this domain. Create keyword-optimized service pages for each offering, add location-specific landing pages for North Scottsdale, Cave Creek, Carefree, and Trilogy at Verde River. Optimize the homepage title, meta description, and H1 for primary keywords.

No LocalBusiness, no Service, no FAQPage, no Organization schema. The site has only basic WordPress/Elementor default markup. Google and AI search engines have no structured way to understand what this business is, where it operates, or what services it offers.

Add LocalBusiness schema with name, address, phone ((480) 571-3335), service area (Scottsdale, Cave Creek, Carefree), license number (AZ ROC #339757), and operating hours. Add Service schema for each service offered. Add Organization schema linking to social profiles.

The title tag reads "Scottsdale Pools – Building Lasting Memories!" — a tagline, not an SEO-optimized title. The most valuable real estate in SEO (the title tag on an exact-match domain) is being used for a generic slogan instead of target keywords.

Rewrite the title to "Custom Pool Builder in Scottsdale, AZ | Scottsdale Pools" — leading with the service keyword and location, followed by the brand. Every page should have a unique, keyword-rich title tag.

Zero blog posts. Zero FAQ entries. The site has roughly 8-12 pages with thin content. No educational content to capture informational searches like "how much does a pool cost in Scottsdale" or "best pool finish for Arizona heat." No long-tail keyword targeting whatsoever.

Launch a content strategy with 2-4 blog posts per month targeting high-value informational keywords. Create a comprehensive FAQ page with 20+ questions (and FAQPage schema). Add detailed service pages with 1,000+ words each covering the full scope of each offering.

The gallery/projects page returns a 404 error. For a pool builder, the portfolio is the single most important trust signal — homeowners want to see completed projects before calling. The navigation links to a broken page, creating a dead end for interested visitors.

Create a fully functional gallery organized by project type (infinity pools, spas, water features, outdoor living). Each project should have multiple high-resolution photos, a brief description, location, and features. Add proper image alt text with location keywords.

The site does have a TrustIndex Google review widget (5.0/5 from 11 reviews) but it's buried far below the fold on the homepage, after all other content. Most visitors will never scroll far enough to see it. There's no star rating in the header, no testimonial section with featured quotes, and no AggregateRating schema for search results.

Move the Google reviews higher on the page — ideally right after the hero or services section. Feature 2-3 standout reviews as pull quotes with names. Add AggregateRating schema so Google can display the 5.0/5 star rating in search results. The reviews are excellent (Pam V., Jim N., Pamela K.) — they need to be seen, not hidden.

WooCommerce (ecommerce plugin) is installed and loading its CSS and JavaScript on every page despite having no products for sale. This adds unnecessary code bloat to every page load — extra HTTP requests, unused stylesheets, and JavaScript that will never execute.

Remove WooCommerce entirely, or at minimum dequeue its styles and scripts from all front-end pages. This eliminates unnecessary network requests and reduces page weight. Consider whether any WooCommerce functionality is actually needed.

While overall PageSpeed is decent (90 mobile), the Largest Contentful Paint is 3.3 seconds — above Google's 2.5s "good" threshold. Combined with 73 KiB of unused JavaScript, 24 KiB of unused CSS, and 11 KiB of unminified JavaScript adding to page weight.

Optimize the LCP element (likely the hero image) with proper sizing, next-gen formats (WebP/AVIF), and preload hints. Remove the 73 KiB of unused JavaScript and 24 KiB of unused CSS. Minify remaining JavaScript for an additional 11 KiB savings.

No founder name, no company history or founding year, no team photos, no awards, no certifications beyond the ROC license number. The page uses generic "family-owned" language without substance. Visitors can't connect with real people or verify the company's track record.

Add founder name and story, founding year, team photos with bios, project count, certifications, insurance details, and any awards or association memberships. Include the AZ ROC #339757 prominently. Real people and real numbers build trust.

No llms.txt file, no GEO-structured content, no entity declarations. The site is invisible to ChatGPT, Perplexity, and Gemini when homeowners ask for Scottsdale pool builder recommendations. As AI search grows, this gap will only widen.

Create llms.txt and llms-full.txt files with structured business information, service descriptions, service areas, and project details. Add entity-rich content throughout the site that AI engines can parse and cite. Implement Organization and LocalBusiness schema.

Siteliner found only 9 pages on the entire site with an average of 429 words per page — well below the median of 859 words. The text-to-HTML ratio is just 1%, and there are only 5 internal links per page. The site has almost no content for Google to index and almost no internal linking structure to distribute authority. On the positive side, duplicate content is only 1% with 92% unique content — there just isn't enough of it.

Expand the site from 9 pages to 25+ pages: add dedicated service pages (custom pools, pool remodeling, outdoor living, maintenance), neighborhood/city landing pages (North Scottsdale, Cave Creek, Carefree, Paradise Valley), a blog with educational content, an FAQ section, and detailed project case studies. Each page should have 800–1,200 words of original content.

Siteliner measured an average page load time of 3,484ms — in the 96th percentile, meaning it's slower than 96% of websites analyzed. Despite a relatively small page size (149KB), the WordPress + Elementor + WooCommerce stack creates server-side processing overhead that significantly delays response time.

Remove WooCommerce (no products are being sold), audit and remove unused Elementor widgets and plugins, implement server-side caching, and consider migrating to a static-first framework like Next.js that pre-renders pages for instant delivery.