Next.js SEO Audit Tool
Audit your Next.js deployment in 30 seconds. Find CSR-only meta tags, App Router metadata gaps, hydration-blocking scripts, and the LCP issues next/image misuse causes on hero sections.
No signup. No credit card. Works on any public Next.js site.
140+ checks
Meta, schema, Core Web Vitals, mobile, security — every Google ranking signal.
Lighthouse-accurate
Same engine Google uses in PageSpeed Insights. Real numbers, not approximations.
30-second scan
Parallel workers, no queue. Scan a 500-page site in under 3 minutes.
Copy-paste fixes
Every finding ships with the exact snippet — ready to paste into your CMS or codebase.
The 6 most common Next.js SEO issues
What we find on the average Next.js site within the first scan.
Meta tags only render client-side
useEffect-based head updates aren't visible to Googlebot's first render. We diff SSR HTML vs hydrated DOM.
Missing generateMetadata exports
App Router dynamic routes without generateMetadata fall back to layout metadata — losing per-page titles.
next/image fill without sizes
<Image fill /> without a sizes prop downloads the largest variant on every viewport. LCP drops by 1–3s.
No OG image generation
Routes without opengraph-image.tsx fall back to a default — losing social-share CTR.
Third-party scripts blocking hydration
Analytics and tag managers loaded with default strategy block INP. We flag candidates for next/script lazyOnload.
Sitemap missing dynamic routes
app/sitemap.ts that only includes static routes — dynamic /blog/[slug] paths get orphaned.
Why a Next.js-specific audit matters
- We render JavaScript like Googlebot does, so SSR vs CSR meta gaps actually surface (not silently hidden).
- Detects App Router vs Pages Router and tailors findings (generateMetadata vs Head, app/sitemap.ts vs getServerSideProps).
- Findings include framework-specific code snippets — generateMetadata exports, next/image sizes props, next/script strategies.
- Works on Vercel, Netlify, Cloudflare Pages, AWS Amplify, or self-hosted. Any public Next.js deployment.
How the audit works
Paste your deployed URL
We crawl the rendered HTML, hydrated DOM, and your /sitemap.xml.
Review Next.js-specific findings
Grouped by metadata, routing, performance, and hydration issues.
Apply code-level fixes
Each finding ships with a TypeScript snippet for generateMetadata, next/image props, or sitemap.ts.
Re-deploy and re-scan
Confirm the fix landed in production HTML before moving to the next issue.
Audit other platforms
SEO guides to pair with your audit
Run a Free SEO Audit in 5 Minutes (2026)
Step-by-step walkthrough for running a free SEO audit on any website — what to scan, how to read the report, and which fixes move the needle first.
Best Free SEO Audit Tools in 2026
We benchmarked 12 free SEO audit tools on accuracy, speed, and what they actually fix. Here's the shortlist that's worth your time.
The 2026 WordPress SEO Checklist
A practical WordPress SEO checklist covering technical setup, on-page, schema, and Core Web Vitals — with the exact plugin and fix for each item.
Next.js SEO audit — FAQ
Does this audit work for both App Router and Pages Router?▼
Yes. We detect which router you're using and tailor every finding — generateMetadata exports for App Router, Head component patterns for Pages Router.
Will it catch meta tags that only render after hydration?▼
Yes — that's one of the most common Next.js SEO bugs. We compare the SSR HTML against the hydrated DOM and flag any meta that only appears post-hydration. Googlebot won't see those.
Does it work for Next.js sites deployed to Vercel?▼
Yes — Vercel, Netlify, Cloudflare Pages, AWS Amplify, Fly, Render, or self-hosted. Any public Next.js URL works.
Can it audit ISR or on-demand revalidated pages?▼
Yes. We audit the live response, regardless of whether it's static, SSR, ISR, or on-demand. Findings reflect what Googlebot actually receives.
Does it suggest next/image and next/script fixes?▼
Yes. We flag <Image> usage missing sizes, priority, or quality props that hurt LCP, and <Script> usage that should be lazyOnload or worker strategy.
Will it catch sitemap.ts issues?▼
Yes — we fetch your /sitemap.xml, diff against discovered URLs, and flag dynamic routes that aren't included.
Stop guessing why your Next.js site isn't ranking.
Run a free Next.js-tailored audit in 30 seconds. No signup, no card.
Run Next.js audit