AtlasForge growth plan
A 700-page web surface that turns 70 years of reputation into local search dominance.
Cameron's Flower Shop already has the brand: 4.9★ from 1,194 reviews, 11 service-area cities, 50+ named B2B accounts at hospitals and funeral homes. What it doesn't have is a web surface that ranks for the searches its customers actually run. This page outlines what Cameron's looks like once we build that surface.
The thesis in one paragraph.
A 70-year, family-owned florist with 1,194 five-star reviews, 11 service-area cities and 50+ B2B accounts is a 5–10× outcome on the same revenue base if we redirect the existing brand equity into pages Google can rank. The current site (a templated Flower Shop Network storefront identical to thousands of other florists) is so generic that even a moderate Atlas execution — modern IA, schema-rich pSEO, four cornerstone content guides, and a real B2B inquiry path — defends a "double the inbound calls" pitch. This page is the proof.
Nine pSEO axes. ~700 pages. Real local intent.
Every axis maps to actual searches the regional market is already running. None of these pages are filler — each one targets a specific intent, surfaces specific real-world facts (hospital protocols, funeral home addresses, neighbourhood geography, holiday cutoffs), and converts a known recipient profile.
| Axis | Pages | Formula | Priority |
|---|---|---|---|
| Service × City | 88 | 8 services · 11 cities | A — primary spine |
| Occasion × City | 242 | 22 occasions · 11 cities | A — primary spine |
| Hospital × Get-well | 50 | 50 named facilities · 1 city | A — already harvested from existing site |
| Funeral home × City | 25 | ~25 funeral homes · 1 city | A — high B2B intent |
| Holiday × City | 154 | 14 holidays · 11 cities | B — seasonal |
| Anniversary year × Flower | 25 | 1st – 50th, traditional flower | B — evergreen content |
| Wedding venue × Service | 60 | ~30 venues · 2 services | B — needs venue research |
| Flower meaning / colour symbolism | 30 | evergreen guides | C — content marketing |
| Flower type × Occasion | 80 | 10 flower types · 8 occasions | C — long-tail |
| Total estimated pages | 754 | Atlas-tier delivery target. Empire upgrade can extend this to 1,500–2,000 pages. | |
Fifteen proof routes shipped in this rebuild.
The routes below ship in the Atlas Stage 2 build. They prove all four pSEO templates (service × city, hospital × occasion, funeral home × city, holiday × city), surface the most-defensible assets (history, reviews, B2B verticals, recurring revenue), and deliver fifteen before/after comparisons against the live FSN site for the demo brief.
- /
Home — proof of design system, 4.9★ trust bar, three-window delivery promise
- /about
Family-ownership narrative, 70-year story, real Cameron's interior photo gap flagged
- /services
Services hub linking to every service line, every delivery city, every B2B vertical
- /services/sympathy-flowers
Sympathy hub with same-day funeral home delivery promise + funeral home shortlist
- /services/sympathy-flowers/funeral-home-delivery/kitchener
First funeral home × city pSEO proof template
- /services/wedding-flowers
Consultation-led wedding florist hub
- /services/get-well-flowers
50+ care facility hub with floor-aware delivery protocol
- /services/get-well-flowers/hospital-delivery/grand-river-hospital
First hospital × occasion pSEO proof template
- /services/local-flower-subscription
Recurring-revenue product LP (currently buried on the live site)
- /services/birthday-flowers
High-volume occasion proof page
- /services/anniversary-flowers
Original-content proof — flower-by-year + colour meaning
- /services/flower-delivery/waterloo
First service × city pSEO proof template
- /services/holidays/mothers-day-flowers-kitchener
First holiday × city pSEO proof template
- /reviews
AggregateRating schema + filterable testimonials from the 1,194-review pool
- /contact
Three-window promise, B2B inquiry path, 50-facility blurb, embedded map
The data model that makes 700 pages tractable.
Every pSEO page is generated from typed data. Adding a new city, a new facility, or a new occasion is a single record change — and the site rebuilds the corresponding pages, updates the sitemap, and pushes the canonical URL to Google. No CMS plate-spinning. No content sprawl.
- Cities — name, slug, neighbourhood list, drive time from shop, anchor copy, sample reviews filter.
- Services — name, slug, schema serviceType, hero copy, FAQ set, product collection, intent-tier (transactional / consideration / awareness).
- Care facilities — name, slug, address, postal, phone, category (hospital / hospice / retirement / care / clinic), unit-restriction notes.
- Funeral homes — name, slug, address, city, religious-tradition tag.
- Holidays — name, slug, date pattern, peak-window flag, city-permitted set.
- Products — id, name, category, image, price, FSN deep-link.
- Reviews — author, rating, category, occasion, body — filterable per service / city / facility.
The content engine that supports the surface.
A pSEO surface alone is not a content strategy. The Atlas engagement bundles a monthly editorial cadence — Cameron's voice, signed off by the owner, written by our content team — that compounds the pSEO win with topical authority.
Sympathy etiquette in Ontario
Timing of arrangements, religious and cultural variants, what to bring vs send. Six cornerstone posts.
Wedding florist budgeting in Waterloo Region
Real venue list, real CAD pricing, real consultation outcomes. Eight cornerstone posts.
Anniversary flowers by year
1st – 50th, traditional flower, modern alternative. 25 evergreens, single-author voice.
Same-day flower delivery cutoff guides
City-specific cutoffs, reliability stats, weather contingency. Eleven city-specific posts.
Hospital delivery rules
Tied to the existing hospital directory. ICU restrictions, allergy-aware design, family liaison protocol.
Local flower subscription content
Seasonal, ties to the recurring-revenue product. Five posts per growing season.
Risks and missing inputs we've flagged.
Every Atlas engagement starts honest. The four items below are tracked in the voice-intake stage and resolved before launch.
Owner-supplied photos pending
Real shop interior, owner/family headshots and real wedding/funeral portfolio photos. Stage 2 ships with carefully cropped FSN product imagery; voice-intake stage files a Bridge Quest item for the owner during onboarding.
FSN cart preserved as boundary
Shopping cart and product detail pages remain on FSN. Atlas rebuild deep-links to FSN's secure cart for purchase. The integration is a strength of the proposal — Cameron's keeps the back-office tooling they know.
70-year founding date provenance
Site claims 70 years, no exact founding year. Copy uses 'over 70 years' and 'since the mid-1950s' until owner provides exact founding date during voice-intake.
Review export from FSN
Programmatic export from FSN's review system not promised. Stage 2 includes 12 manually curated reviews; long-term Empire upsell = Cameron's owns the review surface natively.
For Cameron's
This page is the proof of concept. The real engagement scales it 60×.
The fifteen routes you can click on this rebuild prove the design system, the schema, the templates and the voice. Sign the engagement and we will scale to the full ~700-page surface, ship the cornerstone content engine, and own Waterloo Region's florist search results within two indexing cycles.