Common questions.

Typically 6 to 12 weeks for initial movement on accessible keywords. Competitive terms take longer. We track rankings weekly so you can see progress rather than waiting for a quarterly summary.

Yes. All our work is oriented toward Spanish search behaviour on Google.es. We understand that Spanish buyers search differently from English-language markets and we treat it as a distinct discipline, not translated English SEO.

Yes. All prices are in euros and are fixed upfront. No retainer lock-in, no automatic billing, no scope creep invoices. You buy a defined project and we deliver it.

Yes. Content intelligence projects include strategy for both es-ES and where relevant es-LA targeting. We produce Spanish-language content with native writers.

Editorial outreach to Spanish journalists and editors at real publications. We pitch stories and data and earn placements from Spanish media. No paid links, no directories, no private networks.

Manual action penalties are recoverable in most cases. Algorithmic penalties depend on their cause. We give an honest assessment after an initial audit before recommending a recovery project.

Yes. A significant portion of our clients are non-Spanish businesses targeting the Spanish market. Hreflang configuration, Spanish-intent keyword strategy, and bilingual content are all part of our normal workflow.

You own all the work. If you want further work, we scope a new project. No automatic continuation, no long-term contract. Some clients return quarterly for a new sprint; others handle ongoing execution themselves.

The smallest standard project is the Local Dominance package at €189.70. For custom configurations, we consider projects from €150.00. We do not take on one-off tasks without a defined scope.

Yes. Both are frequently used in the Spanish e-commerce market and we have worked on many projects on each platform. We also work with Prestashop, which is common in Spain.

Yes. Hreflang implementation for es-ES versus es-LA versus es-MX is a specific competency we have developed over multiple projects. It is easy to get wrong and we have corrected many implementations where it was causing traffic loss.