08 SEO TECHNIQUE · GUGUBRAND PLAYBOOK
Serving EN and ES audiences doubles your addressable search market — if engines can tell your language versions apart and searchers land on the right one. Done lazily, it halves your authority instead.
TECHNIQUE 01
Engines index URLs, not toggle states. Language switchers that swap content under one URL hide your Spanish site entirely from Spanish searchers.
Use /en/ and /es/ path prefixes (or subdomains), with every page having a stable URL in each language it exists in.
TECHNIQUE 02
hreflang tags tell Google which URL serves which language — but they only work as reciprocal pairs. One-directional tags are ignored silently.
On every page, declare hreflang for itself and its counterpart (en, es, and x-default). Audit reciprocity: if /en/about points to /es/nosotros, the reverse must hold.
TECHNIQUE 03
Spanish searchers do not search translated English keywords — they use different phrasings, different units of trust, and often different intents (more WhatsApp, more phone-first).
Run keyword research natively in Spanish for your top services. Write the Spanish pages from that research — never machine-translate the English page and ship it.
TECHNIQUE 04
Spanish-speaking prospects convert on Spanish-language proof: testimonials, case studies, and reviews in Spanish from culturally-relevant customers.
Collect and publish at least three Spanish-language testimonials. Ask happy Spanish-speaking clients to review you on Google in Spanish — those reviews rank for Spanish queries.
TECHNIQUE 05
Your EN and ES sites must clearly belong to one business: same Organization schema entity, same NAP, interlinked language versions. Split signals create two weak entities instead of one strong one.
Use identical Organization JSON-LD (same legalName, same address) on both language trees, and link each page to its counterpart visibly in the UI.
TECHNIQUE 06
AI engines answer Spanish queries with far fewer trustworthy local sources to choose from. Quotable Spanish service pages get cited at rates English pages can only dream of.
Apply the citable-content formats (definitions, steps, FAQs) to your Spanish pages too — ask Spanish questions to ChatGPT and Perplexity monthly and log who gets cited.
No — prioritize money pages: services, locations, contact, and the proof that supports them. A small, excellent Spanish tree beats a complete, machine-translated one.
On one URL, yes — engines struggle to classify the page's language and may rank it for neither. Keep each URL monolingual and let hreflang connect the versions.
We build the brand, encode it as an AI skill, and run the SEO and GEO playbook with AI agents — bilingual EN/ES, measured monthly.
Book a fit call