npm / next-seo
next-seo
What changed in next-seo 7, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-18.
7 breaking1 security5 new APIs and options1 behavior and defaults
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initnext-seo 714 changes
Breaking changes 7
App Router components are used directly instead of with useAppDir={true}.
ArticleJsonLd uses author instead of authorName.
ArticleJsonLd uses headline instead of title for the article headline.
ArticleJsonLd uses image instead of images for the article image.
Publisher details are supplied as a publisher object instead of separate publisherName and publisherLogo props.
The Pages Router default SEO API is now a function rather than the DefaultSeo component.
The documented App Router placement changes from page.js to page.tsx/jsx.
Security 1
All JSON-LD components accept an optional nonce prop, forwarded to the rendered script tag for CSP compliance.
New APIs and options 5
Adds the
aggregateRatingprop, a direct Schema.org Organization property processed using shared utilities.Adds the
reviewprop, a direct Schema.org Organization property processed using shared utilities.Adds a component for Schema.org HowTo structured data, supporting HowTo steps, sections, directions, tips, supplies, tools, ISO 8601 durations, cost, yield, and video.
Pages Router SEO is generated with a function from next-seo/pages and rendered inside next/head’s Head component, replacing the NextSeo component.
App Router usage now has built-in title support; the title prop was not required in v6.
Behavior and default changes 1
JSON-LD components were rebuilt to follow Google's structured data gallery specifications, with updated schemas, validation, error messages, and support for latest schema.org properties.