The deployed response is the evidence.
Framework settings and builder dashboards are inputs; the final status, redirect, HTML, canonical, sitemap, and rendered page determine what a crawler can process.
Trace the Finding from Route Output to Owning File.
Check metadata, rendering, discovery files, and statuses on the deployment users and crawlers receive.
Turn one verified production finding into a focused implementation task.
Open the SEO Workspace
Quick Answer
Check the production Next.js site for route-specific Metadata API output, canonical URLs, robots and sitemap metadata files, initial and rendered content, server and client component boundaries, direct-route status codes, redirects, not-found behavior, structured data, internal links, Open Graph images, and performance evidence. Test representative dynamic routes and cache states. A correct local `next build` is necessary evidence, but the final host and runtime can still change redirects, headers, rendering, and errors.
AI Summary
This developer checker covers current Next.js App Router metadata conventions and observable production behavior while remaining useful for older or mixed applications through direct HTML, header, and route inspection.
Fix dependencies before symptoms.
Resolve public access, index controls, canonical conflicts, and missing source content before polishing schema or expanding the content inventory.
One focused workspace
Stop jumping between tools.
Stop jumping between tools.
Keep the workflow in one place.
Audit, AI visibility, research, content optimization, and reporting-organized around the website you are improving.
ReplacesWhat you getOther tools
TruboRankAI
TruboRankAIEverything above vs TruboRankAI - one subscription$755+/mo$19.99/moSave ~97%
Third-party names and logos are trademarks of their owners and are shown for comparison. Other-tool prices are illustrative monthly benchmarks; exact plans and costs may vary.
Production SEO diagnostics
Audit route metadata and rendering without guessing from source code
Inspect the live surface, identify its owner, implement the smallest correction, and verify the release.
What the Next.js SEO checker inspects
Sample static, dynamic, nested, parameterized, redirected, and missing routes. Inspect the initial response head and body, then compare the rendered page. Verify that static metadata or `generateMetadata` produces a unique title, description, canonical, robots directive, and social image where appropriate. Check that metadata derives from approved data and does not fail silently when a record is missing.
Review `robots.txt`, `sitemap.xml`, icons, and social images generated through file conventions or custom route handlers. Next.js documents static and programmatic metadata files; confirm their production URL, content type, cache behavior, hostnames, and route inventory. Large dynamic applications may need split sitemaps and explicit exclusion of private or noncanonical routes.
Test status and streaming behavior. Use framework-supported redirects and not-found handling, inspect the final response, and ensure the user-visible result matches the semantic status. Keep essential public answers in server-visible output where practical, validate structured data in rendered HTML, and avoid making priority links dependent on an interaction that crawlers may not perform.
Review public and private route boundaries before changing discovery controls. Useful acquisition, documentation, support, and policy routes may be indexable. Account, dashboard, billing, checkout, API, webhook, admin, preview, staging, and user-data routes should stay protected and absent from public sitemaps. robots.txt is not access control.
Map the highest-impact failure to the layer that owns it: route, layout, component, CMS record, metadata generator, sitemap builder, robots output, hosting rule, CDN, or domain configuration. Preserve unrelated behavior, define the acceptance test, implement the smallest correction, publish, and repeat the exact production request.
Use Search Console, crawler logs, analytics, and AI visibility observations for their separate questions. A clean technical check improves eligibility and diagnosis; it does not promise indexing, ranking, citation, referral traffic, or conversion. Keep dates and tested URLs with every later observation so changes can be interpreted honestly.
Frequently asked questions
Does Next.js handle SEO automatically?
It provides metadata, rendering, sitemap, robots, and routing primitives; the project still must implement accurate route-specific output.
Should metadata use a client component?
Current Next.js metadata exports are supported in server components; follow the documentation for the application version.
Does streaming metadata hurt SEO?
Next.js documents bot-aware handling, but verify the production response for the crawlers and routes that matter.