Next.js / Astro migration in Lisbon

Migration to Astro or Next.js for Lisbon companies: URL map and 301s, pt-PT and English hreflang, GDPR data flows under the CNPD, staged cutover and Search Console checks.

Next.js / Astro migration

Website & application migration in Lisbon

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.

  • 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.
  • Local WordPress meetup: WordPress Lisboa

My WordPress.org profile

Lisbon is the capital and most populous city of Portugal, with about 658,000 residents inside the municipality and roughly 3.35 million in the Lisbon metropolitan area. A company selling from Lisbon usually runs a website in European Portuguese (pt-PT) and English (en) at least, and often adds Spanish (es), French (fr) or a separate Brazilian Portuguese (pt-BR) edition. That multilingual setup is where CMS migrations break most often. Working solo, remotely and in writing from Gdynia, I move Lisbon business websites from WordPress, Joomla, Drupal or an ageing custom framework to Astro or Next.js, ensuring that the URL map, the language pairs, and the post-launch verification protect the search traffic your domain has earned.

#How do I migrate a Lisbon WordPress site to Astro without losing rankings?

Google’s own site move guidance is explicit: map every old URL to its new address, use server-side permanent redirects (HTTP 301 or 308), and keep those redirects active for as long as possible, generally at least a year. I build the master URL ledger from three distinct sources, because each one misses something when used alone: the XML sitemaps, the raw server access logs, and a direct database export from the legacy CMS. Sitemaps omit pages that an SEO plugin excluded years ago, server logs expose legacy URLs and PDF brochures that still receive referral visits, and the CMS database reveals media attachments, custom post types, and category archives nobody remembers creating.

Every row in that ledger ends in one of three documented states: keep the exact URL path, issue a single-hop 301 redirect to its closest successor URL, or return a deliberate HTTP 410 for obsolete content you decided to retire permanently. Nothing gets a changed address simply because a new framework prefers a different routing convention. On Astro I compile the redirects into the edge host’s routing configuration; on Next.js they live in the edge middleware or routing table.

The underlying content model moves together with the URLs. Legacy posts, pages, custom post types, ACF or Drupal fields, navigation menus, and author profiles are converted into strictly typed collections or clean headless CMS entries so layout shortcodes never leak into the new HTML.

#Should a Lisbon company choose Astro or Next.js?

Astro fits websites that are primarily content and lead generation: corporate service pages, case studies, blogs, technical documentation, real estate or hospitality showcases, and product catalogues that update a few times a day. It compiles static HTML at build time and ships JavaScript only to the specific interactive islands that require it, making it straightforward to stay well within Google’s official Core Web Vitals thresholds (Largest Contentful Paint up to 2.5 s, Interaction to Next Paint up to 200 ms, Cumulative Layout Shift up to 0.1) even on congested mobile networks.

Next.js fits when the platform behaves like an interactive software application: authenticated client portals, per-user B2B pricing tiers, server-side rendering on every request, or custom booking and checkout workflows tied to live APIs. If the honest assessment of your site is “multilingual corporate content with enquiry forms and a resource library”, I recommend Astro and explain why in the written scope. If your editorial team wants to keep WordPress purely as the back-office authoring interface while Astro or Next.js renders the public pages, that decoupled architecture is covered in detail on my headless CMS developer page.

#Lisbon’s commercial and technology sectors: where headless migration pays off

Across business districts such as Parque das Nações, Avenida da Liberdade, Saldanha, Alcântara, and innovation hubs like Beato Innovation District (Hub Criativo do Beato) and Taguspark in Oeiras, Lisbon companies face specific architectural bottlenecks on legacy CMS stacks:

  • SaaS Scaleups, Fintech and Nearshore Engineering Centres (Parque das Nações, Beato, Taguspark): Technology companies operating out of Lisbon sell to enterprise buyers across the UK, Germany, the US, and Iberia. Their websites combine English product documentation and security whitepapers with local Portuguese employer-branding and career pages. Migrating from a plugin-heavy WordPress install to Astro lets engineering teams manage documentation in version-controlled MDX while marketing teams publish campaign pages without risking site-wide downtime.
  • Hospitality, Real Estate and Tourism Platforms: Hotels, serviced-apartment operators, and property investment firms in Greater Lisbon rely heavily on high-resolution galleries, multilingual landing pages (pt-PT, en, fr, de, es), and booking engine integrations. Replacing a sluggish monolithic theme with pre-rendered Astro pages and AVIF image pipelines removes render-blocking scripts and keeps mobile visitors from bouncing before the booking widget loads.
  • Professional Services, Legal, Consulting and Export B2B (Avenida da Liberdade, Saldanha): Law firms, financial advisories, and industrial exporters publish regulatory briefings, PDF reports, and bilingual service directories that accumulate valuable backlinks over years. A strict 1:1 URL map and typed schema generation protect those deep rankings during a visual and technical modernisation.

#How do I keep European Portuguese (pt-PT) and English versions correctly paired?

Hreflang annotations are the single most common point of failure when bilingual Lisbon websites are rebuilt. Google supports ISO 639-1 language codes combined with optional ISO 3166-1 Alpha 2 region codes, which allows pages written for Portugal to be marked pt-PT and kept distinct from Brazilian Portuguese (pt-BR) if your business serves both Lusophone markets alongside English (en). Every language edition must list itself and every sibling translation, and if two pages fail to link back to each other reciprocally, Google ignores the annotations entirely. An x-default tag marks the fallback route for international visitors whose browser language matches none of your published locales.

In legacy WordPress or Drupal sites, multilingual plugins (such as WPML, Polylang, or Drupal’s translation modules) often store translation links in separate database tables that accumulate gaps over time. Before building the new frontend, I export all existing language pairs, flag every orphaned page that lacks a counterpart, and let you decide in writing whether a translation should be added or whether that route remains single-language. In the new Astro or Next.js build, hreflang tags and canonical URLs are generated directly from a shared translation key in the content schema, turning any missing return link into an immediate build-time warning rather than a silent ranking drop in Google Search Console.

Replacing a legacy CMS changes how your website processes personal data, sets cookies, and presents statutory company information under Portuguese and European Union law:

Personal data and CNPD oversight (Lei n.º 58/2019 & GDPR). In Portugal, the GDPR is supplemented by Law no. 58/2019 of 8 August (Lei da Proteção de Dados Pessoais) and supervised by the Comissão Nacional de Proteção de Dados (CNPD). Moving from a monolithic WordPress server to a decoupled Astro or Next.js stack changes where personal data flows, even when a contact form looks identical on screen: instead of posting to a local PHP script and MySQL table, the form may submit to a serverless function, an email relay, or a CRM API. I document every form endpoint, newsletter integration, analytics script, and third-party widget, recording what data it collects, who processes it, and in which geographical region, so your privacy policy (Política de Privacidade) and records of processing activities remain accurate.

That inventory is also essential for incident response. As the CNPD emphasizes in its data breach guidance under Article 33(1) of the GDPR, a personal data breach must be notified to the CNPD within 72 hours of becoming aware of it via its online portal, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. Knowing every processor and endpoint in advance makes that assessment straightforward.

Cookies and electronic communications (Lei n.º 41/2004). Under Law no. 41/2004 of 18 August (as amended, transposing the ePrivacy Directive), storing information or gaining access to information stored on a user’s terminal equipment requires prior informed consent, with an exemption only for technical storage strictly necessary to provide a service explicitly requested by the user. In the rebuilt frontend, analytics and marketing trackers are wired so that zero non-essential cookies or scripts execute before the visitor actively opts in.

Accessibility (Decreto-Lei n.º 83/2018 & Decreto-Lei n.º 82/2022). Portugal’s Decree-Law no. 83/2018 sets digital accessibility requirements based on EN 301 549 / WCAG 2.1 AA, monitored with technical guidance and tools from AMA (Agência para a Modernização Administrativa, accessibility.gov.pt), while Decree-Law no. 82/2022 transposes the European Accessibility Act for covered e-commerce and consumer services from 28 June 2025. Building clean Astro or Next.js templates from scratch lets me implement semantic landmarks, keyboard navigation, form labels, and contrast ratios properly from the start.

Commercial disclosures and distance contracts (Código das Sociedades Comerciais & DL n.º 24/2014). Under Article 171 of the Portuguese Commercial Companies Code (Código das Sociedades Comerciais), websites of commercial companies (such as a sociedade por quotas, Lda., or sociedade anónima, S.A.) must clearly display the company’s registered name, legal form, registered office (sede), registration office (Conservatória do Registo Comercial), corporate identification number (NIPC / NIF), and share capital (capital social). Where the site sells goods or services online to consumers in Portugal, Decree-Law no. 24/2014 (distance and off-premises contracts, supervised by DGC and ASAE) and the electronic complaints book integration (Livro de Reclamações Eletrónico, livroreclamacoes.pt, where applicable) must also remain linked and functional across the new footer templates.

#Pre-cutover verification checklist for Lisbon migrations

Verification areaWhat I check before switching production DNS
URL & PDF redirect mapEvery URL from XML sitemaps, Search Console and server logs returns HTTP 200 or a single-hop 301
Lusophone & international hreflangReciprocal pt-PT, en (and pt-BR / es if used) tags and self-referencing canonicals verified in HTML
CNPD & ePrivacy complianceZero analytics or marketing cookies set prior to consent; processor list documented per form endpoint
WCAG 2.1 AA & DL 82/2022Keyboard focus order, semantic headings, form labels and colour contrast verified across templates
Schema.org JSON-LD parityOrganization, BreadcrumbList, Article, Product and FAQPage schemas validated against legacy pages
Article 171 CSC & footer linksNIPC/NIF, Conservatória, share capital and Livro de Reclamações links preserved across all locales

#How does the cutover run, and what can go wrong?

  1. Inventory: URL map, existing server redirect rules, structured data types in use, forms, CRM integrations, and top landing pages from Search Console.
  2. Staging build: deployed on a preview URL blocked from indexing, with the full redirect table tested against it automatically.
  3. Parity check: titles, meta descriptions, canonicals, hreflang pairs, JSON-LD and internal links compared between old and new for every URL in the map.
  4. Launch: DNS or edge proxy switch, 301 redirects live at the edge, and updated sitemaps submitted.
  5. Post-launch watch: I inspect Search Console page indexing and sitemap reports, crawl stats, and 404 server logs during the initial weeks so any unexpected crawler hit is fixed immediately.

Common migration traps I specifically check for include multi-hop redirect chains accumulated from earlier redesigns, trailing-slash mismatches between canonical tags and served URLs, changed image paths that break Google Images traffic, vanished pagination or category archives, and JSON-LD blocks that lost a required property during template conversion.

#What stays with your company after the migration?

Your organization owns the Git repository, the human-readable redirect map and edge configuration file, the automated build and deployment pipeline, documented environment variables, and a concise written guide showing editors how to publish and update pages. Any developer familiar with TypeScript, Astro, or Next.js can maintain the codebase without lock-in. More about the engineering workflow is on the Next.js and Astro migration page.

#What should you send for a written scope?

Send me your current site URL, the CMS and version it runs on, the languages it serves (pt-PT, en or others), and where your traffic comes from (organic search, paid ads, referrals, newsletters) via the contact page. Read-only access to Google Search Console helps most, because it shows which URLs actually earn impressions and clicks. I reply in writing on working days with a free initial estimate and written scope covering what moves, what gets retired, which framework fits best, and how the cutover is staged.

See also in Portugal

Need this service: Next.js / Astro migration in Lisbon?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Explore other WordPress services and knowledge base