The #1 stack for complex React apps: SSR, App Router, Server Components. SEO-strong but requires precise configuration — one wrong dynamic rendering call nullifies everything. Next.js gives maximum SSR/SSG/ISR flexibility, but that flexibility is the main risk. On Next.js it's equally easy to build a perfectly SEO'd site or one Google can't see at all.
Per-page: SSG, ISR, SSR, dynamic. Wrong choice = no indexation.
Dynamic meta tag generation in App Router, unified via layout, correct canonical.
Proper split — RSC for content, client components only for interactivity. Minimum JS on page.
Revalidate strategies — every N minutes or on-demand. Google loves fresh content.
Dynamic generation via app/sitemap.ts with proper priorities and lastmod.
next/image and next/font — critical for LCP. Separate sizes for mobile and desktop.
One extra force-dynamic flag on homepage — Google stops caching and indexing.
Devs putting 'use client' on every component blows JS bundle to 2-3 MB, LCP drops 3x.
On /blog/[slug] pages without generateStaticParams — every request hits server, slow.
Half-migrated App Router — duplicate pages, meta tag conflicts, lost canonicals.
Middleware runs on EVERY request — even +50ms hurts TTFB.
fetch without proper cache config — every call is new. Edge cache doesn't work.
Per-page rendering mode: SSG, SSR, dynamic. Strategy map.
Vercel Analytics + PageSpeed measurements. Bottleneck identification.
Unified via layout, generateMetadata for dynamic, JSON-LD.
Dynamic app/sitemap.ts, robots.ts, correct alternates.
Client bundle optimization, dynamic imports, font/image optimization.
Google Indexing API for fresh content, Search Console, a report once a month.
This is the central question on any modern framework. Everything else — meta tags, markup, speed — is decided after it.
| Mode | What a crawler sees | When it fits |
|---|---|---|
| Static generation | Ready HTML with all content — the best case for indexing | Content changes rarely: services, articles, catalogues without frequent price updates |
| Server rendering | Ready HTML assembled per request | Data changes often: stock, prices, personalisation |
| Client rendering | An empty page; content appears after scripts run | Account areas and internal interfaces — things that should not be indexed anyway |
| Mixed mode | Depends on which part of the page ships immediately | Catalogues with static cards and dynamic blocks |
A common mistake is client rendering on pages meant to bring people from search. Easy check: open the page source and search for your own text. If it is not there, a crawler may not see it either.
On modern stacks, every SEO strategy starts with correct rendering and indexation. Nothing else works without it.
LCP, INP, CLS — the three metrics Google uses to grade real UX. SSG/SSR stacks make them easy to push into the green.
We work directly with your developers — fixing what SEO tools alone can't reach.
Not 'set it and forget it' — we watch indexation, speed and rankings continuously and send a report once a month.
30-minute call with a senior strategist. We'll review the codebase, indexation and Core Web Vitals — and propose a realistic plan.