The Next.js SEO Checklist for 2026
A complete, up-to-date SEO checklist for Next.js App Router projects in 2026 — metadata, sitemaps, robots, structured data, Core Web Vitals, and rendering strategy.
Next.js is one of the best frameworks for SEO, but only if you use its features correctly. Here is the checklist I run through on every App Router project in 2026.
1. Metadata
Export a metadata object from your layout and pages, or use generateMetadata for dynamic routes. Set a unique title and description per page, a canonical URL via alternates, and Open Graph plus Twitter card tags for shareability.
2. Sitemap and robots
Add app/sitemap.ts to list every indexable URL and app/robots.ts to control crawler access. Point robots at your sitemap and explicitly allow AI crawlers if you want generative engines to use your content.
3. Rendering strategy
Serve primary content as server-rendered HTML. If your headline, body, and links only exist after client-side hydration, crawlers and AI engines may miss them entirely.
4. Structured data
Add JSON-LD for the entities on each page — Article for posts, Person for an about page, BreadcrumbList for navigation. This is the difference between a page that is read and a page that is understood.
5. Core Web Vitals
- Use next/image for automatic responsive images and lazy loading.
- Load fonts with next/font to avoid layout shift.
- Keep JavaScript bundles lean and defer non-critical work.
- Aim for green LCP, INP, and CLS scores in field data.
Conclusion
SEO in Next.js is a checklist, not magic. Metadata, sitemaps, robots, server rendering, structured data, and fast Core Web Vitals together make a site that both search engines and AI answer engines love.
Frequently asked questions
Does Next.js handle SEO automatically?
Next.js gives you the tools — the Metadata API, file-based sitemap.ts and robots.ts, server rendering, and next/image — but you still need to configure titles, descriptions, canonical URLs, and structured data yourself.
Should I use static or server rendering for SEO?
Both work for SEO as long as the content is in the initial HTML. Static generation is fastest; server rendering is best for frequently changing content. Avoid client-only rendering for primary content.