WordPress to Next.js Migration Service, Backed by 62,609 Tracked Switches
Enter your WordPress site's address. We read its sitemap, count the posts, pages and archives, and group them into the templates a Next.js rebuild needs. Our own team does the work.
Updated Nov 5, 2026Switches tracked by TechnologyChecker.io since May 19, 2026Delivered by our own teamEEReviewed by Emre Elbeyoglu, Growth & AI Advisor
Estimate your migration
Enter your WordPress site. We count its pages and templates from your sitemap in about a minute; the price comes as a fixed quote after a short call.
Built by people, sped up by AI. Our engineers rebuild and check every page; AI coding agents take the repetitive work. It is not an automatic converter.
- 24/7 supportReach the team any time during the project and for 30 days after launch.
- SEO-safe, keep your trafficSame URLs, a 301 for every one that changes, metadata moved page by page. If search traffic drops after launch, we fix the cause free.
- Tested in detailEvery page checked against the old site on desktop and mobile: links, forms, redirects, tracking and speed.
- Pay 50% now, 50% at the endHalf to start, the other half when the finished site is live and you've signed it off.
WordPress
9,555,391 live domains
3,722
domains won back from Next.js in 90 days
Next.js
731,970 live domains
42,415
domains gained from WordPress in 90 days
Live domains and switches come from TechnologyChecker.io's own crawl of 29.9M live business domains, read Nov 5, 2026. Counts are domains, not accounts.
Stay on WordPress if…
- Editors publish every day in wp-admin and nobody wants to change how they work.
- Plugins do real work on the site: a WooCommerce store, memberships, courses or bookings.
- Nobody on your team will look after a React codebase once it launches.
- The site is a simple content site, and a lighter tool such as Astro would do the job with less JavaScript.
Move to Next.js if…
- The website is becoming part of the product: logins, dashboards, calculators or pages built from your own data.
- Your product team already works in React and wants one stack for the site and the app.
- Plugin conflicts, security fixes and hosting take more time than publishing.
- You want every change reviewed in a preview before it goes live.
- You want to keep WordPress for editors and only replace the public site.
How we built this page
Every number names its source and the date it was read.
WordPress to Next.js: key findings
TechnologyChecker.io crawl, read Nov 5, 2026- The flow runs 12.3 to 1 toward Next.js. Since May 19, 2026, TechnologyChecker.io's crawl has seen 62,609 domains drop WordPress for Next.js and 5,084 go the other way.
- Next.js is the top destination for sites leaving WordPress. It takes 2.2× as many WordPress leavers as Astro, the next most common destination.
- 14.3% of the companies that moved are technology firms, against 3.4% of all WordPress companies (software, IT services and internet; 42,392 movers matched to a company).
- 60.4% of movers have 1–10 employees, against 66.1% of WordPress's base.
- WordPress runs on 13× as many live domains as Next.js (9,555,391 vs 731,970), and companies with 501+ employees make up 3.5% of Next.js's users against 1.6% for WordPress.
- 39,722 domains run both today, often a Next.js app on one host and the WordPress marketing site or blog on another, a headless setup, or a move still in progress.
WordPress runs more of the web than anything else, and most of those sites are fine where they are. Teams move to Next.js when the website has to work like part of the product, or when plugins and updates take more time than the site itself.
Site and product in one codebase
Next.js is a React framework, the stack many product teams already use. Logins, dashboards, pricing calculators, gated content and pages built from your own data live in the same codebase as the marketing pages. On WordPress, each of those is a plugin or a separate app bolted on.
Features without plugin conflicts
On WordPress, forms, SEO, caching and security each come from a plugin, and an update to one can break another. In Next.js those jobs are written into the site or handled by a service, pinned to a version and checked in a preview before they go live.
G2: 67 WordPress reviews mention “plugin issues”.
Less to attack on the live site
Every WordPress site exposes PHP, a database and a login page, and each plugin adds code to patch. A Next.js site has no wp-admin or plugin folder to probe, and pages that rarely change are served as static files. Its packages still need updates; those happen in the repository, not on the live server.
G2: 51 WordPress reviews mention “security issues”.
Change the site by chatting with AI, with review
The site is code in your repository, and content lives in a CMS or in files. Coding agents such as Claude Code, Cursor or Codex add a page, a component or a redirect from a plain-language request. WordPress has AI tools too; the difference is that every change here arrives as a pull request with a preview link you approve.
Code you own, hosted where you choose
Next.js is open source under the MIT licence and maintained by Vercel. It runs on Vercel, Netlify, Cloudflare or your own Node.js servers, and your content stays in WordPress, a CMS you pick or plain files. TechnologyChecker.io's crawl finds Next.js on 731,970 live domains in August 2026.
Our crawl: technology firms are 14.3% of the companies that moved, against 3.4% of all WordPress companies.
They work at different layers. WordPress is where editors write and how most sites are served; Next.js is a React framework that builds the public site and any app around it, from files, a CMS or WordPress itself. That is why a move can retire WordPress or keep it behind the scenes.
| Dimension | ||
|---|---|---|
| What it is | CMS: editors write in wp-admin and the theme renders each page | React framework for websites and web apps, from static pages to full products |
| Rendering | PHP on every request, unless a caching plugin or the host serves a copy | Static, server-rendered or refreshed in the background, chosen page by page |
| JavaScript | Theme, plugin and page-builder scripts on most pages | React on every page; Server Components keep much of the code on the server |
| Editing | The block editor in wp-admin, for anyone on the team | Headless WordPress, a CMS such as Sanity or Contentful, or Markdown files |
| Extensions | A plugin for almost everything, each one more code to update | Packages and services written into the site and reviewed in code |
| Hosting | A PHP host with a database, often managed WordPress hosting | Vercel, Netlify, Cloudflare, or any Node.js server or container |
| Security and updates | Core, theme and plugin updates, and a login page on the public site | No wp-admin on the public site; framework and package updates in the repository |
| AI agents | AI plugins and assistants inside wp-admin | Any coding agent in your repository: Claude Code, Cursor, Codex |
| Best for | Sites run by editors, and stores or member areas built on plugins | Sites that are part of a product: logins, dynamic pages and custom features |
Does moving to Next.js solve what WordPress users complain about?
G2, read Nov 5, 2026We read G2's published numbers for both listings on Nov 5, 2026: WordPress 4.4/5 from 9,556 reviews, Next.js 4.7/5 from 17. Of WordPress's 4 most-mentioned complaints, moving to Next.js solves 1, softens 2 and leaves 1 where it was.
WordPress's top complaints on G2, after the move
There is no plugin directory to keep in step. Features are code and packages pinned to versions, so an update can't break the live site unseen, but they still need updating.
We list every active plugin on the scoping call and replace each job with code or a service, tested before launch.
The curve moves to developers: Next.js reviewers mention a learning curve too. Editors keep a CMS form, so their part stays simple.
We set up the CMS before launch, train the editors and hand over a documented repository.
The public site loses wp-admin, PHP and plugin code, which is where most WordPress attacks land. Next.js and its packages still get security fixes that someone has to apply.
We leave dependency updates automated and the update path written down; in a headless setup, WordPress moves to a separate host you can lock down.
Nothing updates itself on the live site. Each update is built and checked in a preview first, and ships only when it passes.
The repository ships with automated update pull requests and a build check on each one.
Topic labels and mention counts are G2's, from 9,556 WordPress reviews; the verdicts and what we do about each are ours.
What you give up from WordPress
- Ease of use 135 praise itEditors keep a form to write in: WordPress itself in a headless setup, or a CMS with live preview.
- Customization 100 praise itLayout changes now go through code; a component library keeps common changes small, and a coding agent can make them on request.
- Plugins 94 praise itA new feature is a small build instead of a plugin install: our team, or a coding agent with review, adds it.
New problems you take on with Next.js
- Difficult setup outside Vercel 2 mentionsWe set up hosting on Vercel or your own infrastructure and document the deploy.
- Learning curve 2 mentionsThe handover covers how the repository, CMS and deploys fit together.
- Time-consuming deployment work 2 mentionsDeploys run on every merge, so shipping a change is a review, not a task.
- Confusing errors in production builds 1 mentionLogging and error reporting are wired in before launch.
From 17 Next.js reviews: a small sample, so read these as signals, not rates.
How G2 reviewers score each
Stated preference and revealed preference point the same way. G2 reviewers score Next.js higher on 4 of 4 shared criteria, on too few answers to call; our crawl shows the move itself, 12.3 domains leaving WordPress for Next.js for every one going back. For scale, WordPress's own G2 reviewers report 1 months to implement WordPress itself (2623 responses).
Who is switching from WordPress to Next.js?
TechnologyChecker.io crawl, read Nov 5, 202642,415domains moved from WordPress to Next.js in the 90 days to Nov 5, 2026 · 3,722 went the other way
Counted by TechnologyChecker.io's crawl. Switched = dropped WordPress on every host we track since May 19, 2026 and currently runs Next.js. A drop is a tag disappearing from our crawl, not a confirmed cancellation. 39,722 domains run both today. Counts are domains, not accounts.
“42,415 domains moved from WordPress to Next.js in the 90 days to Nov 5, 2026; 3,722 went the other way (TechnologyChecker.io's crawl of 29.9M live business domains, https://technologychecker.io/migration/wordpress-to-nextjs)”
Switches by month
Domains by the month WordPress (or Next.js) disappeared from our crawl. The first and last months are partial: tracking began May 19, 2026 and the data runs to Nov 5, 2026.
Recent switchers
| Company | Industry | Employees | Country | Seen |
|---|---|---|---|---|
| Reachology Limited | Public Relations and Communications Services | 11-50 | United Kingdom | Nov 5, 2026 |
| R.D. Suppliers Pvt. Ltd. | IT Services and IT Consulting | 11-50 | Nepal | Nov 5, 2026 |
| Rcems | Medical Practices | 11-50 | United States | Nov 5, 2026 |
| Rbqlicence | Construction | 11-50 | Canada | Nov 5, 2026 |
| Raysautocare | Vehicle Repair and Maintenance | 11-50 | Indonesia | Nov 5, 2026 |
| Rainwater INC. | Consumer Electronics | 201-500 | Turkey | Nov 5, 2026 |
| Raya | Higher Education | 501-1000 | Egypt | Nov 5, 2026 |
| Rarrtech | Software Development | 11-50 | India | Nov 5, 2026 |
What kind of company leaves WordPress for Next.js?
TechnologyChecker.io crawl, read Nov 5, 2026We matched 42,392 of the 62,609 domains that moved to a company record. Technology firms lead at 14.3%, 4.2× their share of WordPress's base, followed by advertising services, construction, and business consulting and services. By size, 60.4% have 1–10 employees against 66.1% of WordPress's base.
By industry
By company size
By country
Where do sites leaving WordPress go?
TechnologyChecker.io crawl, read Nov 5, 2026Next.js is the most common destination for domains that drop WordPress: 62,609 since May 19, 2026, against 28,583 for Astro, the next most common.
WordPress vs Next.js: who runs each
TechnologyChecker.io crawl, read Nov 5, 2026By company size
By industry
Fast pages, tested before launch
Pages that don't change are served as static HTML, images and fonts are optimised, and React Server Components keep code on the server where visitors don't download it. Every template is tested against Google's Core Web Vitals on mobile before launch, because Next.js alone doesn't make a site faster.
HTTP Archive, September 2026: 35.7% of Next.js sites pass Core Web Vitals on mobile, against 48.3% of WordPress sites (56.9% vs 53.7% on desktop). Many Next.js sites are heavy apps; moving alone doesn't make a site faster, building it right does.
Publish by chatting with AI, or keep a CMS
Describe a change to a coding agent such as Claude Code, Codex or Cursor: a new landing page, a pricing update, a redirect. It edits the code, runs the build and opens a pull request with a preview link, and nothing goes live until you approve it. Editors who prefer a form keep one: headless WordPress or a CMS you pick.
Editors publish, the site updates itself
Pages are served as static files and refreshed in the background when content changes, so a post published in wp-admin or your CMS goes live without a full rebuild or a developer.
Price follows the size of the site, counted in pages from your sitemap, CMS items included. Each package covers the rebuild, the content import, redirects, testing and launch. Stores, member areas, logins, multilingual plugins such as WPML and custom plugins are scoped on the call, because that is where WordPress estimates go wrong.
| Package | Price | Timeline |
|---|---|---|
| Small siteUp to 100 pages · A marketing site with a small blog | $1,500–$2,500 | 1 week |
| Medium siteUp to 1,000 pages · Several CMS collections, a few hundred items | $2,500–$4,000 | 2–3 weeks |
| Large site1,001+ pages · A large blog or resource library | $4,000–$6,000 | 4–5 weeks |
Does it pay back? It rarely does on hosting alone. It pays when developer control, performance and workflow speed are worth more than WordPress's convenience. For reference, WordPress's G2 reviewers report 10 months to see a return on WordPress itself (1793 responses).
The right method depends on whether you have React developers and whether marketing still needs to publish without them.
Rebuild in Next.js yourself
Developer time · 2–8 weeks
Export the content with Tools → Export or the REST API, move it into a CMS or Markdown files, and rebuild the theme as React components and Next.js routes. Vercel publishes a starter template for a WordPress-backed Next.js site.
Best for: Teams with a React developer and a site without heavy plugins
Go headless: keep WordPress, add Next.js
Developer time · 2–6 weeks
Editors keep wp-admin, and a Next.js front end reads posts from the WordPress REST API or WPGraphQL. WordPress keeps running behind the scenes, so it still needs hosting and updates.
Best for: Editorial teams that publish daily and won't leave wp-admin
Hire a migration team
Fixed quote after a scoping call · 1–5 weeks, by size
One team runs the whole job: content export, the Next.js build, forms, redirects, testing and launch. You trade budget for speed and skip the learning curve.
Best for: Sites with search traffic or leads you can't put at risk
Costs and timelines are typical market ranges for planning, not figures from our data. Our own price for your site comes from the calculator above.
Every template rebuilt in Next.js
Your theme rebuilt as React components and Next.js routes, matching the current design, static wherever the content allows.
All content moved
Posts, pages, categories, tags, authors and custom fields moved into your chosen CMS or into files, cleaned of builder markup.
URLs and rankings protected
Same URLs wherever possible, a 301 for every one that changes, and titles, descriptions and canonicals carried over from your SEO plugin.
Plugin jobs replaced
Forms, search, redirects, analytics and comments rebuilt or moved to a service, each one tested before launch.
Set up for AI agents
An AGENTS.md that describes the project and its components, so coding agents can add pages and features when your team asks, with review.
Launch and handover
DNS switch, a final check against the old site on desktop and mobile, and a recorded walkthrough of the editing setup and the codebase.
- Page-builder and shortcode markupPosts built with Elementor, Divi or WPBakery export as builder markup and shortcodes, not clean content. A converter copies the clutter across.
Each builder layout becomes a React component that matches the design, and every post's content is cleaned of builder markup and shortcodes.
- Plugins doing real jobsForms, SEO metadata, redirects, search and analytics often come from plugins, and each one stops working the day the theme goes.
We list every active plugin on the scoping call and replace each job: a form handler, metadata from the CMS, redirects in the Next.js config, a search index.
- WordPress URLs and archivesDate-based permalinks, category and tag archives, /page/2/ pagination, feeds and attachment pages all have URLs Google already knows.
We keep every URL we can, 301 the rest, rebuild the RSS feed and the sitemap, and check every old URL against the new site before launch.
- Images in /wp-content/uploads/Posts point at images in /wp-content/uploads/, often in several sizes, and other sites link straight to them.
We move the media library, serve images through Next.js image optimisation, and keep or redirect the old upload paths so links and image search don't break.
- Too much JavaScript on mobileA React site can ship more JavaScript than the WordPress theme it replaces, and pass Core Web Vitals less often on phones.
Pages stay static unless they need data, components render on the server by default, and every template is tested on a mid-range phone before launch.
- Editors losing wp-adminWriters who publish in wp-admin every day need somewhere to write after the move.
We pick the editing setup with you: WordPress as a headless CMS, a CMS such as Sanity or Contentful, or Markdown with an AI agent. The team is trained before launch.
You don't have to retire WordPress. In a headless setup, editors keep writing in wp-admin while Next.js serves the public site from the WordPress REST API or WPGraphQL, with WordPress moved to a subdomain such as cms.yoursite.com. Visitors only ever load the Next.js site.
Our crawl sees 39,722 domains running WordPress and Next.js at the same time (Nov 5, 2026). Some are partway through a move; many are a deliberate split.
If your editors won't leave wp-admin, we build the Next.js front end on your WordPress first and move the content later, or never.
Ask any partner these questions before you sign, us included. A fixed price before anyone has looked at your interactions and CMS is a guess you pay for later.
| Ask | Our answer |
|---|---|
| Will you look at our plugins and page builder before you quote? | Yes. We list every active plugin and the builder behind each template on the scoping call, and quote from what the site actually runs. |
| How will you protect search traffic? | Same URLs wherever possible, a 301 for every one that changes, titles and descriptions moved from Yoast or Rank Math, a new sitemap, and Search Console watched after launch. |
| How will you keep the new site fast on phones? | Static pages wherever content allows, server-rendered components, optimised images and fonts, and a Core Web Vitals test on every template before launch. |
| Where will our editors write after the move? | We agree it before the build: headless WordPress, a CMS such as Sanity or Contentful, or Markdown files with an AI agent. |
| Who owns and hosts the site when you're done? | You do. The code lives in your repository and deploys to Vercel, Netlify, Cloudflare or your own servers. |
- 01EstimateEnter your site's address. The calculator counts your posts, pages and archives from the sitemap WordPress or your SEO plugin publishes.
- 02Scoping call and fixed quoteWe go through your plugins, page builder, forms and editing needs, agree a full move or headless, and send a fixed price and timeline.
- 03BuildOur engineers rebuild the templates first, using AI agents for the repetitive parts such as content clean-up, then move the content and check every page against the live site.
- 04LaunchWe switch DNS, watch errors, speed and Search Console, and hand over the repository and the editing setup.
Expert review: is moving from WordPress to Next.js worth it?
Reviewed Nov 5, 2026Stay on WordPress when editors and plugins carry the site, or when it's a simple content site: Astro would do that job with less JavaScript. Move to Next.js when the website is turning into part of the product, with logins, dashboards or pages built from your own data, and your team already works in React. That is where one codebase for the site and the app pays off.
There are two real risks. The first is search: WordPress sites carry years of URLs, from dated permalinks to tag archives and image paths, and each one has to resolve or 301 with its title and description intact. The second is speed: a React site can ship more JavaScript than the theme it replaces, so every template has to be tested on a phone before launch, not after.
Before you migrate: Emre's 4 checks
- List every URL before you startExport the URLs from your sitemap, your SEO plugin and Search Console's Pages report, including tag, category and attachment pages. That list becomes the redirect map.
- Write down what each plugin doesGo through Plugins in wp-admin and note the job each active plugin does. Most of the build plan comes from that list.
- Decide where editors will writeHeadless WordPress, a CMS, or Markdown with an AI agent: pick before the build, because it decides how the content is stored.
- Record your mobile speed firstSave your current Core Web Vitals from Search Console or PageSpeed Insights, and agree that no template launches slower on a phone than the page it replaces.
Where this data comes from
Analysed Nov 5, 2026Our detection data
Switching counts, destinations and both platforms' user bases come from TechnologyChecker.io's own monthly crawl of 29.9M live business domains. A switch is an observed change: a domain dropped WordPress on every host we track and now runs Next.js. Company attributes come from company records matched by domain (42,392 movers matched).
Full detection methodology →The calculator
It reads only what your site publishes: robots.txt, the sitemap and up to eight sampled pages. Nothing is stored unless you ask for a quote. Pages missing from your sitemap, gated content and app-like features aren't counted; the scoping call covers them.
G2's published numbers
Ratings, respondent counts and pros-and-cons topic counts for both listings, read on Nov 5, 2026. Numbers only: no review text is reproduced, and every count links back to G2. The verdicts on each complaint are ours.
G2's comparison →TechnologyChecker sells this migration. The switching numbers come from the same crawl that powers our technology profiles and are not adjusted for this page.
How much does a WordPress to Next.js migration cost?
Our packages price by page count: up to 100 pages $1,500–2,500, up to 1,000 pages $2,500–4,000, and $4,000–6,000 above that. WordPress sites get a fixed quote after a scoping call, because plugins, page builders and app features vary more than page count does. You pay 50% to start and 50% when the site is live.
How long does a WordPress to Next.js migration take?
About one week for a small site, two to three weeks for a medium one and four to five weeks for a large one. A store, a member area, logins or a heavy page-builder clean-up can add time; the timeline is fixed in the quote.
Will I lose my Google rankings when I move from WordPress to Next.js?
Not if URLs and metadata move with care. We keep every URL we can, 301 every one that changes, carry over titles, descriptions and canonicals from Yoast or Rank Math, publish a new sitemap and watch Search Console after launch. If search traffic drops after launch, we find and fix the cause at no extra cost.
Will moving to Next.js make my site faster?
Only if it's built for speed. In HTTP Archive's September 2026 report, 35.7% of Next.js sites pass Core Web Vitals on mobile against 48.3% of WordPress sites, because many Next.js sites are heavy apps. We keep pages static where we can, render components on the server and test every template on mobile before launch.
Can my editors keep using WordPress after the move?
Yes, with a headless setup. Editors keep writing in wp-admin, and Next.js serves the public site from the WordPress REST API or WPGraphQL. WordPress still needs hosting and updates, but it's no longer what visitors load. If you'd rather retire it, the content moves to a CMS you choose or to files.
What happens to my WordPress plugins?
Each plugin's job gets a replacement. Forms go to a form handler, SEO fields move into the CMS, redirects move into the Next.js config, and search runs from an index. We list them all on the scoping call, so nothing stops working by surprise.
Can you migrate a site built with Elementor or Divi?
Yes. Page-builder layouts are rebuilt as React components that match the design, and the builder's markup and shortcodes are cleaned out of each post. Converters handle this part worst, so engineers do it, with AI agents taking the repetitive clean-up.
What about WooCommerce, logins or a members area?
We scope them on the call. Next.js runs server code, so logins, member areas and custom app features can live in the same codebase. A store either stays on its own platform, such as WooCommerce on a subdomain or Shopify, or runs headless behind the Next.js front end.
Where is a Next.js site hosted, and what does it cost to run?
Anywhere that runs Node.js: Vercel, which makes Next.js, plus Netlify, Cloudflare or your own servers. A content site that is mostly static pages often fits a free or low-cost plan. Logins, heavy traffic or server-rendered pages cost more, so we size hosting on the scoping call.
Can I manage a Next.js site by chatting with AI?
Yes. Coding agents such as Claude Code, Cursor or Codex add pages, components and redirects from plain-language requests. The repository ships with an AGENTS.md, and every change arrives as a pull request with a preview link you approve.
Who does the migration?
TechnologyChecker's own engineers, not an automatic converter. People plan the build, write and review the code and check every page; AI coding agents take the repetitive work. We run the detection crawl behind the switching numbers on this page, and we deliver migrations ourselves rather than passing them to a partner.
How does the calculator count pages for a WordPress site?
It reads your robots.txt and the sitemap WordPress or your SEO plugin publishes, and groups the URLs into page designs and collections such as posts. If the sitemap lists category and tag archives, they count too, because each needs a template or a redirect. We confirm the count on the scoping call.
Where do the switching numbers come from?
From TechnologyChecker.io's own detection crawl of 29.9M live business domains, run every month. A domain counts as WordPress when its pages load WordPress theme or core files, or carry its headers or generator tag, and as switched when every WordPress signal is gone from the hosts we track and it runs Next.js. A headless build counts as a switch only when the WordPress backend sits on a host we don't track; otherwise the domain counts as running both. Counts are domains, not companies.
Which is better, WordPress or NextJS?
It depends on who runs the site. WordPress is better when editors and plugins carry it: a blog, a store or a member area without developers. Next.js is better when the site is part of a product and engineers own it: logins, dashboards, custom features and one codebase with the app.
Can Next-js be used with WordPress?
Yes. In a headless setup, WordPress stays the CMS and Next.js serves the public site, reading posts through the WordPress REST API or WPGraphQL. Editors keep wp-admin; visitors load the Next.js site. TechnologyChecker.io's crawl finds 39,722 domains running both in November 2026: headless setups, apps next to a WordPress site, and moves still in progress.
What are the downsides of NextJS?
It needs developers: there is no admin panel, and features that are plugins on WordPress are code. Sites can ship too much JavaScript, which is why only 35.7% of Next.js sites pass Core Web Vitals on mobile in HTTP Archive's September 2026 report. Hosting outside Vercel takes more setup.
Is Next.js still relevant in 2026?
Yes. TechnologyChecker.io's crawl finds Next.js on 731,970 live domains in August 2026, and it is the most common destination for sites leaving WordPress: 62,609 domains since May 19, 2026, against 5,084 that went the other way.
Is NextJS better than Astro?
For different sites. Astro ships less JavaScript and suits content: posts, landing pages and docs. Next.js suits sites turning into apps, with logins and dashboards. Among domains leaving WordPress since May 19, 2026, TechnologyChecker.io's crawl finds 62,609 moving to Next.js and 28,583 to Astro. We build both and say which fits on the call.
Includes questions people also ask on Google about this move, quoted as Google shows them; the answers are ours.