Mastering Next.js SEO: Schema Markup, Core Web Vitals, and Technical Audits
A complete technical SEO guide for Next.js applications — from structured data implementation to Core Web Vitals optimization and the technical audits that uncover ranking-impacting issues.
By POINTNEXIS Team
Next.js is an excellent SEO platform — server-side rendering, static generation, and the App Router's metadata API give you fine-grained control over everything Google reads. But good technical infrastructure alone does not guarantee rankings.
This guide covers the implementation details that separate well-ranking Next.js sites from ones that technically 'should' rank but do not.
Metadata and Open Graph with generateMetadata
The App Router's `generateMetadata` function exports typed metadata per route, including title templates, canonical URLs, Open Graph images, and robots directives. Use the `title.template` in your root layout to ensure every page gets `Page Title | Brand Name` formatting without repetition.
Generate unique, descriptive titles and meta descriptions per page — not boilerplate. Pages with thin or duplicate metadata consistently underperform regardless of content quality.
Structured Data (Schema.org) Implementation
Inject JSON-LD structured data via a `<script type='application/ld+json'>` tag inside your Server Components. Common schemas: `Organization` on the homepage, `BlogPosting` on articles, `FAQPage` on FAQ sections, `LocalBusiness` for service businesses, and `BreadcrumbList` for navigation.
Use Google's Rich Results Test to validate your markup before deploying. Schema errors silently fail — Google ignores malformed JSON-LD rather than surfacing parse errors in Search Console.
Core Web Vitals: LCP, INP, and CLS
Largest Contentful Paint (LCP) is most often the hero image. Use `priority` on the above-the-fold Next.js `<Image>` component, serve images from a CDN with proper `Cache-Control` headers, and preload the LCP resource with `<link rel='preload'>` if it is not server-rendered.
Interaction to Next Paint (INP) measures responsiveness. Long Tasks over 50ms on the main thread degrade INP. Defer non-critical JavaScript, use `startTransition` for non-urgent state updates, and move heavy computations to Web Workers. Cumulative Layout Shift is fixed by always reserving space for images and dynamic content with explicit `width` and `height` attributes.
Technical Audit Checklist
Run Lighthouse and PageSpeed Insights on mobile, not just desktop — mobile scores are the ones that affect rankings. Audit: canonical URLs on every indexable page, sitemap.xml with correct lastmod dates, robots.txt that does not accidentally block important paths, and 301 redirects for all moved or removed pages.
POINTNEXIS ships every web project with SEO instrumentation pre-built: canonical tags, sitemap generation, schema markup, and a Lighthouse CI budget that fails the build if Core Web Vitals drop below thresholds.