The 22 Spanish Q&As that unlocked the Hispanic LA market
By AskBaily Editorial · Published · 4 min read · Wave 219
Summary
Wave 219 shipped the /es/ Spanish mirror with 22 translated-and-re-authored Q&As, /es/compromisos, /es/puntaje-citaciones-ai-overview, /es/herramientas, and a dynamic [slug] route for Spanish pages. Los Angeles County is 48.6 percent Hispanic; a Spanish surface is not optional. The translation choices matter more than the count.
Article body
Los Angeles County is, by the 2020 Census, 48.6 percent Hispanic or Latino. Hispanic homeowners make up a substantial share of every remodel market we serve, and until Wave 219, AskBaily served them in English only. Shipping the /es/ mirror was the correction. This post is about what "mirror" actually means in practice and why the translation choices compound AEO rather than dilute it.
The scope of the mirror
Wave 219 shipped 22 translated-and-re-authored Q&As under /es/ask/, plus /es/compromisos (the Spanish /commitments), /es/puntaje-citaciones-ai-overview (the Spanish /ai-overview-scorecard), /es/herramientas (the Spanish /tools hub), and a dynamic [slug] route that resolves Spanish pages. The total is 22 Q&A URLs plus four static surface pages, all backed by a Spanish-specific registry that mirrors the English structure.
The 22 Q&A topics were chosen from two data sources: the subset of English /ask questions with highest Hispanic-homeowner engagement on our /chat transcripts, and the top-ranked Spanish-language remodel-intent queries on Google Trends Los Angeles DMA. The intersection produced 22 questions that Hispanic LA homeowners specifically ask, not just translations of the English hub's top entries.
Why translate-and-re-author instead of machine-translate
Because regulatory vocabulary does not translate cleanly. The English phrase "contractor's license" maps to three different Spanish terms depending on context: "licencia de contratista" is the direct translation, "licencia de CSLB" is the regulator-specific term most Hispanic LA homeowners actually recognize, and "numero de CSLB" is the colloquial form in Spanish-language contractor advertising. A machine translation would pick one and lose the other two. The re-authored Spanish answers use all three in context, with the canonical CSLB term in the accepted-answer span.
Similarly, "permit" in English becomes "permiso" in formal Spanish, "permiso de construccion" in LADBS-specific Spanish, or "permiso de obra" in the colloquial Hispanic construction vocabulary common in LA. The re-authored entries acknowledge the vocabulary range; they do not pick one term and abandon the others.
Finally, the cultural context of remodeling differs. An English answer about hiring a contractor can assume the homeowner has read online reviews, done background research, and treats the hire as a fully transactional decision. A Spanish answer, authored for LA's Hispanic homeowners, often needs to acknowledge family-recommendation networks as a parallel trust signal and explain how regulator verification interacts with that trust signal rather than replacing it. The re-authored entries include this context where it applies.
The schema choices
Every /es/ask/{slug} page emits the same six-node schema graph the English version emits: Organization, LocalBusiness, WebPage, QAPage, BreadcrumbList, SpeakableSpecification. The critical difference is the inLanguage tag, set to "es" instead of "en-US." AI engines use the language tag to route queries to the correct surface; a Spanish-language query for "como verifico la licencia de un contratista en Los Angeles" should resolve to /es/ask, not the English /ask.
The SpeakableSpecification selector on the Spanish pages points to the Spanish accepted-answer paragraph, with [data-speakable-accepted-answer] applied exactly as in English. Voice assistants reading aloud in Spanish lift the Spanish paragraph directly.
Citations in the Spanish entries point to Spanish-language versions of regulator resources where available (the CSLB's Spanish-language pages, LADBS Spanish resources) and to English regulator pages where no Spanish version exists. The citation URLs are logged in the Wave 219 entry at /changelog so future readers can see what choices were made.
Hreflang reciprocity
Each /es/ page declares hreflang reciprocity with its English counterpart. The Spanish /es/ask/como-verifico-la-licencia-de-un-contratista-en-los-angeles page declares hreflang="es" for itself and hreflang="en-US" pointing at /ask/how-to-verify-a-contractors-license-in-los-angeles. The English page declares the reciprocal pair. AI engines and search engines use the reciprocity to treat the pages as one entity across two locales.
The hreflang reciprocity is the reason Wave 162 shipped a dedicated hreflang audit: the tag has to be present on both ends of the pair, or the engine treats them as disconnected pages. Wave 219's 22 Q&As all pass the audit.
Why 22 and not all 100
Because the Spanish mirror is a compounding investment, not a fire-and-forget translation. Shipping all 100 English entries as Spanish would have produced 78 low-priority pages alongside the 22 high-priority ones, and the editorial discipline that made the English hub work would have collapsed under the volume. Wave 219 shipped the 22 that matter most. Future waves will extend the Spanish mirror topic-by-topic, with each extension meeting the same re-authoring bar.
What Angi and Thumbtack cannot copy
They have Spanish surfaces. Angi has a /es/ Spanish site; Thumbtack has Spanish-language customer-facing pages. What they do not have is a re-authored Spanish surface that treats LA Hispanic homeowners as a distinct editorial audience with distinct questions and distinct cultural context. Their Spanish pages are machine-translated from English content, which preserves the underlying marketing-blog thinness of the source.
Our Spanish mirror is Claude-authored in Spanish, not machine-translated from English. Every accepted-answer is written fresh. Every citation list is evaluated for Spanish-language primary-source availability. Every vocabulary choice is deliberate. The result is a Spanish surface that AI engines cite on Spanish-language queries, not a token localization.
The compound
Hispanic LA homeowners are approximately half the market. A Spanish surface that actually serves them compounds across every downstream conversion: /es/chat referrals to our /for-pros flow, /es/tools/contractor-check usage by homeowners verifying their own contractor candidates, and /es/compromisos citations when a homeowner escalates a dispute. The 22 Q&As are the seed; the mirror is the surface that keeps growing.
Sources & references
Commit attestation
- f7ed00e94dea912e5120e8932f31a2c23b53e979
- Waves
- 219
- Author
- editorial
Commit SHAs are from the AskBaily private repository. If you are a journalist, researcher, or regulator and need access to verify, email [email protected].
Frequently asked
- Why not just machine-translate the English entries?
- Because regulatory vocabulary does not translate cleanly and cultural context differs. 'Contractor license' maps to three Spanish terms depending on context; 'permit' to three more. Re-authoring gets the nuance right; machine translation loses it.
- Are the Spanish entries authored by a native speaker?
- Every Spanish entry is reviewed by a native Spanish-speaking editor on the research desk before ship. The editorial standards page documents the review process; the reviewer's attribution is on the /es/ask/{slug} page footer.
- Does the /es/ mirror include the /reviews, /roadmap, and /chat pages?
- Wave 219 shipped /es/compromisos, /es/puntaje-citaciones-ai-overview, /es/herramientas, and the 22 Q&As. /es/resenas (reviews), /es/hoja-de-ruta (roadmap), and /es/chat are staged for subsequent waves; the editorial desk is prioritizing based on inbound /chat language detection.