Next.js / Astro migration in Manchester

Freelance Astro developer for Manchester firms: new Astro sites and WordPress migrations with your URLs kept. Remote from Poland, reply in 48 hours.

Next.js / Astro migration

Website & application migration in Manchester

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.

My WordPress.org profile

I am Mariusz Szatkowski, a freelance Astro developer working from Gdynia, Poland. I am one person, not an agency, and I have no office in Manchester. If you searched for an Astro development agency in Manchester, you should know that before you write to me: the person who scopes your site is the person who builds it.

This website runs on Astro 7 and Cloudflare Pages, so what I describe below is the stack I use every day. I work for businesses in Manchester, Salford and the rest of Greater Manchester, and for firms elsewhere in the UK. Gdynia is on Central European Time, one hour ahead of the UK. I work through email and shared documents and answer within 48 hours.

My wordpress.org account dates from 2006. Credentials you can check: core contributor to WordPress 7.0 and 7.1, 30 plugins in the wordpress.org directory, WordCamp organiser and speaker, and at every WordCamp Europe from 2017 to 2026.

#What I build with Astro

Astro renders most of a page to static HTML and adds JavaScript only for the small interactive parts, which the Astro documentation calls islands (Islands architecture). A service page, a case study or an article therefore arrives as plain HTML, and a quote calculator or a course finder loads its script on its own.

That suits sites where most pages are read, not operated: company sites, publications, documentation, event sites, portfolios. It suits them less when most pages depend on who is logged in. For that I use a different tool, and I say so in the written scope. My general Astro service is described on the Astro developer page.

#Moving a WordPress site to Astro

The Astro documentation names three differences you will feel after a move: editing happens in a code editor, not a dashboard; many plugin features have to be built or replaced; and content lives in files instead of a database, unless you keep a CMS (Migrating from WordPress). Each difference decides which of three routes fits.

  1. WordPress stays as the editor, Astro becomes the public site. Astro reads your posts and pages through the WordPress REST API, or through WPGraphQL if you add it (Headless WordPress and Astro). Your editors change nothing about how they work.
  2. Content moves into the repository. Pages become Markdown or MDX files. This is the cheapest to run and the least friendly to non-technical editors.
  3. A different CMS behind Astro. Worth it only when the WordPress admin itself is the problem.

Which route fits depends on who edits, how often and how many people. I ask those three questions first. The general pattern is described on the Next.js and Astro migration page and the headless CMS developer page.

#Keeping your Google rankings during the move

Most ranking losses after a migration come from addresses nobody wrote down. I list every URL from a crawl, Google Search Console and server logs, then decide for each one: same path, or one permanent redirect to the closest successor. Astro lets you declare permanent redirects as a mapping of old paths to new ones in its configuration (Routing, redirects).

I do not redirect a group of old pages to the homepage. Before the switch I fetch representative pages from both versions and compare status codes, titles, descriptions, canonicals and links. For sitemaps I use the official Astro sitemap integration, which the documentation recommends for large multi-page sites (sitemap integration).

If your slow WordPress site only needs tuning, I say that instead of proposing a new frontend. The tuning work is on the speed up WordPress page.

#Design comes from you, the build from me

Graphic design, UX, mockups and wireframes are outside what I offer. If you are looking for an Astro web designer in Manchester, you need a designer first and a developer second. You or your designer supply the design as a Figma file or a wireframe, and I build it as a working, fast, accessible site.

A design that covers mobile layouts, error states and the forms saves the most time. If a screen cannot be built accessibly, for example pale grey text on a white card, I tell you which screen before I build it.

#Astro hosting for UK sites

A static Astro build is a folder of files, so it runs on almost any host. I deploy to Cloudflare, as for this site. The Astro deploy guide now recommends Cloudflare Workers for new projects and points existing Pages projects to Cloudflare’s migration guide (Deploy to Cloudflare). I follow that for a new build.

If your company needs a specific host, for instance one your IT team already manages, tell me in the brief and I deploy there. Astro publishes deploy guides for many hosts. Where the site is served from and where its forms and analytics send data are separate questions, and I list both in the handover.

#Manchester and Salford in numbers

Manchester had about 551,900 residents at the 2021 census, up 9.7% from 2011 and the third-largest percentage rise in the North West (ONS, Manchester). Next door, Salford grew 15.4% to about 269,900, the largest rise in the region (ONS, Salford). England grew 6.6% over the same decade.

I do not treat that growth as a reason to build a local-only site. I build for the market you sell to, and your own area is one of the places you want to rank for. Local landing pages for Manchester and Salford are fine when each one has something true to say about the service, not a swapped place name.

If you later hire in-house developers, Manchester Digital, an independent not-for-profit that has backed Greater Manchester’s tech sector since 2001, runs events and programmes in the region (Manchester Digital).

#UK rules that touch a website move

Cookies, analytics consent, accessibility duties and VAT on invoices from a Polish sole trader are covered once on the software development for the UK and Ireland page, with links to the legislation. During a migration I check that the consent banner and analytics still behave as you configured them, because a new frontend often drops scripts that a WordPress plugin used to add.

#Where Astro is the wrong choice

If most pages need a login, a basket or per-user data, a framework built around static pages adds friction. Next.js is then the better fit, and it can sit beside Astro on the same domain. I also advise against a migration when a handful of slow templates can be fixed in place, or when nobody on your side will own updates after launch. My Manchester page for the other framework is Next.js developer in Manchester.

#How a project runs

  1. You send the current address, the brief and the design file.
  2. I send an audit of URLs, content and integrations, with a recommendation to repair, rebuild in WordPress or move to Astro.
  3. I write up scope, assumptions and exclusions in a document. Work starts after you confirm it in writing.
  4. I build on a preview address you can open, and you test it.
  5. I switch over with a written rollback path, then watch 404s, indexing and form submissions against the starting numbers.
  6. You receive the repository, the redirect map and documentation for editors and developers.

I do not propose calls or meetings. Writing each decision down gives you the reasons behind it later.

#Questions people ask before writing

Are you an Astro development agency in Manchester? No. I am a sole proprietorship in Gdynia, Poland, working remotely, with no office in Manchester. You deal with one developer, with no account manager in between.

Can you design the site as well as build it? No. You or your designer provide the design as a Figma file or a wireframe, and I build it as a fast, accessible Astro site.

Do we have to leave WordPress? No. Astro can read content from WordPress through the REST API or WPGraphQL, so editors keep the admin they know while the public site becomes Astro.

Will we lose our Google rankings? Not if the move is planned. Every old URL keeps its path or gets one permanent redirect to its closest successor, and I compare old and new pages before the switch.

How do I start? Send the current site address, the problem and the goal by email. I answer within 48 hours and recommend a next step.

See also in Great Britain

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

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

Describe your project

Explore other WordPress services and knowledge base