RankpediaA plain-English encyclopedia of search

Next SEO

Configures a Next.js site so search engines can crawl, render, index, and understand its pages efficiently, covering rendering, metadata, and technical controls.

If you treat Next.js SEO as just adding a plugin, you miss the fundamentals of crawlability, indexable HTML, and canonical control.

Key points

  • Use server-side rendering or static generation to deliver indexable HTML.
  • Make every link a standard anchor tag so crawlers can follow it.
  • Set a canonical tag on every page that is reachable through multiple URLs.
  • Submit a sitemap to surface your most important URLs for crawl budget.
  • Block state-changing URLs like cart or checkout in robots.txt.

A multilingual Next.js store missing hreflang

A fashion retailer built a Next.js site with English, French, and German variants. Each product page existed at three URLs, but no hreflang tags were set. Google indexed the German version for English queries, and the French version appeared in German results. After adding hreflang and canonical tags, each language variant ranked in its correct market. Traffic from organic search rose 34% in three months.

Three ways it goes wrong

  • Client-only rendering Relying on client-side JavaScript alone leaves empty HTML for crawlers. Use getServerSideProps, getStaticProps, or the App Router's server components to deliver indexable content.
  • Missing canonical tags Parameterised URLs, filter pages, and trailing-slash variants create duplicates. Without a canonical tag, Google may index the wrong version or split ranking signals. This is a core part of canonical seo.
  • Blocked crawl paths Accidentally disallowing important pages in robots.txt or setting noindex on dynamic routes prevents discovery. Check your robots.txt and metadata for unintended blocks.

Three things to check before launch

  • Indexable HTML View the page source after a hard refresh. If the main content is missing, your rendering strategy is not producing HTML that search engines can parse.
  • Internal links Every page should be reachable through a standard anchor link from another page on the site. Orphan pages waste crawl budget and may never be indexed.
  • Sitemap coverage Your XML sitemap should list only canonical, indexable URLs. Exclude parameterised variants, pagination pages, and non-canonical versions to avoid wasting crawl budget.

Common questions

Does Next.js automatically handle SEO?

No. Next.js provides tools for rendering and metadata, but you must configure them correctly for crawlability and indexing.

Do I need a plugin for Next.js SEO?

Not necessarily. The built-in metadata API and next-sitemap can cover most needs. Plugins add convenience but are not required.

How does crawl budget affect Next.js sites?

Large sites with many dynamic routes can exhaust crawl budget. Use robots.txt to block low-value URLs and sitemaps to highlight important ones.

Sources

  1. Google Search Central: SEO Starter Guide Covers crawlability, indexing, and rendering fundamentals.
  2. Google Search Central: Crawling and indexing documentation Details on robots.txt, sitemaps, and crawl budget.
  3. Next.js Documentation Official guide to rendering, metadata, and routing in Next.js.
↑