Website & application migration in Valencia
I migrate sites from WordPress, Joomla, Drupal, Angular, Vue and other technologies to Astro and Next.js. I plan each migration to keep SEO, content and features intact and switch over in an agreed window. I work alone and have years of experience with both legacy and modern stacks.
Specific context: Tourism booking platforms, agricultural sector digitization, and bilingual Spanish and Valencian content delivery.
- I have had a wordpress.org account since 2006.
- I contributed to WordPress core for versions 7.0 and 7.1.
- I maintain 30 plugins on wordpress.org.
- I organise and speak at WordCamps.
- I have attended every WordCamp Europe from 2017 to 2026.
Migration to Next.js & Astro in Valencia
I migrate sites from monolithic WordPress, Joomla, Drupal and other CMSs to modern Headless architecture powered by Astro or Next.js. In Valencia I execute zero-downtime migrations, your site stays live throughout the entire process.
I migrate applications from Angular, Vue, legacy React, jQuery, PHP and static generators (Hugo, Jekyll, Gatsby) to Astro or Next.js. You gain better performance, SEO and easier long-term development.
A migration to Astro or Next.js in Valencia reaches PageSpeed 95-100 and a sharply lower TTFB, because pages are served from the edge rather than assembled per request. A static front-end eliminates common attack vectors and drastically lowers hosting costs.
Every migration includes full URL mapping, 301 redirects, meta tag and structured data transfer. Your Google rankings don't just hold, they typically improve thanks to better Core Web Vitals.
Valencia is the capital of the Valencian Community and the third most populous city in Spain, with 841,558 residents in 2025, and its websites work in two official languages, Spanish and Valencian. A migration from WordPress, Joomla, Drupal or an old framework to Astro or Next.js has to carry both languages, every indexed URL and a consent banner that matches Spanish guidance, without a dip in enquiries while the switch happens. This page sets out how I do that and how you can check each step yourself.
When is moving off WordPress or Joomla worth it for a Valencia business?
It is worth it when the CMS itself is the bottleneck: a slow server response that caching cannot fix, an admin that breaks after every plugin update, or an editorial team that waits for a developer to publish a page. If the problem is three heavy plugins and no page cache, a cleanup costs less and I will tell you so in the scope.
Astro suits content sites: service pages, blogs, catalogues, tourism and hospitality sites where most pages are the same for every visitor. It ships HTML with almost no JavaScript by default. Next.js suits sites with logins, account areas, personalised prices or heavy client-side interaction. Many Valencia sites are a mix, so the decision is per section, not per company.
What does the migration involve, step by step?
1. Crawl and inventory. I crawl the live site and export the URL list from the CMS, the XML sitemaps and Search Console. The three lists never match: the gaps are orphaned pages, old campaign landings and duplicate language versions. Each URL gets a decision: keep, merge or retire.
2. URL map and 301s. Every URL that keeps a reason to exist gets a one-to-one permanent redirect to its new address. Google recommends 301 or 308 redirects, mapping each old URL to its matching new one rather than to the homepage, and keeping them for at least a year. The map lives in a spreadsheet you can read, and the same file generates the redirect rules, so nothing is typed twice.
3. Content model. Pages, posts, custom post types, categories and custom fields become typed content collections in Astro or a schema in a headless CMS for Next.js. Shortcodes and page builder blocks are the slow part: each one becomes a component or plain Markdown, and I list the ones that need a decision from you.
4. Structured data. Organization, LocalBusiness, Article, Product and FAQ markup is rebuilt from the content model, not pasted from the old plugin output. I validate the rendered JSON-LD on the staging build, page type by page type.
5. Staging and parity checks. Before cutover I compare old and new pages on title, meta description, canonical, H1, hreflang, indexability and main body text.
6. Staged cutover. The new frontend takes over one section at a time while edge rules route the rest to the old system. Small sites switch in one go.
7. Search Console after launch. I submit the new sitemap, watch the Pages report for redirect errors and soft 404s, and inspect a sample of old URLs to confirm Google sees the 301. If the domain changes, Search Console’s Change of Address tool comes into play; for path changes on the same domain it is not needed.
How do Spanish and Valencian versions survive the move?
Bilingual sites in Valencia break in a predictable place: the hreflang annotations. WPML or Polylang generate them inside WordPress, and when the CMS goes, they go with it. On the new site I generate them from the content model, so each page knows its sibling in the other language.
Google’s rules are strict. The value starts with an ISO 639-1 language code, optionally followed by a region code, and every language version must link to all the others, including itself. Without return links Google may ignore the annotations. Valencian has no separate ISO 639-1 code, so the code a site uses for it is a decision I document in the scope and keep consistent across hreflang, the lang attribute and the sitemap. An x-default points users whose language matches neither version to a sensible fallback.
I check hreflang on the built HTML of every page pair, because a missing return link is invisible in the editor and obvious in the output.
What changes for cookies and personal data?
The cookie banner is almost always a WordPress plugin, so it does not survive a migration. I rebuild consent as part of the frontend. Spain’s data protection authority, the AEPD (Agencia Española de Protección de Datos), publishes a cookie guide, updated in May 2024, which interprets article 22 of Ley 34/2002 (LSSI). It asks for a reject button alongside the accept button, a settings panel that lets users accept or reject by purpose, and no design that pushes users toward accepting, such as a reject button whose text does not contrast with its colour.
In practice that means analytics and advertising scripts load only after consent, and I test it on staging with an empty browser profile: no third-party request should leave the page before a choice is made. Forms are rebuilt too, so I list where each submission goes and which processors handle it, since contact form plugins often send data to services nobody remembers adding.
Where should the new site be hosted?
Astro builds to static files that can be served from a CDN, with a small serverless layer for forms. Next.js needs a Node runtime or a platform that supports it. If you need your data processed in the EU, I pick providers and regions that allow it and write the choice into the handover document, including which parts of the site run where.
What can go wrong, and how do I check it?
- Redirect chains. Old redirects from earlier relaunches point to URLs that now redirect again. I flatten chains so each old URL reaches its final address in one hop.
- Lost pages. A page that had traffic but no menu link gets forgotten. The crawl plus the Search Console export catches it.
- Language mix-ups. A Valencian page redirected to the Spanish version loses its audience. The URL map has a language column, and I check it per row.
- Tracking gaps. Analytics that fired from the old theme stops silently. I compare events on staging before cutover.
What stays with you after launch?
The repository, the redirect map, environment variables, the deploy pipeline and a short document on how to publish, add a page in both languages and roll back a release.
For the method in full, see my Next.js and Astro migration service and, for new builds, Astro development.
How do I get a scope for my site?
Send me three things: the current URL, the CMS and version it runs on, and where your traffic comes from (organic search, ads, referrals, newsletters). I reply with a written scope covering the URL count, the language versions, what migrates as-is and what needs a decision, and the order of the cutover.
WordPress community signals in Valencia
The community reference is WordPress Valencia (https://www.meetup.com/wordpress-valencia/). It does not replace a contract; it sets the technical vocabulary teams use in Valencia.
We build secure, high-performance WordPress solutions for businesses in Valencia, tailored to local market realities. In the Tourism & Agriculture Tech segment, questions usually turn on WordPress, WooCommerce, Astro, Next.js versus legacy.
Scope and assumptions arrive in writing after a short brief. Tourism booking platforms, agricultural sector digitization, and bilingual Spanish and Valencian content delivery.
Map of Valencia and surrounding area
Selected projects
Examples of my work.
Website Delivery: Sole Practitioner Law Firm
Technical implementation for a sole practitioner law firm in Wroclaw: WordPress migration, SSL certificate, mail server configuration, and pre-launch QA.
WooCommerce wholesale API integration: an automotive parts store
Case study of integrating a WooCommerce store with an automotive wholesaler's REST API: catalog, stock and price synchronisation in real time plus automatic margin logic.
WPPoland - rebuilding a proof-led WordPress, Astro and technical SEO site
A method-led case study of the WPPoland rebuild: Astro, Markdown/MDX content, six locales, technical SEO, structured data, AEO/GEO and content quality gates.
WordPress support & development in Valencia
Methodology guides (SEO, GEO, compliance)
How I approach AI citations, WooCommerce B2B modernization, and NIS2-aligned operational resilience on WordPress. These guides apply to every client location.
What makes Valencia unique
Local expertise:
- Migration to Astro & Next.js in Valencia, Spain
- From WordPress, Joomla, Drupal and legacy frameworks
- Staged migrations with redirect mapping and SEO checks
I work remotely for businesses in Valencia.
Need this service: Next.js / Astro migration in Valencia?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectFAQ - Next.js / Astro migration Valencia
Can my Spanish and Valencian pages keep their rankings after the move?
They can, if each language version keeps a 301 from its old URL and the new pages carry reciprocal hreflang annotations. Google ignores hreflang when the return links are missing, so I check every pair in the built HTML before launch, not in the CMS settings.
Do I need the Change of Address tool in Search Console?
Only if the domain changes, for example from a .com to a .es. Google says the tool is not needed for path changes on the same domain, which is what most CMS to Astro migrations are. The 301 map does the work in both cases.
Do you migrate everything at once or incrementally?
Incremental by default. The new frontend takes over one section at a time while the rest keeps running on the old system, with edge rules splitting the traffic until the last section moves. A big-bang cutover only makes sense on small sites, where running two stacks in parallel costs more than one clean switch.
What happens to the cookie banner?
It is rebuilt, not copied. Most old banners are CMS plugins that do not exist on Astro or Next.js. The new one follows the AEPD cookie guide: a reject button next to the accept button, a settings panel by purpose, and no analytics script before consent.
Explore 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.