Star's Janitorial: A 160-Page Bilingual AEO/SEO Site, Built and Shipped
Prospectr Digital designed, wrote, and launched a 160-page answer-engine-optimized website for Star's Janitorial Services (Concord, CA) — a fully bilingual 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: 160 pages (80 English + full 80-page Spanish mirror) · Astro · AWS Amplify · full schema graph · first commit 2026-07-03, live in production and actively shipping as of 2026-08-18
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. 160 pages, zero doorway templates.
- Fully bilingual, not a translate widget: every one of the 80 English pages has a hand-built Spanish counterpart at
/es/withhreflangpairing andinLanguage:esschema — real indexable pages in both languages, which matters in a market where a large share of facility and janitorial decision-makers search in Spanish. - 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 160-page bilingual build is a quarter-long project at most agencies. Our production system (structured page manifests, class-level templates, automated quality gates, human review sampling) took this one from first commit to live production in under six weeks — 2026-07-03 to launch — without producing template sludge, because 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.
What shipped
- 160 pages live in production on Astro/Amplify — 80 English plus a complete 80-page Spanish mirror, every one present in the submitted sitemap.
- Full schema graph: Organization/LocalBusiness with stable
@ids, Service and FAQPage markup per page, breadcrumbs, real-reviews-only markup. - AI-crawler allowlist and clean sitemaps — GPTBot, ClaudeBot, PerplexityBot and Google-Extended are explicitly permitted to crawl and cite the content.
- Bilingual by construction, not by widget:
hreflangpairing andinLanguage:esschema across the full Spanish set, so both languages are independently indexable. - Program-level: Star's doubled annual revenue across the broader engagement (client testimonial).
Search performance data will be published once the site has a full post-launch measurement window.
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.