React vs Next.js for a Marketing Site That Must Rank

A client-only React SPA is a poor default for pages you need in search. Next.js (or a Laravel shell) changes the rendering story.

A client-only React SPA is a poor default for pages you need in search. Crawlers have improved. They have not made it free to ship a blank shell, hydrate late, and hope the title tag survives a redirect chain.

We build React products and Next.js sites. The question on a marketing brief is not “which is modern.” It is whether the first HTML the bot receives is the page.

When a SPA is fine

Signed-in apps, dashboards, and tools behind auth. Those URLs should usually be noindex anyway. React in a Laravel Inertia or API setup is a normal way to ship Laravel + React products. That is not the same job as the homepage, service pages, and blog.

If your “marketing site” is actually the app’s marketing routes, Next.js (App Router, sensible caching) or a server-rendered Laravel front is the usual recommendation. We will not wrap a five-page company site in a SPA because the designer handed over a React prototype.

What ranking still needs

Stable URLs, one H1, unique titles, a canonical, and content that is not a client-only afterthought. Internal links that work without a click handler. Images with dimensions. That is boring on purpose. Our service URLs live at the root for that reason — see WordPress, Laravel, and the rest of services.

Core Web Vitals on the templates people land on matter more than a perfect Lighthouse screenshot of /. Category and article templates are where we measure. We wrote about that for stores in Core Web Vitals for stores.

Next.js is not automatic SEO

You can still ship a Next.js site that is a client island with a pretty URL. You can still duplicate titles. You can still block crawling in robots.txt and then ask why nothing indexed. The framework helps when you use the render path. It does not replace an IA.

For this studio’s own marketing site we use a Laravel shell and React for the UI, with server-rendered meta and a sitemap. That is a valid pattern when the CMS and the app already live in Laravel. For a client who only needs a content site, WordPress is still the cheaper editor story.

How we choose on a brief

If editors must own pages: WordPress or a headless CMS with a server-rendered front. If the product is the app and marketing is a few routes: Next.js or Laravel views. If someone asks for “React, like a web app, but it must rank for twenty cities,” we slow the conversation down and pick URLs first. Book a call with the list of URLs, not a moodboard.