Here’s a frustrating situation. The site is beautiful, looks fast, built on a modern framework — and in search it’s as if it doesn’t exist. The reason is often not the text and not the links, but one technical fork nobody usually tells the client about: where exactly the page gets assembled — on the server, or already in the user’s browser.
Two pages that look identical
Imagine two sites, indistinguishable from the outside.
The first sends a finished page: the server assembled the HTML with text, headings, and links — and handed it over whole. You open it, everything’s already in place.
The second sends an almost empty shell and a program that will draw the content in, already inside the browser. A person barely notices the difference — waits a fraction of a second and it all appears. But a search bot may look in at exactly the moment the empty shell arrived and the scripts haven’t run yet — and see emptiness.
That’s the difference between server-side and client-side rendering. To the eye it’s almost nothing. To search it’s decisive.
Why it hits SEO specifically
A bot can be impatient. It doesn’t always wait for the browser code to finish; on large sites it has a limit of time and effort per page. If the content only appears after the scripts run, some pages it will take half-empty, and some it won’t take at all. The text seems to be there — but for search it might as well not be.
With server-side rendering this lottery doesn’t exist. What’s on the page is what the bot got — in the very first second, no «hold on, still drawing». You don’t depend on when, and with how much patience, it looked in.
«But everyone runs SPAs, and they get by»
They get by — because the big ones learned to fix it. They re-render pages on the server, hand the bot finished HTML, and layer the interactivity on top. That is, they don’t ignore the problem, they solve it — with that same server-side rendering or pre-rendering, just under the hood, invisibly.
Trouble comes when the trendy frontend gets adopted and this part gets forgotten. Then you get exactly this: beautiful for the human, blank for search. And it doesn’t surface right away — it shows up a couple of months later, when the pages still haven’t appeared in the results and the cause is hunted for anywhere but there.
What to do about it
If the site is only being planned — build in server-side rendering from the start. It’s cheaper than fixing it later. That’s why we build sites so the page arrives ready: the bot gets full HTML, and speed and interactivity don’t suffer for it — one doesn’t get in the way of the other if you think about it at the start.
If the site already exists and a suspicion has crept in — checking is simple, with your own hands. Open a page, turn off JavaScript in the browser, and reload. Content still there — you’re fine. Blank — search sees exactly the same thing, and that’s a reason to call in someone who handles the technical side of SEO before the un-indexed pages pile up.
A pretty picture and visibility in search are not the same thing. It’s a shame to invest in the first and lose the second for no reason — over a fork you can only see under the hood.