Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hello all, hope all of you are fine.
I have a question that is on my mind the last weeks, so I want to get it clear.
I love Inertia.js development, I also love it's SPA functionality (who doesn't love it? it makes browsing a web application PERFECT)
Now that Inertia.js published it's SSR functionality I want to ask this:
How it is compared on SEO with a old application with Blade? Do they even compared? Is it similar? Is it worst? Is it better?
For example would it be suitable for E-commerce websites | blogs that are highly depended on SEO?
I really need to know, because developing apps on inertia would be a game changing for me.
Actually:
Inertia on front end (Perfect User Experience) Livewire on back end (Quicky & easy)
What you think of that?
Thank you very much
Inertia SSR return plain html in the first request this is,
view-source:https://ssr-demo.inertiajs.com/login
then, it will change to SPA mode from the second request onward.
For SEO, when bots grab the link they always make first request so, they always get plain html.
I think we can say that for SEO, inertia SSR is the same with SSR websites.
https://laracasts.com/browse/all why we can see html in page source as in your provided exmaple?
It's because of `data-server-rendered="true" yes?
Thank you for your answer @koramit
Waiting for more opinions on this.
Is the SEO the same with old SSR apps using Blade?
If yes, how do you find this stack with Inertia? It can be awesome, don't you think?
SPA + SEO
@georlioy SEO is tied to the URL, so basically if the search engines read/index your URL and get different page content each time they search, you lose ground, if they only ever get to see the same content, then your other content never gets seen and is of no SEO value.
I've not used SPA in those sorts of circumstances, but in the example of a blog, unless SSR can give you a unique URL that can be reached and indexed by a search engine then it is basically useless for SEO.
@chiefguru thank you for your answer too. Looking for someone that knows SSR to give a legit answer though, hope someone can give us his lights
Hey, creator of Inertia.js here. The answers from @koramit and @chiefguru are exactly right. Using Inertia.js SSR will be exactly the same as rendering pages using Blade, since both provide the same HTML, which is all search engines care about.
thank you!!! thanks for the perfect package too ^^
You should mark one answer as best, because you got an answer :)
Done. thank you :)
Hey @reinink! It's been six month since you wrote your answer here and coincidentally Inertia's SSR has just been released for Laravel. Following up the discussion, after the implementation of Inertia's SSR, would you say that keeping on using Blade — at least for those who make use of Inertia.js and were still attached to Blade (which I personally like a lot) for pages where SEO is highly relevant — has become a matter of simple preference and/or lack of need for a SPA-like front-end feeling? So far I have kept some blade views in my project (usually non-authenticated area) either because of SEO or because app-like reactivity wasn't really a must, but now with Inertia's SSR this may well be a farewell to Blade. I have to highlight that I'm not underestimating Blade, it just seems to me that from now on it's all about preference instead of need. I may have missed something in my considerations, of course. Cheers and thanks for the great job!
Your approach of using Inertia.js on the frontend and Livewire on the backend sounds like a promising combination for creating dynamic web applications with excellent user experiences and strong SEO capabilities.
Please or to participate in this conversation.