Star's Janitorial: A 270-Page AEO/SEO Site, Built and Shipped
Prospectr Digital designed, wrote, and launched a 270-page answer-engine-optimized website for Star's Janitorial Services (Concord, CA) — a full local-topical map covering every service, segment, and service-area page a Bay Area janitorial company needs to be the extractable answer in Google, AI Overviews, and LLM search. The site runs on Astro deployed to AWS Amplify: static-fast, schema-complete, and built to our 12-criteria cutover standard.
Client: Star's Janitorial Services (Briana Hernandez), Concord, CA — starsjanitorialservices.com
Engagement: AEO/SEO website build (part of a broader program on which Star's doubled annual revenue — full growth story →)
Build: 270 pages · Astro · AWS Amplify · full schema graph · timeline: [NEEDS-DATA: kickoff-to-live dates from repo history]
The problem
Star's competes in the East Bay against national franchises with decade-old domains. Winning classic SEO head terms from a standing start would take years. But the search landscape split: facility managers now get answers from Google's AI layer and chat assistants, where the winner isn't the oldest domain — it's the most extractable, most entity-consistent source. That's a race a challenger can win.
What we built
- A complete local topical map, not a brochure site: service pages, industry-segment pages (medical, office, industrial, retail…), and city/service-area pages for the real route radius — every page answer-first, FAQ-structured, and individually justified. 270 pages, zero doorway templates.
- Machine-readable identity: sitewide JSON-LD
@graph— Organization/LocalBusiness with stable@ids, Service and FAQPage markup per page, real-reviews-only markup, breadcrumbs. - AI-crawler-ready infrastructure: robots allowlist for the crawlers that feed AI answers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended), clean sitemaps, canonicals, 1:1 redirect mapping.
- Static-fast stack: Astro → AWS Amplify. No plugin bloat, no WordPress attack surface, Lighthouse-clean.
- Launch discipline: shipped through our 12-criteria Site Cutover Readiness standard — copy integrity, NAP/entity identity, schema graph, link integrity, redirect equity maps, analytics baseline — before DNS ever moved.
Why the speed matters
A 270-page build is a quarter-long project at most agencies. Our production system (structured page manifests, class-level templates, automated quality gates, human review sampling) compresses that to [NEEDS-DATA: actual build duration] without producing template sludge — every page passes a uniqueness gate before it ships. Speed isn't the vanity metric; time-to-indexed is. Every week a page isn't live is a week it isn't earning citations.
Results
- [NEEDS-DATA: GSC — indexed pages, impressions/clicks curve since launch]
- [NEEDS-DATA: local rankings for top service+city terms]
- [NEEDS-DATA: AI-surface checks — AI Overview citations, ChatGPT/Perplexity mentions for “janitorial Concord CA”-class queries]
- Program-level: Star's doubled annual revenue across the engagement (client testimonial)
What this means if you run a cleaning company
The franchise down the street has domain age. You can have coverage, structure, and entity clarity — the things answer engines actually reward — live in weeks. Get your site's AEO Report Card and see the exact grade gap.
Two paths. Pick yours.
Start with a Lead Gen strategy call, or explore Sovereign and deploy an AI teammate in your AWS in two days. Both start with a 20-minute call.