From reading to action
A practical path through this guide.
Select a step to explore what to do and why it matters.
Inspect public responses
Check useful page content and correct missing-route behavior.
A Next.js technical SEO review should inspect the rendered response, metadata, crawl controls, and generated discovery routes. A page that looks correct in the browser can still publish the wrong canonical URL or disappear from the sitemap when CMS data changes.
Inspect the public response
Choose a homepage, a blog listing, an article, and a missing route. Confirm meaningful content is available through the intended rendering strategy and that a missing article returns the correct not-found behavior. Check production-like builds because development behavior can differ.
Verify titles and descriptions against the CMS fields and fallback rules. An empty manual SEO field should not erase a useful default. Use the public hostname for canonical and social URLs, particularly when preview environments have their own domains.
Keep indexing signals consistent
Inspect robots directives, canonical links, redirects, and sitemap membership together. A page intended for indexing should not accidentally inherit a noindex setting from a preview template. A filtered listing may deliberately use different indexing rules from the main blog.
Define the handling of trailing slashes, alternate hostnames, and old slugs. Redirect retired URLs when there is a relevant replacement. Avoid redirecting every missing article to the homepage, which obscures the actual state for users and crawlers.
Verify generated content routes
- The sitemap contains canonical published article URLs.
- Robots rules allow intended public routes and protect private areas appropriately.
- Social metadata uses absolute usable image URLs.
- Article structured data matches visible content and dates.
- Any LLM-readable files reflect the same current services and articles.
These files should consume a consistent content set. If a CMS query returns only managed posts while local articles remain publicly accessible, the sitemap can omit valid pages. Test both configured and unconfigured CMS behavior.
Review publishing changes
Edit one test article, trigger the intended revalidation flow, and confirm the title, body, listing, and machine-readable routes update coherently. Check the old slug if it changed. A successful webhook response does not prove all cached views refreshed.
Use search performance data after deployment to assess impressions and queries. Technical correctness enables discovery but does not guarantee a particular ranking. The next content decision should follow evidence about the audience rather than a promise that framework settings alone will win search results.
Further reading
Use Next.js metadata documentation for implementation details and Google's SEO starter guide for search fundamentals.
A few practical answers
Frequently asked questions
Which Next.js routes should a technical SEO spot check include?
Inspect the homepage, blog listing, article and an unknown route. Check rendered content, indexing signals, navigation and whether a missing article returns the intended 404.
Why should generated routes be checked after a publishing change?
The article, listing, sitemap and generated text routes may use different queries or caches. A current article page alone does not prove discovery routes updated coherently.
