Next.js SEO audit

Data fetched in useEffect or behind a loading state is absent from the HTML response. CrawlX crawls both the raw response and the rendered DOM (Professional and above) and flags pages whose headings, body text or metadata appear only after JavaScript runs.

Navigation built with onClick handlers and router.push on non-anchor elements produces no href for a crawler to follow. CrawlX reports pages that are only reachable through rendered links and orphan pages that the raw HTML never links to.

Route segments without a metadata or generateMetadata export inherit the layout's default, so many pages share one title and description. CrawlX reports missing, duplicate and over-length titles and descriptions and groups them by route pattern.

A trailingSlash setting that disagrees with internal links, plus redirects in next.config stacked on hosting-level rules, creates chains and 308 loops. CrawlX follows every redirect, reports hop count and final status, and lists the internal links that trigger them.

Canonical and Open Graph URLs built without metadataBase come out relative, and pages regenerated on a long revalidate window can keep an old canonical after a domain or path change. CrawlX validates every canonical for absoluteness, self-reference and cross-domain targets.

A dynamic route that renders an empty state instead of calling notFound() returns 200 for URLs that do not exist. CrawlX detects thin pages returning 200 on parameterised routes and reports them as soft 404 candidates.

Images outside next/image, missing sizes attributes, or the LCP image without priority all show up in the rendered page. CrawlX reports oversized and unsized images and, on Professional and above, measures Core Web Vitals in a real browser.

Search and filter pages that put state in query strings, and routes reachable in more than one casing, multiply indexable URLs. CrawlX groups parameter variants and case variants and reports which are canonicalised.