Pool Service Website Template

A pool company’s website has one job that no other trade’s site has: sell a recurring plan, not a visit. The homeowner who lands on a plan page and chooses weekly service is worth $2,400-4,800 a year, and the relationship usually runs for years. A six-second load on that page is the most expensive slow page in home services.

The other thing about pool searches is that half of them are panicked. Green water two days before a party. A pump that stopped in a July heat wave. A liner tear the week before opening. Those searches happen from the backyard on a phone, and the company whose site loads and shows a phone number gets the route slot.

The Pool Template, Honestly

Pool service is not in the launch set, which is roofing, HVAC, plumbing, electrical, landscaping, cleaning, pressure washing, pest control, garage door, and painting. A pool template follows later, free to every owner as an update, and no date is attached. What a pool company gets today is the base those ten templates share, and for a route business that base already does the important work.

Plans as Pages

Out of the box there is a services index and, under it, one plain-text detail page per service. For a pool company the first three services are the plans: weekly, bi-weekly, monthly. Each page carries the visit checklist (skim, brush, vacuum, test, balance, empty baskets, check the pad), the frequency, and the price, with a comparison table in the page body. Each has its own URL, Service schema, and breadcrumb, so “weekly pool maintenance plans” is a real page and not a paragraph on a services overview.

A “start this plan” button leads to the lead form or the multi-step quote wizard. One limit to state clearly: Pro has no payment processing or subscription billing. The site gets the plan chosen and the request in; the first invoice still comes from your route software.

The Green-Pool Request

Behind the request form is the Pro lead engine, a serverless API that runs in your own AWS account rather than a form plugin. A homeowner enters pool type (in-ground or above-ground), approximate size, what they are seeing, and a preferred day, and attaches photos, up to four, shrunk in the browser. One shot of the water and one of the equipment pad tells a tech whether it is a chemistry call or a pump call before the truck moves.

On submit the request goes out as an email, as a Telegram or SMS push to a phone, and as a DynamoDB record; route software that accepts inbound webhooks can take a copy too. The API filters spam on its own, and Turnstile is there if a bot finds the form. The fleet tooling includes a leads CLI for pulling records at the terminal. The sticky call bar keeps the phone number pinned on mobile for the homeowner who would rather talk than type.

Seasonal Pages That Stay Indexed

Opening, closing, and winterization are each a service detail page with a permanent URL. They do not rotate off the site in summer; they wait. The homeowner in Scottsdale who books an opening in February finds the opening page in February. Pair each with a seasonal post in the blog, which ships with tags, author pages, RSS, Article schema, and per-page Open Graph images, and link both to the relevant city page.

Equipment repair follows the same pattern: pump and filter, heater, salt cell, automation, liner. Each is its own page, so “pool heater repair near me” lands on the heater page rather than a generic services list.

Every Stop on the Route

For every city on the route there is a service-area page, and for every service in every city a page of its own (“weekly pool cleaning in Gilbert”); the local SEO engine builds the list from Census place names. Any page that cannot justify its URL is stopped by the build gate, and the content audit catches near-duplicates before deploy. Scottsdale, Chandler, Gilbert, and a dozen more become real pages, or the build reports which ones need something specific to say about pools in that city.

What Else Ships With Pro

• Home, about, blog, contact, thank-you, privacy, 404
• Widgets: estimate calculator (a plan-price example by pool size), quote wizard, reviews carousel for your existing reviews, before/after gallery for green-to-clear pairs, and the sticky call bar
• JSON-LD covering Organization, WebSite, Service, Article, FAQPage, and BreadcrumbList; per-page OG images; sitemap, robots.txt, RSS, llms.txt, web manifest
• Optional GA4, GTM, and Clarity, each a config switch, plus six design switches
• Fleet tooling for a multi-route operator: new-site scaffolder, cross-site verifier, S3 and CloudFront deploy for AWS, a leads CLI
• CLAUDE.md, AGENTS.md, seventeen docs, and four Claude Code skills
• Astro 7, Tailwind CSS 4, TypeScript, no JavaScript framework on the page, Lighthouse 100 enforced in CI

Storm Week

After a severe storm knocks out pumps across a metro, pool repair searches spike in an afternoon. A WordPress site on shared hosting slows or errors at that moment because every visitor triggers database queries and a PHP process. An Amrify site is static files on a CDN with a serverless API behind the form; five thousand visitors in an hour see the same sub-second page as fifty. The company whose site stayed up during storm week is the one that fills the route with repair calls that become plan customers.

Measuring the Current Site

A WordPress pool site with a visual builder, a form plugin, an SEO plugin, and shared hosting loads in four to nine seconds on a phone and scores 25-55 on Lighthouse. Hosting is $15-40 a month and plugins $80-250 a year; three years cost $1,200-3,500. The Amrify base build hosts free on Netlify, Vercel, or Cloudflare Pages and costs $249 once for founding members.

Run the free grader on your site before deciding. In about thirty seconds, and without asking for an email, it runs Google’s PageSpeed test the way a phone would see the page, returns the four Lighthouse scores, and checks structured data, SSL expiry, robots.txt, and the sitemap. The slow website cost calculator puts your traffic and a plan customer’s annual value into the same math. For a company already on WordPress, the migration guide covers moving the plan pages and keeping the redirects.

Launching Before Opening Season

Lock in the founding price. There is no checkout yet, so a free account is the hold on a $249 spot. The 5,000th member closes the founding window; from then on checkout charges $399. At release the private repo is linked from your account dashboard. A seat covers one person’s repo access.

Write the company in. Name, phone, address, and hours go into config. Write the three plan pages with checklists and prices. Write the opening, closing, and winterization pages. Add equipment repair pages. Add your route cities; the scaffolder seeds each one from Census data. Load green-to-clear pairs into the gallery. Write the first chemistry post. “Add a salt cell replacement page with a three-to-five-year lifespan note” is a sentence the repo’s Claude Code skills can act on; Cursor and Copilot work from the same CLAUDE.md.

Deploy and route requests. Once the GitHub repo is linked to Netlify, Vercel, or Cloudflare Pages, the site is up with SSL. The lead API runs serverless in an AWS account you own. Point Telegram or SMS at the tech on call and the webhook at your route software if it accepts one.

Watch the score across the season. The free account includes the Website Monitor; add the site there. Its watch list takes up to thirty sites, keeps a score history for each, re-tests any of them on a click, and retains the last ten results. Nothing runs on a schedule and nothing alerts you, but after a storm week of quick edits it is the fastest way to confirm the site still scores 100.

Pool Companies This Fits

A solo tech building a route. The site’s job is to sell the plan while you are in someone’s backyard: priced plan pages, a photo-taking request form, and a number pinned to the screen, all for one payment.

A cleaning company adding repair and renovation. Heater, pump, salt cell, automation, liner, remodel: each is a page with its own URL and its own service-in-city pages, so the repair side ranks separately from cleaning and feeds the plan side.

A franchise or multi-territory operator. Every territory runs as its own site inside the monorepo, with separate plans, phone, and cities on the shared codebase and brand. One edit to the request form reaches every territory, and there is no per-site fee.

The codebase is Alex Crabinsky’s; he works from Alpharetta, Georgia, and wrote it after more than ten years in production web work. The company’s own live sites, from roofers to glass shops to exterior cleaners, sit on it, every one public and gradeable. The developer.

Frequently Asked Questions

Can I present weekly, bi-weekly, and monthly plans with prices?

Yes, as service detail pages you write. Each plan is a plain text file with what the visit includes, the frequency, and the price, and each gets its own URL with Service schema and a breadcrumb. There is no plan-comparison component in the base build; a table in the page body does the comparison. Sign-up goes through the lead form or the quote wizard, and there is no online payment or subscription billing in Pro, so the first invoice still comes from your route software.

Is there a pool service template today?

Not as a finished layout. At launch there are ten, all home-service trades: roofing, HVAC, plumbing, electrical, landscaping, cleaning, pressure washing, pest control, garage door, and painting. Pool companies get a template of their own later, free with the updates that every owner receives, and no date has been set. Until then a pool company works from the base those ten share: service pages for plans and seasonal work, the lead engine with photos, the sticky call bar, the before/after gallery, and city pages.

Can a homeowner send a photo of a green pool with the request?

Yes. Four photos can go with a Pro lead request, shrunk in the browser so they upload quickly from a backyard. A picture of the water and one of the equipment pad tells a tech whether it is a chemistry call or a pump call before anyone drives out. Email, a Telegram or SMS push to a phone, and a database record all happen on submit, and route software that accepts a webhook can get a copy.

How do opening and closing pages work?

Each is a service detail page with its own URL: spring opening, fall closing, winterization, and whatever else your climate calls for. They stay indexed all year, so the homeowner who books in February finds the opening page in February. The local SEO engine also generates a seasonal-service-in-city page for every city you serve, gated so a thin one fails the build.

What does Pro cost for a pool company?

A single payment: $249 for the first 5,000 founding members, $399 afterward. For that you get one seat with no site limit, the lead engine and the local SEO engine, the five widgets, and lifetime updates, the pool service template among them. Netlify, Vercel, and Cloudflare Pages will host the static site for nothing. Custom pool sites run $3,000-8,000; WordPress with hosting and plugins costs $1,200-3,500 over three years, which is less than one maintenance customer’s first year.

Can I rank in each city on my route?

Yes: a service-area page for each city and, layered on top, a page per service per city (‘weekly pool cleaning in Gilbert’). The local SEO engine seeds the list from Census place names, and the build gate turns thin pages away, so twelve cities become twelve pages with something to say about pools there, or a build report listing the ones that still need it. A content audit flags near-duplicates before deploy.

Is any coding involved?

No. Config holds the company name, phone, address, and hours. Plans, seasonal pages, equipment repair pages, and water chemistry posts are plain text. Cities are one file each, started by the scaffolder. With the CLAUDE.md and four Claude Code skills that ship in the repo, an assistant can draft the salt cell replacement page from your notes; Cursor and Copilot read the same files.

How fast can a pool company be live?

With plan details and pricing ready, a day. The sequence is cloning the private repo, filling config, writing the plan and seasonal pages, adding equipment repair pages and cities, dropping in photos, and deploying; hosting setup takes roughly thirty minutes of it.

Two brands or two territories on one purchase?

Yes. Unlimited production sites come with the one seat. Each brand or territory gets its own monorepo entry, with plans, phone, and cities of its own on the shared codebase; change the request form once and all of them have it at the next build.

---

Related solutions: Landscaping | Pest Control | Pressure Washing | Fencing

The Showcase lists the production sites on this codebase. Every term is on the prices page.

Not sure Amrify is right for a pool service business? The comparisons against WordPress, Wix and Next.js are honest about where each one beats Amrify.

Take a founding spot above, or send a note describing your route setup. The solutions page lists launch trades and update trades together.