Choose around the people using and running the website
WordPress and React solve different parts of a website. WordPress provides a content-management platform. React provides a way to build interfaces from components and manage their interactive states. They can be used separately or together.
The right starting point is the work: what the visitor needs to do, what the team needs to publish and which systems must stay connected. That gives the architecture a purpose.
Three useful routes
These are planning patterns rather than fixed packages. Each still needs decisions about hosting, rendering, forms, security and maintenance.
| Route | Useful when | Plan for |
|---|---|---|
| WordPress-led | The main work is publishing service pages, articles or a catalogue with established journeys. | Reusable content models, a considered theme, plugin ownership and the required integrations. |
| React-led | The main experience is an application, configurator, dashboard or detailed multi-step journey. | A backend and API, state and error handling, rendering, editorial needs and deployment ownership. |
| Combined | A publishing team needs familiar editing while customers need richer interactions. | A clear boundary between managed content, server-rendered pages, React components and application rules. |
Consider publishing and content ownership
Ask who will create pages, update a service description or publish a case study. WordPress can provide familiar editing and structured records. The frontend still needs templates that turn those records into a coherent customer journey.
A React-led application may need a separate publishing model or an integrated CMS. Content should not become dependent on a developer for routine changes unless that trade-off is deliberate.
Look at the interaction beyond the page
A quotation journey may have quantities, options, pricing feedback and steps that depend on previous choices. React can help present those states clearly. The authoritative pricing, permission and transaction rules still need an appropriate backend.
A content page has different needs. Useful navigation, responsive layout and a clear enquiry can often be delivered with less client-side complexity. The choice can vary within the same website.
Plan discoverability and resilience explicitly
Neither a technology label nor a successful browser demonstration establishes search readiness. The implementation needs crawlable links, useful page text, correct responses and consistent canonical addresses. We also check the important journey with JavaScript unavailable where that journey is intended to support it.
On the JAS website, WordPress owns the content while server-rendered markup and React share the frontend experience. That is one example of combining publishing and interaction around a defined content structure.
Google’s JavaScript SEO guidance
Make the maintenance boundary visible
A proposal should explain who owns the content model, frontend, API, third-party connections and release process. It should also identify how changes are tested and how the team recovers when a release needs reversing.
Combining tools can be useful, but each extra boundary needs a reason and an owner. We choose the smallest coherent arrangement that supports the agreed journeys and the people maintaining them.
Bring examples to the decision
A few representative pages, the most complex form and an example transaction will reveal more than a preference for a framework. We can compare the routes against that material and explain what each implies for design, delivery and ongoing operation.
WordPress development in London

