Migrate from WordPress to Astro in Porto
Many businesses in Porto 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 builds Astro websites from Gdynia for companies in Porto and the towns around it. Most Porto briefs come from three kinds of buyer: manufacturers and traders that export through the Port of Leixões in Matosinhos, young companies hosted at UPTEC, the University of Porto science and technology park, and established firms that need a careers site good enough to hire engineers in Northern Portugal. Each of them needs a public site that renders as static HTML, carries European Portuguese next to English, and keeps Portuguese consent and distance-contract rules in versioned templates that a reviewer can diff.
What Porto briefs ask an Astro developer to build
A Porto brief usually opens with a business problem that the current site makes worse, often a WordPress install from a few years ago that grew a page builder, a translation plugin and a dozen marketing scripts.
The three buyer groups ask for different things:
| Buyer | Typical pages | What the current site gets wrong |
|---|---|---|
| Exporter or logistics firm around Leixões | Product catalogue, certificates, technical datasheets, quote request | Slow catalogue pages on mobile, PDF links instead of indexable pages, one language done well and the others machine translated |
| UPTEC spinout or research company | Product story, team, publications, investor page, documentation | Template site that looks like every other startup, docs locked in PDFs, no structure for search engines to read |
| Employer hiring in Northern Portugal | Careers hub, job pages, engineering blog, benefits | Job pages rendered by a third-party widget that search engines cannot index, slow load on the candidate’s phone |
Astro fits all three because the content is mostly read, rarely interacted with, and changes on an editorial schedule. A product page, a job post and a research summary are documents. Astro compiles documents to HTML at build time and adds JavaScript only where a component needs it.
Your designer owns the visual identity, the Figma frames and the component specs. I turn approved layouts into Astro templates, wire the content model under them and connect the forms to the CRM or inbox you choose.
Leixões and Matosinhos: websites for a port economy
The Port of Leixões sits at the mouth of the river Leça in the municipality of Matosinhos, a few kilometres northwest of central Porto. APDL, the authority that administers it, describes it as the largest artificial port in Portugal. Its own figures for 2023 list 14.7 million tonnes of cargo, 702 thousand TEU, 2,391 ships, more than 456 thousand trucks and 1,826 trains through the port.
According to the APDL port page, two container terminals are operated by Yilport Leixões, with a ro-ro terminal, a multipurpose terminal, a cereal terminal and liquid bulk berths alongside. The Porto Cruise Terminal on the south breakwater, with a quay inaugurated in April 2011, also houses CIIMAR, a University of Porto marine research centre.
That traffic shapes the websites I get asked to rebuild. A cork, textile, footwear or metalworking company that ships through Leixões sells to buyers who never visit Porto. Those buyers meet the company on its website, often through a search for a specific product code or certification, and they decide in the first page view whether to send a request for quotation.
What an exporter catalogue needs
- One indexable page per product line, with the technical table in HTML and the PDF datasheet as a secondary download. Search engines read the table; buyers print the PDF.
- Language versions for the markets you ship to. Porto exporters commonly add Spanish and French next to pt-PT and English. Each version gets its own URL and reciprocal hreflang, generated from the content model.
- Certificates and compliance documents (ISO certificates, material declarations, CE documentation where it applies) kept as structured entries with an expiry date, so an expired certificate drops off the page at the next build.
- A quote request form as a small interactive island that posts to your CRM, with the product code pre-filled from the page the buyer came from.
- Incoterms and lead-time copy written by your sales team once and reused across product pages through a shared component, so a change in shipping policy is one edit.
Logistics and forwarding firms in Matosinhos have a different version of the same problem. Their customers want schedules, service descriptions and contact routes per trade lane. APDL already publishes operational tools for port users, including a live map and links to the port’s logistics platforms on the Leixões site. A forwarder’s own site can leave those systems where they are and concentrate on fast service pages that explain what the firm handles, with deep links to the tracking tools the customer already uses.
UPTEC spinouts and research companies
UPTEC is the science and technology park of the University of Porto, and it has supported projects since 2007. It runs four centres across the city:
| Centre | Address | Focus |
|---|---|---|
| Asprela I | Rua Alfredo Allen, Porto | Technology and sciences |
| Asprela II | Rua Dr. Júlio de Matos, Porto | Science and technology with a large laboratory component |
| Baixa | Praça do Coronel Pacheco, Porto | Culture and creative industries |
| Mar | Avenida da Liberdade, Leça da Palmeira | Science and technology for the sea economy |
A company at Asprela II and a design studio at UPTEC Baixa need different sites, but they share a constraint: the founders have little time for website maintenance, and the site has to survive a funding round, a pivot and a change of marketing lead.
For research-led companies I usually set up three content collections. Product pages hold the commercial story. A publications or results collection holds papers, patents and conference talks with their DOIs and dates. A documentation collection holds technical notes in MDX that researchers edit through pull requests, with code blocks and formulas rendered at build time. The typed schema stops a draft without a date or an author from reaching production.
Investor pages stay deliberately plain: team, problem, traction your board has approved for publication, and contact. If a grant agreement requires a funding notice or logo block on the site, I add it as a shared component exactly as the agreement specifies, so it appears on every page that needs it and nowhere else.
Sea economy companies at the Mar centre in Leça da Palmeira sit next door to the port. Their sites often serve two audiences at once, scientific partners and industrial buyers in shipping or aquaculture, and they need separate entry pages for each with shared underlying data.
Careers pages for hiring engineers in Northern Portugal
Porto competes for engineers with Lisbon, with Spanish cities across the border and with remote employers anywhere in Europe. The University of Porto trains engineers at its Faculty of Engineering (FEUP), and the INESC TEC research institute sits on the FEUP campus with poles at ISEP, the University of Minho and UTAD. Porto Tech Hub has run its conference for more than ten editions. Graduates and experienced engineers in the region have options, and they compare employers on their phones before they apply.
A careers site that loads slowly, hides job descriptions inside an applicant tracking system iframe or exists only in Portuguese loses candidates at the first click. Each of those problems has a direct fix in the build:
- Job pages as real HTML generated from your applicant tracking system’s feed or from a content collection, each at a stable URL.
- JobPosting structured data following the Google Search Central job posting guidelines, with
validThroughset and the markup removed when the role is filled. - pt-PT and English versions of every role that accepts international applicants, with salary and contract information in the same place in both languages when your HR team decides to publish it.
- An engineering blog or team page in MDX, written by your engineers, so candidates see the actual stack and the actual people.
- A light application form as an island that posts to the ATS, with a link to the privacy notice that covers recruitment data.
Recruitment data is personal data under the GDPR, so the form, the retention period in your privacy notice and the ATS configuration have to agree with each other. I make the form and the notice link match. The retention period itself is your HR and legal decision.
How the Astro build works for these sites
Astro’s islands architecture renders every page to static HTML and hydrates only the components you mark with a client directive. On a Porto exporter’s catalogue that means the product table, the certificate list and the language switcher ship as plain HTML, while the quote form and perhaps a unit converter load their scripts when they come into view.
The practical effects:
- Core Web Vitals within the thresholds published on web.dev, LCP within 2.5 seconds, INP within 200 milliseconds and CLS within 0.1, are reachable on mid-range phones because there is no client framework to download before the first paint.
- Content collections with a schema validate every product, job and publication at build time. A missing field fails the build instead of producing a broken page.
- Static hosting on an edge network serves the same files to a buyer in Vigo and a candidate in Braga, with no database to patch.
- Interactive components in React, Svelte or Vue where your team already has them, mounted as islands without turning the whole site into a single-page application.
Editors who already work in WordPress can stay there. WordPress becomes the authoring backend, and Astro pulls content through the REST API at build time and publishes HTML. Teams without an existing CMS usually start with Markdown and MDX in Git, or a headless CMS chosen for the people who will edit it.
When Astro is the wrong choice
A logged-in customer portal with live shipment status, account management and complex client state is an application. For that layer I recommend Next.js or a framework your team already runs, and keep Astro for the public marketing and catalogue site in front of it. The Next.js developer in Porto page describes that split from the application side.
Portuguese law in the template: DL 24/2014, Lei 41/2004 and the CNPD
Portuguese rules on websites come from EU law transposed into national acts. I build the technical hooks; your lawyer or data protection officer approves the wording.
Distance contracts
Decreto-Lei n.º 24/2014, published in the Diário da República on 14 February 2014, transposes Directive 2011/83/EU on consumer rights. The decree covers contracts between traders and consumers, which matters in Porto because many exporters sell only to businesses. A pure B2B catalogue with quote requests falls outside it. A consumer shop next to the trade portal does not, and its checkout has to carry the pre-contract information, an order button that makes the obligation to pay explicit, and information about the 14-day right of withdrawal set by the directive.
Cookies and device storage
Article 5 of Lei n.º 41/2004, the Portuguese electronic communications privacy law, permits storing or reading information on a user’s device only with prior consent based on clear information. The exceptions are storage needed to transmit a communication and storage strictly necessary for a service the user requested. In an Astro build, analytics, heatmaps and advertising tags live inside a consent island and do not load until the visitor agrees.
Data protection supervision
Lei n.º 58/2019 of 8 August 2019 ensures the execution of the GDPR in Portugal, and its Article 3 names the CNPD (Comissão Nacional de Proteção de Dados) as the national supervisory authority. The CNPD breach notification page restates the duty under Article 33 of the GDPR to notify a personal data breach within 72 hours of becoming aware of it, unless the breach is unlikely to create a risk for the people affected.
What that means in the code
- Every third-party script is registered in one typed configuration file with its purpose and consent category, so your DPO can review the list in a pull request.
- Forms collect only the fields the brief names, post over HTTPS to the endpoint you specify, and link to the privacy notice in the language of the page.
- The consumer checkout, where one exists, gets the disclosure blocks and button label your lawyer approves, rendered from shared components so every product uses the same wording.
- Form endpoints and hosting logs have a named owner on your side, which is the person who needs to know about a breach within the 72-hour window.
Moving a Porto WordPress site to Astro
Many Porto sites I see started on WordPress, and the migration plan depends on what the site does today.
- Inventory first. I crawl the current site, export every URL with organic traffic from Search Console, and list the structured data, forms and scripts on each template.
- Redirect map before launch. Every URL that changes gets a 301 to its new address in the edge redirect file. URLs without a replacement get a decision in writing, kept or retired.
- Content model, then templates. Products, jobs, publications and pages become typed collections. Templates come from your designer’s approved layouts.
- Side by side measurement. The new site runs on a staging URL while I compare Lighthouse results, rendered HTML and structured data with the old one.
- Cutover and watch. DNS moves on an agreed date, and I monitor crawl errors and Search Console coverage for the following weeks.
A mid-sized catalogue site usually takes six to ten weeks, depending on the number of languages, the state of the content and how many integrations need rebuilding. The Next.js to Astro migration in Porto page covers the case where the current site is a React application.
How a project runs from Gdynia
I work remotely from Gdynia, Poland, and the project runs in writing. There are no on-site workshops in Porto or Matosinhos and no standing calls.
| Phase | What you receive | What I need from you |
|---|---|---|
| Brief review | Written questions and a list of risks | Site URL, languages, buyer types, design files |
| Scope note | Content model, page list, integrations, redirect plan | Confirmation of scope and launch date |
| Build | Staging URL updated with every change, changelog in Git | Content per language, legal text from your adviser |
| Compliance pass | Consent behaviour, form audit, checkout disclosures where relevant | Cookie classification and DPO sign-off |
| Launch | DNS checklist, redirect file, monitoring notes | A named owner for DNS and hosting accounts |
Reviews happen in pull requests, comment threads on staging or the ticket system your team already uses. I answer on CET working days, which is one hour ahead of Porto.
Checklist before you commission an Astro site in Porto
Whoever builds the site, these decisions save rework:
- Decide which buyer groups the site serves: export buyers, consumers, candidates, investors, or a mix.
- List the languages required at launch and the ones that can follow.
- Confirm with your lawyer whether any flow is a consumer distance contract under DL 24/2014.
- Classify every cookie and tracker before marketing adds a tag manager.
- Move datasheets and job descriptions out of PDFs and widgets into structured content.
- Freeze URL patterns per language before writers start.
- Name one owner for the domain, DNS and hosting accounts.
The local WordPress community meets as WordPress Porto, and its recent events took place in Matosinhos. It is a good place to hear how other Porto companies handled a rebuild.
Related services in Porto
- Next.js developer in Porto for logged-in portals and applications behind the public site.
- WordPress developer in Porto when editors stay in WordPress as the authoring backend.
- WooCommerce developer in Porto for a consumer shop that runs next to an Astro catalogue.
- PHP developer in Porto for a Laravel or Symfony backend that feeds the Astro front.
Start with a written brief
Send the current site URL, the buyer groups the site serves, the languages, the launch date and who delivers the design through the contact form. I answer on CET working days with questions or a scope note, and the first written estimate is free once the brief is detailed enough to price.
Selected projects
Examples of my work.
Corporate Website: neolight.pl
Neolight.pl is an advanced project in my portfolio as a WordPress developer, realised as an advertising portal supporting LED screen campaigns in Poland. Aro...
Corporate Website: ogloszenia.osemka.pl
Ogloszenia.osemka.pl is a classifieds portal that operated as a subdomain of the social platform Osemka.pl, designed and implemented in 2006-2007. The goal w...
Corporate Website: olsztyn.com.pl
Olsztyn.com.pl is one of the key projects in my WordPress developer portfolio, serving as a comprehensive city portal dedicated to the residents of Olsztyn. ...
WordPress support & development in Porto
See also in Portugal
Need this service: Astro developer in Porto?
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.