Next.js is a strong foundation for SEO: pages can be pre-rendered, metadata is easy to control, and performance tools are built in. But a Next.js site can still have serious SEO problems if these features are misused. Use this checklist when building or auditing a Next.js website.
Rendering
- Make sure important content is in the server-rendered or statically generated HTML, not loaded only in the browser.
- Use static generation for pages that rarely change and incremental regeneration for content that updates.
- Check pages with JavaScript disabled or by viewing the source to confirm content is present.
Metadata
- Unique title and meta description for every page, using the Metadata API.
- Canonical URLs on every indexable page.
- Open Graph and social metadata.
- Correct language and locale settings.
Crawling and Indexing
- Generate an XML sitemap that includes every indexable page.
- Provide a robots.txt that allows crawling of important sections.
- Use noindex for thin, duplicate or private pages.
- Avoid accidental noindex on production from staging settings.
- Ensure dynamic routes are discoverable through internal links and the sitemap.
URLs and Redirects
- Clean, descriptive, lowercase URLs.
- Consistent trailing slash and www settings.
- Permanent redirects for moved pages.
- Proper 404 pages that return a 404 status.
Structured Data
- Add JSON-LD for Organization, WebSite, BreadcrumbList and content types such as BlogPosting, Product or Service where they reflect the page.
- Validate with Google's Rich Results Test.
- Only mark up content that is visible on the page.
Performance
- Optimise images with responsive sizes and modern formats.
- Load fonts efficiently to avoid layout shifts.
- Keep client-side JavaScript lean; use server components where possible.
- Lazy-load below-the-fold content.
- Measure Core Web Vitals with field data, not just lab tests.
Internal Linking
- Link related pages with descriptive anchor text.
- Use breadcrumbs.
- Avoid orphan pages with no internal links.
Content
- One clear H1 per page.
- Logical heading structure.
- Alt text for meaningful images.
"Next.js gives you the tools for great SEO. The checklist makes sure you use them."
Monitoring
- Verify the site in Google Search Console.
- Review indexing reports regularly.
- Monitor Core Web Vitals.
- Fix crawl errors promptly.
Common Questions
Is client-side rendering bad for SEO? Search engines can render JavaScript, but rendering may be delayed and content may be missed. Server-side rendering or static generation for important content is more reliable and also faster for users.
How should multilingual Next.js sites be handled? Use separate URLs for each language, add hreflang annotations, translate metadata and keep sitemaps updated for each language version.
Should every page be in the sitemap? Include only canonical, indexable pages that you want in search results. Exclude redirects, noindex pages, filtered duplicates and private areas.
How do we check what Google sees? Use the URL Inspection tool in Google Search Console to see the rendered HTML and indexing status, and fix any differences between what users and search engines see.
How ITELLIC Helps
We build websites with Next.js and audit existing ones for technical SEO, fixing rendering, metadata, indexing and performance issues.
SEO & Growth Hacking
More qualified visitors, more enquiries.
