Migrate from WordPress to Astro in Madrid
Many businesses in Madrid run WordPress but face performance ceilings, security overhead, and rising hosting costs. Astro solves these with static HTML output, zero JavaScript by default, and edge deployment. I migrate existing WordPress sites to Astro with full SEO preservation, URL mapping, and 301 redirects.
- PageSpeed 95-100
Static HTML with zero JavaScript. Faster than any WordPress solution.
- SEO-safe migration
URL mapping, 301 redirects, Google rankings preserved.
- Cloudflare Pages hosting
Global CDN, free SSL, instant deployments. Hosting costs near zero.
Mariusz Szatkowski works from Gdynia, Poland, on Astro builds for organisations whose boards and procurement teams operate from Madrid. Typical clients anchor branding along Paseo de la Castellana, in the Cuatro Torres business cluster, or in innovation campuses such as Distrito Telefónica and La Nave Villaverde. They sell B2B platforms, run regulated finance or infrastructure brands, or host international HQs that must pair Spanish statutory pages with English corridors for investors and EU tenders. A bloated WordPress theme stacked with marketing plugins, or a client-rendered SPA that repaints the viewport before legal footers render, creates avoidable exposure under Spain's Ley 34/2002 on information society services and under AEPD expectations for cookie choice. Astro compiles marketing routes to static HTML, hydrates only widgets that need runtime logic, and keeps LSSI identification fields plus consent gating in version control where Madrid counsel can review diffs.
What Madrid headquarters expect from a corporate public site
Madrid concentrates Spain’s largest listed companies, bank HQs, consulting practices, and scale-ups that still pitch enterprise buyers. Briefs from Chamberí procurement desks or innovation leads at Villaverde hubs repeat the same technical demands even when the sector shifts from insurance on the Castellana to mobility startups near South Summit venues.
When I read scopes for Madrid, these items appear in nearly every RFP matrix:
- Article 10 identification visible on every template, not buried inside a PDF linked once from the blog.
- Article 21 commercial communications rules reflected on newsletter and webinar signup flows in Spanish and, when live, in English.
- Cookie loading order that matches the AEPD cookies guide for electronic communications services before any non-essential tag manager fires.
- Core Web Vitals within the thresholds Google documents on web.dev, because enterprise buyers and journalists open links on LTE during commutes through Atocha or Nuevos Ministerios.
- Bilingual or multilingual trees where Spanish carries statutory tone and English carries investor narrative without duplicate spam URLs.
Graphic design, motion studies, and photography come from your Madrid agency or in-house brand studio. I implement approved layouts and wire the compliance skeleton underneath.

Photo: Dewel, CC BY-SA 4.0, Wikimedia Commons.
Where Astro fits the Castellana corridor and satellite campuses
Paseo de la Castellana is not a single neighbourhood; it is a spine of towers, bank headquarters, and professional services firms from Plaza de Colón north toward the Cuatro Torres. AZCA and nearby financial blocks add law firms and asset managers whose sites must look conservative, load instantly, and survive counsel review after every template change.
Astro matches that posture because marketing pages compile to HTML without shipping a default JavaScript runtime. Islands hold the pieces that genuinely need client logic: mortgage simulators for retail banking microsites, multi-step RFP download gates, job-board filters, or a consent manager. Everything else stays static, which keeps Largest Contentful Paint and Interaction to Next Paint inside the bands Google uses for ranking signals.
Distrito Telefónica and campuses such as La Nave Villaverde produce briefs skewed toward product storytelling and event microsites. Those teams often already run React dashboards for authenticated users. I keep Astro on the anonymous marketing domain and integrate with their existing auth stack through links or embedded islands rather than forcing one framework across both surfaces.
Corporate deliverables I ship for Madrid buyers
- Group and subsidiary sites with Spanish primary URLs and English investor sections.
- Sustainability and governance microsites where counsel edits MDX or CMS entries but footers stay typed.
- Migration off WordPress multilingual stacks that slow mobile Article pages during earnings season.
- Headless setups where editorial remains in WordPress or Storyblok while Astro publishes the edge-cached public layer.
- Performance and schema audits on existing Astro repositories before an AEPD or accessibility review.
I do not fabricate client logos or revenue figures. If you need a local reference, ask in the communities your team already trusts, such as Madrid WordPress practitioner channels named in prior briefs, or request peer contacts in your vertical directly.
LSSI-CE Article 10 and commercial communications on Astro layouts
Ley 34/2002, consolidated as LSSI-CE, treats your domain as an information society service. Article 10 requires service providers to offer permanent, easy, free access to identification data: corporate name, tax identifier, registered office, contact routes, and commercial register references where applicable. Madrid counsel often insists those blocks appear in Spanish even when the visible article is English, because the company redomiciled in Spain remains subject to Spanish disclosure duties.
Article 21 governs commercial communications sent through the site or collected there. A webinar registration form is not “just marketing”; it triggers duties about lawful basis, clarity, and opt-out paths. I map each form variant to a typed partial so legal can approve Spanish and English strings once, and engineers cannot ship a campaign landing without the correct footer and consent linkage.
Because Astro renders footers from data files in Git, procurement teams in Madrid can compare pull requests during sprint review. That beats hunting checkboxes inside a page builder after a rebrand swap colours overnight.
| Surface | LSSI-CE anchor | How I wire it in Astro |
|---|---|---|
| Global footer | Article 10 identification | Typed legalIdentity object injected into every layout |
| Press mailing list | Article 21 commercial comms | Separate partial with unsubscribe copy per locale |
| Careers CRM hand-off | Transparency on data use | Form schema links to privacy policy slug in active language |
| Cookie banner | Article 22 plus AEPD guide | Consent island gates tag manager and pixels |
GDPR privacy policies remain your DPO’s text. My responsibility is technical alignment: no analytics network call before opt-in, minimal fields on lead forms, and consent logs if you enable them.
Ley 11/2023 digital rights where employee routes touch the same brand
Ley 11/2023 on digital rights modernised Spanish rules on disconnection, algorithmic transparency in employment, and related worker protections. A pure corporate homepage about turbines or audit services may never mention those articles. The moment you publish a staff benefits microsite, an internal policy hub, or a whistleblower intake linked from empleo. subdomains, labour lawyers ask whether transparency notices and disconnection policies appear in the language employees actually read.
I document route boundaries in the architecture note: which paths are public marketing, which are staff-only, and which islands call HR APIs. Astro can host both, but firewall rules, robots directives, and template footers differ. Madrid HR teams often want Spanish copy even when the group site markets in English worldwide; I keep locale files explicit so a missing labour notice blocks release.
AEPD-aligned cookie and analytics loading
The Spanish Data Protection Agency publishes a cookies guide aimed at telecom and electronic communications services, which Madrid counsel still cite during audits of corporate domains. Astro’s default export path ships no client JavaScript until you opt in through islands. That makes it practical to mount analytics, A/B tools, and remarketing pixels only after a visitor selects purposes in the banner.
I classify scripts in a spreadsheet you approve before build: strictly necessary, analytics, personalization, advertising. Each class maps to a loader function the consent island calls. If marketing adds a new pixel mid-project, the change is a pull request against that table, not a hidden snippet pasted into a CMS widget.
For groups already using Google Analytics 4 or Matomo, I configure build-time or runtime loading according to your DPO’s preference. The key is provability: Madrid reviewers can open devtools on staging, decline cookies, and confirm zero non-essential requests on first paint.

Photo: Benjamín Núñez González, CC BY-SA 4.0, Wikimedia Commons.
Islands architecture for B2B interactions without SPA weight
Corporate Madrid sites rarely need full single-page-application behaviour on every route. What they do need is selective interactivity:
- Investor relations download gates that verify email domain before PDF release.
- Configurable product selectors for industrial divisions with long SKU lists.
- Office locators with filters for Castellana towers versus regional branches.
- Event registration tied to marketing automation with double opt-in in Spanish.
The Astro islands model keeps those widgets in React, Vue, or Svelte while surrounding copy stays static HTML. Screen readers encounter predictable heading order; SEO crawlers see complete text without waiting for hydration.
When a Madrid subsidiary insists on Next.js for a logged-in dealer portal, I still recommend Astro for the anonymous catalogue that feeds SEO. Hybrid architectures are normal along the Castellana: performance-sensitive public HTML, heavier client bundles only behind authentication.
Content collections for regulated copy
Annual reports, governance statements, and statutory sustainability metrics fit content collections with Zod validation. Each entry carries lang, fiscalYear, and translationGroup fields. Build scripts assert that every Spanish statutory paragraph has an English counterpart when the brief demands parity, or explicitly mark investor-only English pages so hreflang maps stay honest.
MDX allows embedded charts where your design agency supplies data, but numbers in prose still need a named source. I leave placeholders tagged TBD until your IR team supplies figures; I do not invent EBITDA tables to pad length.
Technical stack I use on Madrid Astro engagements
Every repository targets current stable Astro with TypeScript strictness, Tailwind CSS design tokens from your brand PDF, and content collections for long-form pages. Deployment usually lands on Cloudflare Pages with automatic preview URLs per branch so Madrid agencies can review without VPN fuss.
| Layer | Role on Madrid corporate sites |
|---|---|
| Astro 5.x | Static marketing routes, view transitions where brand allows |
| TypeScript | Schema validation on legal and IR content |
| Tailwind CSS 4 | Utility layout matching supplied Figma spacing |
| React or Vue islands | Forms, consent, calculators |
| Cloudflare Pages | EU-friendly edge, custom headers for security policies |
| GitHub Actions | Lint, typecheck, Lighthouse CI on pull requests |
Structured data comes from the same typed content: Organization with legal name and Madrid address, WebSite with inLanguage, FAQPage only where FAQs are visible on the page. I validate JSON-LD on staging with the same tools your SEO agency already uses.
Written delivery from Gdynia without a Madrid desk
I do not maintain a office on Calle de Goya or weekly onsite stand-ups at Torre Emperador. Projects run through written channels your procurement office already prefers: email or ticket thread, shared Git repository, staging links, and checklist acceptance.
| Phase | Madrid-side participants | What you receive |
|---|---|---|
| Intake | Marketing owner, legal counsel, SEO agency | Restated scope, risk log, language map |
| Architecture | IT security, DPO | Route diagram, cookie taxonomy, subdomain plan |
| Build sprints | Brand agency, content authors | Preview URLs, diffs for legal footers |
| Compliance pass | DPO, external labour counsel if staff routes exist | Evidence pack for cookie and ID checks |
| Launch | DNS owner, IR if investor pages move | Redirect file, Search Console checklist |
Central European working hours cover most Madrid business days. Urgent production defects get written acknowledgement the same day when they block a Castellana campaign; feature scope still flows through change notes so procurement retains audit trail.
Pricing stays individual. Market surveys quote wide hourly bands for senior front-end contractors in Madrid; my quotes follow scope after the written audit and name no figure on this page.
Migration from WordPress or Next.js without losing Castellana SEO equity
Many Madrid domains grew on WordPress with page builders that embed Spanish legal shortcodes inconsistently across English clones. Migrations begin with URL and content inventory merged from crawl, CMS export, analytics landing reports, and Search Console. Each URL gets a disposition: keep slug, redirect with single-hop 301, or retire with 410 when no successor exists.
Astro receives typed content, not raw database dumps. Page-builder blocks become components or Markdown with explicit review for tables copied from annual PDFs. I measure Lighthouse on representative templates before and after migration so IR and marketing see numeric proof, not adjectives.
Next.js migrations focus on shedding default client bundles from catalogue routes that never needed application state. Where React Server Components already power authenticated areas, I leave them intact and only move marketing paths to Astro at the edge.
Local visibility for Madrid service queries
Local SEO for a corporate HQ is less about map packs and more about entity clarity: consistent NAP data in footers, LocalBusiness or ProfessionalService schema where appropriate, and location landing pages only when you operate retail outlets beyond the tower lobby.
For AI-assisted discovery, clean semantic HTML and explicit about entities in structured data help parsers cite your sustainability or governance pages accurately. I avoid keyword-stuffed neighbourhood lists; Madrid buyers punish transparent fluff.
Checklist before you sign any Astro contract in Madrid
Use this list internally even if you choose another vendor:
- Confirm Article 10 fields render on Spanish and English templates alike.
- Map Article 21 flows for every form that triggers email campaigns.
- Freeze cookie categories before marketing installs tag containers.
- Decide whether Ley 11/2023 notices apply to staff routes on the same registrable domain.
- Require hreflang reciprocity on built HTML, not only in a plugin admin screen.
- Assign a single legal owner who approves footer diffs in Git or staging.
- Plan vitals measurement on real mobile profiles along commuter corridors.
How to start
Send your Madrid domain, languages, and whether the project is greenfield, migration, or performance recovery. I answer on working days with a written next step and staging access once scope is agreed. EU B2B contracting, individual quote after the audit, no Madrid office and no improvised phone discovery.
Selected projects
Examples of my work.
Real Estate Platform: surfuje.pl
surfuje.pl is a website for surfers and watersports enthusiasts, with clear content, simple publishing, and stable technical operation.
Real Estate Platform: zamki-szkocji.com
zamki-szkocji.com is a comprehensive information portal dedicated to the castles of Scotland, combining rich historical content, interactive maps, photo gall...
Scalac.io - Big Data and Business Scaling Solutions Platform
scalac.io is an international platform founded in 2014 to meet the challenges associated with big data management and business operations scaling, specializing in Scala, distributed systems, and cryptography solutions.
WordPress support & development in Madrid
Need this service: Astro developer in Madrid?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
Migration to Astro, Next.js, and headless WordPress.
WooCommerce sync with ERP and wholesale systems.
Business process automation around WordPress and company systems.
Library of concrete automation use cases.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Astro, MDX, edge delivery, and Core Web Vitals measured on real traffic.
Custom WordPress engineering and architecture.
Scalable headless, ERP, and AI architecture for enterprise.
Related categories
Supporting articles

Six to sixteen weeks for typical engagements, with a four-phase shape: discovery, scoping, build and cutover, tuning. The variables are catalogue size, integration count, URL preservation, and editorial team readiness, not framework choice.

A definitive 4-year Total Cost of Ownership (TCO) analysis, real-world Core Web Vitals benchmarks, Astro 7 GraphQL APQ architecture, and a 10-point executive decision matrix for choosing between decoupled and traditional WordPress.

The Shopify Plus vs WooCommerce headless decision in 2026 is no longer a binary "platform vs custom" trade-off. Both can run headless, both integrate AI, both ship at the edge. The real axes are control, total cost over five years, and exit strategy. This article walks the matrix with confirmed platform facts.