A Google-dominant market split between Castilian Spanish and genuinely distinct regional languages that a national template cannot fake.
We build programmatic SEO surfaces for Spanish companies — Idealista and Fotocasa-aware in real estate, region-accurate across Spain's autonomous communities, and held to the same performance and quality gates we run on our own properties.
Programmatic SEO is not a content order. It is a data model, a template system, a performance budget and a maintenance routine that has to keep working after launch. We own all four.
Idealista owns the head terms in Spanish property search, with Fotocasa a strong second. We map where their templates thin out — barrio-level detail, comunidad de propietarios specifics, energy-certificate explainers — and build the layer they under-serve.
Spain is not one market: Catalonia, the Basque Country and Galicia carry real co-official languages and distinct search behaviour. Where it matters commercially, templates ship in Catalan, Basque or Galician alongside Castilian, not as a machine-translated afterthought.
Every template enforces a minimum threshold of genuinely local substance before a page is allowed to publish — a direct defence against the scaled-content abuse policy that has hit Spanish affiliate and directory sites hard since 2023.
Consent flows, cookie policy and data-retention logic built into the template layer, matching Spain's own data protection law (LOPDGDD) on top of the EU baseline.
Performance budget set against mid-range Android on 4G, reflecting how the majority of Spanish search traffic actually arrives. The build fails past LCP 2.5s / INP 200ms.
Coverage reports, cannibalisation checks across regional and national URL sets, pruning of the bottom decile and consolidation of near-duplicate barrio or municipio pages.
Each vertical has its own page types, its own data source and its own failure mode. Pick yours to see what we'd actually ship.

Property is the most unforgiving programmatic category there is: inventory changes weekly, every portal already owns the head terms, and a stale page is a wrong page. We build the neighbourhood, building and agent layers portals under-serve, wire them to your live listing feed, and keep the 404/410 discipline that stops decayed inventory from rotting your index.
Reference implementations, not clients or partners. Listed because their public page architecture is worth studying.
Different buyers, different matrices, different risks. The engine is the same; the model is not.
Idealista y Fotocasa poseen las búsquedas genéricas. La oportunidad real está en el barrio, la comunidad de propietarios y el certificado energético, datos que estos portales generan de forma genérica al no tener información propia por edificio.
Real operators, described by what they actually publish. We build the same structural discipline into surfaces a fraction of their size.
La superficie pública de Idealista apila páginas de anuncio, edificio, barrio y municipio, generadas desde los feeds de agencias. Es la referencia estructural con la que se compara cualquier reto en el mercado español.
No batch of pages goes live before the batch before it has been measured. That sequencing is the reason these surfaces survive core updates.
We document which page types Idealista, Fotocasa, Milanuncios and category leaders rank with, and where a challenger can realistically compete.
Clean URL structure matching Spain's administrative geography — comunidad autónoma, provincia, municipio, barrio.
A small batch ships first and is measured before scale. If it does not earn impressions in four to six weeks, we change the template, not the volume.
Controlled publishing waves with the uniqueness gate, performance budget and schema validation on every page.
Comunidad → provincia → municipio hub structure so authority reaches deep pages instead of pooling at the top.
Monthly review of what ranks, what stalls and what gets cited by AI assistants; the dead tail gets consolidated or removed.
Your data, your WordPress, your domain. We bring the engine, the gates and the discipline.
Sin reintroducción manual, sin cementerio de CSV.
Google Sheets, Airtable, tu API de producto, tus feeds de anuncios, o un simple CSV. Cada fila se convierte en página, cada actualización en revisión, cada baja en un 410 real.
Figures we work from, with the source stated. Where a number is directional, we say so.
Spain looks like a single Spanish-language market from outside and is nothing of the sort once you're building at scale. Catalonia, the Basque Country and Galicia have real regional-language search demand — not large in absolute volume compared to Castilian, but high-intent and poorly served by national competitors, which makes it a genuine opening for a programmatic build that gets the localisation right.
Second, Spanish buyers are price-sensitive and comparison-heavy searchers; 'comparador' and 'opiniones' page types consistently outperform generic category pages, and Google.es's local packs are unusually decisive for services because Spanish consumers check reviews before almost any other market signal.
Third, hosting latency to Spain from generic EU infrastructure is fine, but LCP budgets need testing against Spanish mobile networks specifically — 4G coverage outside Madrid and Barcelona is patchier than northern Europe, and a template that's fast in Frankfurt tests can still miss budget in rural Andalusia.
Scaled pages don't get demoted for being scaled. They get demoted for being interchangeable, slow, or wrong about the place they claim to serve.
Catalonia and the Basque Country have real regional-language demand for local services; a Castilian-only template cedes that segment to smaller, better-localised competitors.
Spanish commercial intent skews heavily toward 'mejor X' and 'opiniones' formats; a plain feature-list page under-converts against a competitor running a genuine comparison table.
Templates tested only against Madrid/Barcelona connectivity miss LCP budget in less-connected regions where a meaningful share of mobile searches originate.
Spanish consumers expect IVA-inclusive pricing displayed clearly; ambiguous pricing is a trust failure that shows up as bounce rate before it shows up as a ranking problem.
Templates treating Spain as 50 provinces with no autonomous-community tier miss how Spanish users actually search (by comunidad autónoma for many service categories).
Same order every time. The uniqueness gate and the performance budget come before a single page publishes.
Build Catalan or Euskera pages only where genuine demand and a competent native reviewer both exist — a thin regional set is worse than none.
'Mejor', 'comparativa' and 'opiniones' templates for commercial categories, backed by real comparison data.
Budget verified on mid-range Android over regional 4G, not just Madrid fibre.
Consumer pages default to tax-inclusive pricing with the rate stated, matching Spanish consumer expectation.
Country → autonomous community → province → city, matching how services and property are actually searched.
Search Console filtered to Spain, with regional-language segments tracked separately from Castilian.
Not partners — reference implementations. External links are nofollow.
Iberian property portal.
The reference model for province and neighbourhood-level property pages built from a live listing feed across Spain and Portugal.
idealista.comProperty portal.
A strong secondary property incumbent — useful for gap analysis against Idealista's weaker categories.
fotocasa.esSpain's largest job board.
Category × province × role programmatic structure worth studying for any Spanish jobs or HR-adjacent build.
infojobs.netFinancial comparison site.
The comparator format done at scale for Spanish fintech — sourced, dated tables rather than static copy.
kelisto.esBacklink and keyword research suite.
Regional-language (Catalan/Basque/Galician) volume data is thin — treat it as directional and validate with Search Console.
ahrefs.comEdge network and caching.
Madrid PoP keeps latency reasonable for national Spanish traffic without moving origin infrastructure.
cloudflare.com| Option | Best for | Trade-off |
|---|---|---|
| SMEs and agencies needing editorial control across Castilian and regional-language sets. | Needs disciplined hreflang setup to avoid ES/CA cannibalisation. | |
| Spanish and Latin-market-facing ecommerce. | Facet SEO needs manual configuration. | |
| Marketing sites under ~10k pages. | Multi-language collections get unwieldy past a few thousand pages. | |
| Product-led SaaS with live data. | Requires in-house engineering to maintain regional-language variants. |
Each city has its own angle, its own blockers and its own first moves — because they genuinely differ.
Finance, government and the densest B2B SERP in Spain.
Tech, tourism and the one Spanish city where a genuine Catalan-language surface pays off.
Growing tech and logistics hub with a materially softer SERP than Madrid or Barcelona.
Tourism, heritage and a regional Andalusian buyer base that responds badly to generic national copy.
Industrial and financial hub with genuine Basque-language (Euskera) local demand.
Only where you have genuine Catalonia-based demand and a native reviewer — a thin machine-translated Catalan set reads worse than not having one.
Very, for commercial categories — 'mejor' and 'opiniones' query patterns are a large share of intent here.
Yes for local and regional intent — always build and test against Google.es specifically, not a generic Spanish-language Google result.
Yes, by default, for consumer pages — Spanish buyers expect tax-inclusive pricing shown clearly.
Usually 100–300, similar to other mature EU markets — small enough to reverse, large enough to read a signal.
We'll audit the data source, size the first batch, set the performance budget and tell you honestly if programmatic is the wrong tool for your category.