Next.js SEO Checklist

Quick answer

Next.js SEO comes down to four things: pages render as crawlable HTML (SSR/SSG, not client-only), metadata is correct per page (title, description, canonical), Core Web Vitals pass (fast load, stable layout, responsive input), and a sitemap plus robots.txt tell crawlers what to index. Miss any one of these and the framework’s SEO advantages do not show up in results.

Rendering strategy: make sure crawlers see real content

Next.js’s SEO advantage comes from server-side rendering or static generation — pages that arrive as real HTML rather than an empty shell that JavaScript fills in later. If a page that needs to rank is rendered client-side only, you are giving up the main reason to choose Next.js in the first place.

Check this directly: view page source (not the rendered DOM) for any page you expect to rank, and confirm the actual content — not just a loading skeleton — is present in the raw HTML response.

Metadata checklist per page

Every page that should rank needs its own accurate metadata — not a site-wide default copied everywhere.

• Unique title tag per page, under ~60 characters
• Unique meta description per page, roughly 140–155 characters
• Canonical URL set correctly (especially for pages reachable via multiple paths)
• Open Graph and Twitter card tags for social sharing previews
• Structured data (JSON-LD) where it matches the actual page content — never fabricated

Core Web Vitals basics

Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) affect both user experience and ranking signals. Common Next.js-specific wins: use the built-in Image component for automatic optimization, avoid render-blocking fonts without a fallback, and reserve space for images/ads so layout does not shift after load.

Sitemap, robots, and indexing basics

Generate a sitemap.xml that lists only canonical, indexable URLs — not every internal route. Make sure robots.txt is not accidentally blocking pages you want crawled (a common mistake after moving from a staging environment to production). Submit the sitemap in Search Console and Bing Webmaster Tools after launch, then request indexing for your most important pages manually if you need faster coverage.

Common mistakes

Shipping a client-only rendered page that needs to rank and wondering why it never shows up in search. Copying the same title/description across every page. Ignoring Core Web Vitals until a Lighthouse audit flags them post-launch. Forgetting to update robots.txt after moving from staging to production, accidentally blocking the whole site.