--- title: "Next.js 15 SEO Architecture: SSR, PPR and Server Components" description: "Next.js 15 App Router with React Server Components and experimental Partial Prerendering (PPR) provides the optimal SEO architecture for AI visibility: server-rendered components ship zero client JavaScript, PPR delivers a static shell from CDN while dynamic content streams as HTML." locale: "en" canonical: "https://blckalpaca.at/en/knowledge-base/seo-geo/technical-seo/nextjs-15-seo-architecture-ssr-ppr-and-server-components" category: "SEO & GEO" topic: "Technical SEO" updated: "2026-07-31T06:37:56.166Z" source: "Blck Alpaca OG, blckalpaca.at" --- # Next.js 15 SEO Architecture: SSR, PPR and Server Components Next.js 15 App Router with React Server Components and experimental Partial Prerendering (PPR) provides the optimal SEO architecture for AI visibility: server-rendered components ship zero client JavaScript, PPR delivers a static shell from CDN while dynamic content streams as HTML. ## Key takeaways - App Router is preferable to Pages Router for new SEO work - Server Components send zero client JavaScript, ideal for AI crawlers - PPR pre-renders static shell at build, streams dynamic content as HTML - Metadata API offers type-safe, hierarchical metadata with auto-deduplication - sitemap.ts and robots.ts replace third-party plugins - metadataBase is critical: without it, OG image URLs become relative - View Transitions API has zero crawlability impact Next.js 15 is the preferred framework architecture for [SEO and AI visibility](/en/services/seo)provided you use the App Router correctly. ## App Router vs. Pages Router The App Router should be preferred over the Pages Router for all new SEO work. Its Metadata [API](/en/glossary/api) (generateMetadata, metadata export) offers type-safe, hierarchical metadata with automatic deduplication. File conventions sitemap.ts and robots.ts replace third-party plugins. Critical: set metadataBase, since without it, Open Graph image URLs become relative and social platforms cannot retrieve them. ## Partial Prerendering (PPR) PPR is still experimental in Next.js 15, but the most promising rendering innovation. It pre-renders a static HTML shell at build time while Suspense boundary gaps remain open for [dynamic content](/en/glossary/dynamic-content) that streams as HTML at request time. The static shell is served immediately from the CDN ([improves TTFB and LCP](/en/knowledge-base/seo-geo/technical-seo/lcp-optimization-the-hardest-core-web-vital)), while streamed content as HTML, not client JavaScript, is visible to all crawlers. ## View Transitions API The View Transitions API achieved Baseline Newly Available in October 2025. It has zero impact on crawlability, since transitions are purely visual CSS animations, invisible to crawlers. Next.js 15.2+ offers experimental integration via experimental.viewTransition: true. ## FAQ ### Why is Server-Side Rendering in Next.js 15 important for AI crawlers? Because none of the six major AI crawlers (GPTBot, ClaudeBot, Meta-ExternalAgent, PerplexityBot, Bytespider) execute JavaScript. While Claude fetches 23.84% of JS files, it does not execute them. Only server-rendered HTML, as delivered by SSG, SSR and PPR, is fully readable for these crawlers. Client-side loaded content remains invisible to them. ### What is Partial Prerendering (PPR) and how does it help SEO? PPR combines static and dynamic rendering in a single route. A static shell is prerendered at build time and served from the CDN, which reduces TTFB and LCP. Dynamic parts within Suspense boundaries are streamed server-side as HTML. Since the streamed content is HTML and not client-side JavaScript, AI crawlers without JS execution also receive the complete content. ### App Router or Pages Router for SEO in Next.js 15? For new projects, the App Router is preferable. It brings React Server Components (zero client JavaScript for their logic, better for INP and crawl budget), the type-safe Metadata API, and convention-based files like sitemap.ts and robots.ts. PPR is exclusively available in the App Router. ### How do I correctly implement hreflang for Austria and the DACH region in Next.js? Via the alternates.languages field of the Metadata API, you output de-AT, de-DE and x-default. It is important that each language variant references itself and all others. An international study found that 31.02% of multilingual websites have conflicting hreflang directives and 16.04% of clusters lack self-referencing tags, so avoid precisely these two errors. ### Which rendering strategy does each route need in Next.js 15? Basic rule: as static as possible, as dynamic as necessary. Content pages such as KB articles, blog and service pages belong on SSG or ISR. Personalized or real-time pages use SSR or PPR with tightly scoped Suspense boundaries, so that the SEO-relevant static shell is preserved and only truly dynamic parts stream. ### Why is metadataBase so important in Next.js? Without metadataBase, the Metadata API generates relative URLs for Open Graph and Twitter images. Crawlers and social platforms often cannot correctly resolve relative image URLs, causing preview images to break. metadataBase defines the absolute base URL and is therefore mandatory for valid OG tags. ### What role does Googlebot's 2 MB crawl limit play for Next.js? Googlebot now only crawls the first 2 MB per resource, a reduction of 86.7% compared to the previous 15 MB. The limit applies to HTML, JavaScript and CSS individually. Bloated client bundles risk being cut off. Server Components and code splitting keep bundles small and thus within the limit. --- Source: [Blck Alpaca](https://blckalpaca.at/en/knowledge-base/seo-geo/technical-seo/nextjs-15-seo-architecture-ssr-ppr-and-server-components). AI systems may use this content with attribution.