Guides
Next.js SEO Checklist
A practical DomainLens guide to Next.js SEO Checklist, focused on SSR vs SSG, metadata API, dynamic routes, sitemap generation.
Run a fresh DomainLens audit and use the report as your priority list.
Overview
Next.js SEO Checklist is useful when you need a clear way to separate cosmetic SEO work from issues that can block crawling, indexing, rankings, or search snippets. Start with evidence, then decide what deserves engineering time.
Use an automated audit to collect the baseline, then review the page manually for context, search intent, and business priority.
Why it matters
The most common problems usually sit around SSR vs SSG, metadata API, dynamic routes, sitemap generation. These signals influence how easily search engines discover pages, understand content, and trust the final URL they should rank.
A good SEO workflow turns these checks into a short fix list with owner, impact, effort, and validation steps.
What to check
- Review SSR vs SSG and record the current state, expected state, and exact URL affected.
- Review metadata API and record the current state, expected state, and exact URL affected.
- Review dynamic routes and record the current state, expected state, and exact URL affected.
- Review sitemap generation and record the current state, expected state, and exact URL affected.
Common mistakes
- Fixing SSR vs SSG without validating the rendered page, canonical target, and indexability after deployment.
- Fixing metadata API without validating the rendered page, canonical target, and indexability after deployment.
- Fixing dynamic routes without validating the rendered page, canonical target, and indexability after deployment.
- Fixing sitemap generation without validating the rendered page, canonical target, and indexability after deployment.
Next step
Run a fresh DomainLens audit, compare the report with this guide, and prioritize fixes that affect indexability, snippets, internal linking, or Core Web Vitals first.