Skip to main content

Next.js SEO

Technical SEO Checklist for a Next.js Website

A production-focused Next.js technical SEO checklist covering rendering, metadata, canonicals, sitemaps, schema, redirects, Core Web Vitals, and validation.

Published 24 October 2026

Direct answer

A technically sound Next.js website should serve important content in crawlable HTML, give every indexable page a unique title and canonical URL, return accurate status codes, publish a truthful sitemap, control robots directives, use relevant structured data, preserve URLs through redirects, and perform well on mobile devices.

Crawling and rendering

Render important content on the server
Service copy, article content, headings, links, and product information should be present in the initial HTML instead of appearing only after a client-side request.
Return meaningful status codes
Missing records should return a real 404, removed pages should redirect or return 410 when appropriate, and server failures should not masquerade as successful pages.
Keep public resources crawlable
Do not block JavaScript, CSS, images, or route data required to understand and render an indexable page.

Metadata and URL control

Use unique titles and descriptions
Each page should describe its specific intent. Avoid a title template that repeats the brand or makes every title too long.
Declare one canonical URL
Normalize protocol, hostname, trailing-slash policy, parameters, and case so alternate versions do not compete.
Maintain redirect chains
Redirect retired or renamed URLs directly to the closest replacement in one permanent hop and update internal links to the destination.

Sitemaps, schema, and internal links

Publish only canonical, indexable URLs
A sitemap should exclude admin pages, parameter variants, redirects, missing pages, and unpublished content. Modification dates should reflect real changes.
Use schema that matches visible content
Service, Article, Person, Organization, Breadcrumb, and FAQ markup should describe facts that visitors can also verify on the page.
Build descriptive internal links
Connect hubs, services, evidence, and supporting answers using anchors that explain the destination instead of repeatedly saying “learn more.”

Performance and verification

Optimize the real mobile experience: the main content image, fonts, JavaScript boundaries, third-party scripts, layout stability, and interaction responsiveness. A synthetic score is useful for diagnosis, but field data and actual user journeys matter more.

After deployment, inspect rendered HTML, test structured data, crawl the site, check Search Console coverage, and verify that analytics records the conversion paths that matter. Technical SEO is complete only when the production output matches the intended implementation.

Common questions

Is Next.js good for SEO?

Yes, when rendering, metadata, status codes, caching, canonicals, and routing are implemented correctly. Next.js provides strong primitives, but the framework does not automatically prevent thin content, duplicate intent, incorrect redirects, or misleading sitemap dates.

Does every Next.js page need structured data?

No. Add structured data only when a supported type accurately describes the visible page. Site-wide Person and Organization data, plus relevant Service, Article, Breadcrumb, or FAQ markup, is more useful than attaching unrelated schema everywhere.