Getting found starts
with getting read.

The problem

A site visitors could see. AI couldn't.

Brightwater's original site was built on a no-code app builder that renders everything client-side. A visitor's browser did the work of assembling the page, so the site looked complete on screen.

An AI crawler doesn't run JavaScript the way a browser does. It reads the raw response. For Brightwater, that response was an empty shell: no service descriptions, no pricing, no proof the business existed.

No amount of AI Overview, ChatGPT, Gemini, or Perplexity visibility work fixes anything sitting on top of a page crawlers can't read. That has to get fixed first.

What we built

A foundation built to be read.

We rebuilt Brightwater's site as static HTML, so the content that matters, services, service area, pricing, and contact information, is present in the page itself, not assembled after the fact.

• A single, real contact form that actually delivers to the owner, replacing a setup where one of two forms on the old site didn't send anywhere
• Google Analytics (GA4) installed and Google Search Console set up, with a sitemap submitted, so real performance data starts accumulating from day one
• Service-area content structured for the 40 ZIP codes Brightwater actually serves across St. Petersburg, Clearwater, and mid-Pinellas County
• Google Business Profile work underway to build the entity signals AI platforms look for beyond the website itself

Where things stand

Early, and honest about it.

This case study leads with the foundation, not results, because there aren't real citation or traffic numbers yet to report honestly. Google Business Profile verification is in progress, and the site needs runway to build the kind of history a results-based case study depends on.

Foundation work always comes first. When there's real GA4 and Search Console data behind Brightwater's AI search visibility, this case study gets a second half.