Skip to content
Babczynski.ITMarketing · AI · IT for business

Websites, shops and platforms

WordPress or a Modern React Website: What to Choose in 2027

WordPress or React? I compare content editing, security, speed and SEO, and suggest when to choose which technology.

Piotr BabczyńskiSEO, ads and AI for business · 30 years in ITPublished 6 min read

In short

  • WordPress wins on easy content editing and a huge ecosystem, but needs constant updates.
  • React with server-side rendering gives speed and flexibility, but changes to structure are usually made by a programmer.
  • Google recommends server-side rendering or pre-generating pages as good practice.
  • To measure speed, use Core Web Vitals: LCP, INP and CLS.
  • When migrating, use 301 redirects from the old addresses to their equivalents.
Table of contents (9)
  1. How the two approaches differ
  2. WordPress: what it gives and what you pay for
  3. A modern React website: what it gives and what you pay for
  4. WordPress or React: a comparison table
  5. Speed and SEO: what to look at
  6. When to choose WordPress and when React
  7. Migrating from WordPress without losing rankings
  8. Where to start choosing a technology
  9. Frequently asked questions

I hear the question "WordPress or React" from business owners more and more often, usually when they are getting a new website or rebuilding an old one. Both routes work, and both have their place. Below I compare them honestly, without mocking WordPress and without promoting modern technologies for fashion's sake.

How the two approaches differ

WordPress is a content management system (CMS). You install it on a server, choose a theme, add plugins and edit content in a panel. The whole website, from the look to the forms, is put together from ready-made blocks.

A modern React website is built as a program. The content and the look are described by code, and the page is usually generated on the server side. Frameworks such as Next.js or TanStack Start are used for this. You can edit the content in a custom-built panel or in a separate system such as a headless CMS, which only stores texts and photos.

The shortest difference: WordPress gives you a ready tool that you configure. React gives you a tailored solution that you design.

WordPress: what it gives and what you pay for

Illustration: a website panel with many plugins needing updates

The biggest advantage is easy content editing. A person without technical knowledge will change a text, add a post or a photo in a few minutes. The second asset is the ecosystem: for most typical needs (a form, bookings, a shop, translations) a ready-made plugin exists. There are many contractors, so it is easy to find someone to help.

The price of this convenience is maintenance. The official WordPress.org recommendations say plainly that you should update the core of the system, plugins and themes, and delete unused plugins. Older versions do not receive security fixes. Every plugin is extra code from another author, so the more of them there are, the more places that need attention.

The second issue is performance. A website with many plugins and a heavy theme can be slow. It can be sped up, but this takes deliberate work: choosing plugins, caching, image optimisation.

From practice: most problems with WordPress websites do not come from the system itself. They come from the fact that after launch nobody is responsible for updates and backups.

A modern React website: what it gives and what you pay for

With server-side rendering, the page reaches the browser as ready HTML and only then "comes alive". This gives good speed, and the code is written only for your needs, without unnecessary extras. The attack surface is also smaller: there is no login panel open to everyone, no database exposed to the world, and no dozens of plugins to patch. This does not mean such a solution is immune to errors. Dependencies and the server also have to be watched, there are just fewer of them.

The greatest flexibility appears with non-standard features: your own calculator, integration with a company system, a customer panel, login. In WordPress this often cannot be done cleanly, while in React it is everyday work.

The downside is concrete. A change to the structure of the website, a new type of subpage or a new feature usually requires a programmer. You can edit content yourself if a panel or a headless CMS has been set up, but the layout you cannot. There are also fewer contractors than for WordPress, so it is worth making sure you have documentation and access to the code on your own account.

WordPress or React: a comparison table

The table shows the differences in typical builds. A specific project may look different.

CriterionWordPressReact with server-side rendering
Content editingVery easy, a ready panel, a block editorDepends on the build: a custom panel or a headless CMS
Cost of maintenanceUpdates, backups, oversight of plugins; usually regular, small workFewer ongoing updates, but structural changes need a programmer
SecurityNeeds constant updates of the core, plugins and themesA smaller attack surface, but dependencies and the server also need oversight
SpeedDepends on the theme and the number of plugins, can be improvedUsually very good, because the code is tailored to the project
SEOGood tools and plugins, content ready in HTMLVery good with server-side rendering, a risk with browser-only rendering
FlexibilityLarge within plugins, limited beyond themPractically unlimited
Availability of contractorsVery largeSmaller, but sufficient

The exact costs of both solutions depend on the scope. I write about them separately in the post how much does a business website cost.

Speed and SEO: what to look at

Website speed is best assessed through Core Web Vitals. These are three metrics described on web.dev: LCP (loading speed of the main content), INP (response to clicks) and CLS (layout stability). Google assesses them on the basis of data from real users, so what counts is how the website works for your customers, not just in a test on a fast computer.

As for the search engine: Google Search Central's documentation on JavaScript SEO says that Google can run JavaScript and index such pages, but server-side rendering or pre-generating the page is still a good idea. The page is then faster for people and for robots, and not every robot copes with JavaScript. That is why with React I choose server-side rendering and do not base visibility on content assembled only in the browser.

This does not mean WordPress is worse at SEO. It delivers ready HTML and has mature tools. A well-made website on either technology can have good visibility. Rankings are decided above all by content, structure and speed, not by the technology itself.

When to choose WordPress and when React

Two website speed gauges, one slow and one fast

The answer depends on what your website is to do and who will run it.

WordPress will do well when:

  1. the website is mainly content: a blog, an offer, a portfolio, a company business card,
  2. the budget is limited and the needs are standard,
  3. you want to change texts, photos and subpages often yourself,
  4. the feature you need has a ready, proven plugin,
  5. someone in the company or at a trusted contractor will take care of updates.

I would choose React when:

  1. the website is to be an application: a customer panel, a calculator, bookings, a configurator,
  2. you need integrations with company systems such as a CRM, payments or your own database,
  3. you care about high performance and full control over the code,
  4. the editing panel is to look exactly the way your processes work,
  5. you have a permanent programmer or a contract for further development.

From practice: before you choose a technology, list five things the website is to do a year from now. If all of them are content and a form, WordPress is usually enough. If login or integrations appear, the conversation turns to something more.

If the website is above all to win enquiries, what is on it matters more than the technology. I described this in the post a website that collects enquiries. When you need more than a website, take a look at the offer for web applications.

Migrating from WordPress without losing rankings

Moving to a new technology does not have to cost you visibility in Google if you take care of the addresses. Google's documentation on site moves recommends permanent server-side redirects (301 or 308) from the old addresses to their new equivalents. According to that documentation, 301 redirects do not cause a loss of PageRank.

What this means in practice:

  1. Make a full list of the old website's addresses, including the posts and subpages that bring traffic.
  2. Assign each address its equivalent on the new website, one to one.
  3. Do not send many old addresses to the home page. Google may treat this as a soft 404 error.
  4. Avoid chains of redirects: the old address should lead straight to the final one.
  5. Keep the redirects on for a long time. Google indicates at least a year.
  6. After launch, check Google Search Console for errors and changes in indexing.

If the new website keeps the old addresses, there will be fewer redirects, but they still have to be tested before launch.

Where to start choosing a technology

Start with the goal, not the technology. Answer three questions: what is the website to do a year from now, who will change the content and who will take care of maintenance. Add to that a budget for the first build and for later care.

Then look at your current website. If it runs on WordPress, is fast and is enough, there is no reason to change it. If it blocks you with integrations, is slow despite attempts at optimisation, or its maintenance causes trouble, then migration makes sense.

If you want to discuss this on a specific example from your business, write to me. I will tell you what is enough in your situation and what would be overkill.

Frequently asked questions

Is a React website better for SEO than WordPress?

Not by definition. A well-made website on either technology can have good visibility. With React, server-side rendering matters, because Google recommends it in its documentation on JavaScript SEO. Rankings are decided mainly by content, structure and speed.

Can I edit content on a React website myself?

Yes, if an editing panel or a headless CMS has been set up. Layout changes or new types of subpages usually need a programmer, though. It is worth agreeing this split at the project stage.

Is WordPress dangerous?

No, as long as it is kept updated. The official WordPress.org recommendations talk about updating the core, plugins and themes and deleting unused plugins. Problems usually start when nobody takes care of this.

Will changing the website's technology lower my rankings in Google?

It does not have to, if you take care of the addresses. Google recommends permanent server-side redirects from the old addresses to the new ones and keeping them for a long time. After launch, check the reports in Search Console.

What does the cost of a website depend on in each technology?

On the scope, the number of features, the integrations and how much work there is after launch. The technologies alone do not decide the price. I write more about this in the post on the cost of a website.

Sources

  1. Google Search Central: podstawy JavaScript SEO
  2. Google Search Central: przeniesienie witryny ze zmianą adresów URL
  3. web.dev: Core Web Vitals
  4. WordPress.org: Hardening WordPress
Piotr Babczyński

Author

Piotr Babczyński

I help businesses win customers online: SEO, Google and Meta ads, automation and AI. I work from Szczecin, Poland, and remotely. I write about what I test on real projects.

  • 30 years in IT
  • SEO and Google Ads
  • AI implementation
More about me
  • #WordPress
  • #React
  • #website
  • #SEO
Last updated:

Keep reading

More on Websites, shops and platforms

Free consultation

Let's talk about your business

A no-obligation chat: I'll tell you what will really bring you more customers and what it costs. I reply within 24 hours.

Piotr Babczyński working on a laptop