Server Components: what actually changes for SEO
For a decade, single-page applications asked crawlers to execute JavaScript before they could see any content. Search engines learned to cope, imperfectly. Server Components change the default back: content is in the HTML again.
That is a real improvement, but it is not automatic, and it does not make every other SEO decision irrelevant.
What genuinely changes
With Server Components, the markup for your headings, body copy, lists and links exists in the initial response. A crawler that never runs JavaScript still sees the page. AI search engines, which are far less patient with client-side rendering than Google is, see it too.
The second change is bundle size. Content that never becomes interactive no longer ships as JavaScript, which improves Interaction to Next Paint and reduces the work a low-end phone has to do.
What does not change
Structured data still has to be emitted deliberately. Canonical URLs still have to be correct. Headings still need a sane hierarchy with exactly one h1. Content still has to answer the question the searcher actually asked.
Server rendering removes an obstacle. It does not supply the substance.
Where to draw the client boundary
The useful rule is to push Client Components as far down the tree as possible. A page can be a Server Component that renders mostly static sections and one small interactive island — a carousel, a form, a tab set.
When a section is marked as a Client Component only because of a single click handler, the whole subtree becomes client-rendered and its content leaves the initial HTML unnecessarily.
- Static marketing copy, FAQs and course descriptions: Server Components
- Carousels, forms, tabs and accordions: Client Components, kept small
- Prefer `details`/`summary` over a JavaScript accordion when you only need expand and collapse
Writing for generative engines
AI assistants quote pages that state facts plainly. Short paragraphs, explicit entity names, and a heading that matches the question all make a page easier to quote correctly.
On this site, for example, every page names "Wisen IT Solutions, Chennai" in full at least once, so an assistant summarising the page does not have to guess which Wisen is meant.
