Blinks's avatar

Inertia for heavily SEO application

Hello everyone!

Our company has raised the issue of creating a new portal that will rely heavily on SEO. One of the suggested options is Laravel + Next.js or Laravel+ Inertia + React. Regarding Inertia, no one has any experience working with it, so we asked Chatgpt to conduct research on the possibility of using Inertia for SEO, and he replied that it is better to use Laravel + Next.js, because:

  • Inertia has many well-known problems with SSR
  • he uses knowledge mainly on Inertia v0-v1
  • Inertia has a lot of problems with hydration mismatch
  • it is difficult to synchronize client props with server ones
  • it is difficult to set up ssr deployment of an application in Kubernetes

What do you think about Inertia and SEO apps? Has anyone created something like this and will dispel doubts about Inertia? Or is it really better to use Laravel + Next.js ?

0 likes
4 replies
JussiMannisto's avatar

we asked Chatgpt to conduct research

There's your first mistake.

Inertia has many well-known problems with SSR

No.

Inertia has a lot of problems with hydration mismatch

No. Unless you misconfigure it.

it is difficult to synchronize client props with server ones

???

it is difficult to set up ssr deployment of an application in Kubernetes

???

ChatGPT composes nonsense about any topic if you ask it to. Those bullet points are worthless because they don't explain anything.

Inertia is just a wire protocol between the Laravel backend and an SPA front end. You can set up SSR if you think it's worthwhile. Inertia isn't better or worse for SEO than any other app. SEO isn't a matter of tech stack, but of content and performance.

I'd always go with Inertia. It's less complicated than using Laravel as a backend API. You use server-side routing, get sessions and CSRF protection for free, etc. From an SEO perspective, there's no difference.

DigitalArtisan's avatar

Its 2026 now, that article is OLD.

Here is a current AI response:

Laravel + Next.js vs Laravel + Inertia + React for SEO

1. Laravel + Next.js

Pros:

  • Server-Side Rendering (SSR): Next.js renders pages on the server before sending them to the browser, which is great for SEO.
  • SEO Optimized: Built-in features like image optimization, fast page loads, and prefetching help with SEO.
  • Static Site Generation (SSG): You can generate static pages, improving performance and SEO.

Cons:

  • More Complex: Managing both Laravel and Next.js can be tricky. You'll need separate setups and integration.
  • API Management: You'll need to set up APIs for Laravel to serve data to Next.js.

2. Laravel + Inertia + React

Pros:

  • Simple Integration: Keeps everything within Laravel, no need for a separate front-end framework.
  • Server-side Rendering: You can still use Laravel to serve initial HTML, making it SEO-friendly.

Cons:

  • Client-Side Rendering (CSR): By default, Inertia uses React on the client-side, which can be problematic for SEO if not handled correctly.
  • Manual SEO Work: You may need additional tools like React Helmet or implement SSR manually for optimal SEO.

Conclusion:

  • For better SEO out of the box: Go with Laravel + Next.js. It has built-in SSR and other SEO optimizations.
  • For simplicity: Laravel + Inertia + React works if you don't mind handling SEO optimization yourself, but it might require more effort to get it right.

Please or to participate in this conversation.