Case study — Aquascapes

Thirty years of pool craft,
made findable.

Aquascapes has built and serviced vinyl pools across Waterloo Region since 1994. Its digital presence did not reflect any of it — so we modelled the business as it actually operates, and rebuilt outward from there.

Website traffic

450%

against the pre-rebuild baseline

AI impressions

700%

surfaced by assistants, not just search

Industry

Pool construction, service & retail

Service

Entity-first digital rebuild

Store revenue

4× traffic and revenue

Market

Waterloo Region

01 — The client

A thirty-year pool builder whose reputation travelled by word of mouth.

Aquascapes Recreational Contractors has served Waterloo Region since 1994, building deep technical capability across vinyl-pool construction, seasonal service, maintenance, repairs and a retail store.

It is really several connected businesses — new builds, service, and retail — each with its own customers, decision stages and seasonal rhythm. None of that structure existed anywhere a machine could read it.

At a glance
In business since1994 · 30 years
Service areaWaterloo Region
EngagementEntity-first digital rebuild
Lighthouse99 · 100 · 96 · 92

02 — The challenge

Word of mouth does not carry a business through Maps, AI Overviews and assistants.

Pool construction, service & retail · Waterloo Region · seasonal demand

Traffic was declining and local competition was increasing. Three decades of technical capability and a strong local reputation were not visible to the systems people now use to choose a contractor.

The search environment had moved to Google Maps, search results, AI Overviews, Bing and AI assistants — surfaces that do not reward a reputation they cannot resolve. Nothing in the old presence told them what Aquascapes did, where, for whom, or on what evidence.

A machine cannot recommend what it cannot describe. Thirty years of proof that lives only in customers' heads is, to a search system, no proof at all.

The capability was real. The record of it was not.

03 — The strategy: an entity-first rebuild

Model the business as it actually operates, then build everything else out of that model.

Six blocks, in the order they had to happen. Each is a precondition for the next: you cannot rebuild a Business Profile against an entity model that does not exist yet, and you cannot expose reporting to an agent until there is reporting.

01

Entity modelling

Modelled Aquascapes as it actually operates — legal identity, services, service areas, people, qualifications, certifications, technical knowledge, customer stories, project outcomes, store categories and seasonal workflows. That structure then shaped the content model, the information architecture, the booking flows and the structured data.

02

Google Business Profile rebuild

For a local business the profile is a major public connection point into Google's knowledge graph. Details, categories, services, attributes, service areas and content were rebuilt against the same entity model as the site, so the two agree instead of drifting.

03

The knowledge graph

A relational graph connecting the brand to its legal and operating identity — including the CRA business number — plus sameAs references, service categories, neighbourhoods, customer stories, qualifications and the evidence behind each claim. Shaun's expertise is modelled as knowsAbout relationships over vinyl pools, construction, maintenance, seasonal operation and troubleshooting.

04

Website and operations

A ground-up Astro build with React islands for the interactive journeys: a multi-step booking wizard for openings, closings and maintenance, seasonal and holiday-adjusted scheduling, Stripe payment collection, and neighbourhood pages tied to the customer stories that belong to them.

05

Search and reporting

Google and Bing search setup, entity reconciliation, structured data and automated Business Profile posting. A Google Apps Script engine consolidates GA4, Search Console, Bing Webmaster Tools, Business Profile, Clarity and PageSpeed into one sheet.

06

Agent access

A Cloudflare Worker exposes that reporting as an MCP server, so the numbers can be queried conversationally. The public site carries an API catalogue, an MCP server card, an A2A agent card and WebMCP tools — machine-readable ways for capable systems to discover and use what Aquascapes publishes.

04 — The site, at phone width

Every path a customer takes — research, proof, booking, payment — on the device they take it on.

Astro with React islands for the interactive journeys. A multi-step booking wizard with seasonal and holiday-adjusted scheduling, Stripe payment, and neighbourhood pages tied to the customer stories that belong to them.

The live site, aquascapesrc.ca

The Aquascapes home page at phone width: a dusk pool and cabana photo under the Waterloo Region custom pool builder headline.The mobile navigation menu open on a deep blue panel: About, Build, Services, Pool Gallery and Retail Store links.The pool building process page at phone width: a waterfall and hot tub photo pair above step one, Dream it.A neighbourhood page at phone width: a pool photo over a build conditions list covering soil, water table, lot access and slope.The pool gallery at phone width: aerial photos of the Celebrity and Rectangle builds with photo-count badges.The pool closing service page at phone width: photos of a covered pool above the Covered for winter heading.The retail store page at phone width: a staff member at the counter with a product catalogue.The home page call to action at phone width: a kid mid-jump into a backyard pool above the Ready to start building your dream pool heading.

aquascapesrc.ca

The Aquascapes home page on desktop: a dusk photograph of a lit pool and cabana behind the Waterloo Region's custom pool builder headline.

The live site · aquascapesrc.ca

A Lighthouse report for aquascapesrc.ca scoring 99 Performance, 100 Accessibility, 96 Best Practices and 92 SEO.

Lighthouse · 99 / 100 / 96 / 92

05 — What moved, and how we know

The business did not change. What a machine could say about it did.

Every figure names the system it came from, so each one can be traced back to the place it was measured rather than taken on trust.

AI impressions

700%

The surfaces that answer rather than list — assistants, AI Overviews, agent queries — went from almost never naming Aquascapes to naming it routinely, on a record they could finally resolve.

Reporting engine, AI surfaces · baseline is the pre-rebuild presence

Figure

What moved

Window & source

450%

Website traffic, against the pre-rebuild baseline.

GA4 + Google Search Console

700%

AI impressions — the business being surfaced by assistants and AI answers rather than only by classic search.

Reporting engine, AI surfaces

4×

Retail store traffic and revenue, the part of the business the old site barely represented.

Client-reported retail figures

300%

New-build pipeline — enquiries for the highest-value service line.

Client-reported enquiries

99/100

Lighthouse Performance, with 100 Accessibility (AODA-grade), 96 Best Practices and 92 SEO. Independently re-runnable.

Lighthouse · anyone can re-run it

Not a new coat of paint. A business a machine can describe.

Get your AI Readiness Report ›

What happens next

Get your score, read your report, then map the plan.

Step 1 — See your score

Run a free check of how clearly AI can resolve, trust, and cite you, scored out of 100 across six signals. Your report lands in your inbox, usually within minutes.

Step 2 — Map the plan

We walk through your report, show you where AI hesitates, and map whether the Authority Foundation or the Authority Graph is the right system for your goal. Interpretation and planning, not a sales pitch.