Skip to content

Comments

fix: update dependency next-seo to v7 (main-private)#541

Open
renovate[bot] wants to merge 1 commit intomain-privatefrom
renovate/main-private-next-seo-7.x
Open

fix: update dependency next-seo to v7 (main-private)#541
renovate[bot] wants to merge 1 commit intomain-privatefrom
renovate/main-private-next-seo-7.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 21, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
next-seo 5.15.0 → 7.2.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

garmeeh/next-seo (next-seo)

v7.2.0

Compare Source

Minor Changes
  • 28c684e: Add review and aggregateRating props to OrganizationJsonLd component, matching the existing support in LocalBusinessJsonLd. Both are direct Schema.org Organization properties processed using shared utilities.

v7.1.0

Compare Source

Minor Changes
  • d412e2b: Add HowToJsonLd component for structured data support
    • New HowToJsonLd component following Schema.org HowTo specification
    • Support for HowToStep, HowToSection, HowToDirection, and HowToTip types
    • HowToSupply and HowToTool for materials and equipment
    • Duration properties (prepTime, performTime, totalTime) in ISO 8601 format
    • estimatedCost as string or MonetaryAmount object
    • yield as string or QuantitativeValue
    • Video support via VideoObject

v7.0.1

Patch Changes
  • 1db3648: Add JSDoc comment to internal type guard function

v7.0.0

Next SEO v7.0.0 Release Notes

🚨 Important Notice

Next SEO v7 is a complete rewrite with breaking changes throughout the entire API.

We strongly recommend staying on v6 unless you:

  • Need the new JSON-LD components based on Google's latest specifications
  • Are starting a new project and want to use the latest architecture
  • Are willing to completely rewrite your SEO implementation

Version 6 will continue to receive bug fixes and security updates.

📋 Summary

Next SEO v7 represents a ground-up rewrite of the library, modernizing every aspect from tooling to API design. This release focuses on:

  • Modern developer experience with improved TypeScript support and better tree-shaking
  • AI-friendly development making it easier to maintain and contribute
  • Google-specification compliance for all JSON-LD components
  • Maintains Pages Router support with function-based API

🎯 Why v7?

The web development ecosystem has evolved significantly as well as my skills (I hope) since Next SEO's inception. Version 7 addresses several key challenges:

  1. Maintainability: The previous architecture made it difficult to add new components and keep up with Google's evolving structured data specifications
  2. Modern Tooling: Moving from legacy build tools to modern alternatives for better performance and developer experience
  3. AI-Assisted Development: Set up to be AI agent-friendly, making it easier for contributors to add features and fix bugs
  4. Specification Compliance: All JSON-LD components rebuilt from scratch following Google's latest documentation and also you can easily create your own

✨ Major Improvements

1. Modern Build Tooling
  • tsup replaces microbundle for faster, more reliable builds
  • Vitest replaces Jest for lightning-fast unit tests
  • Playwright replaces Cypress for more stable E2E testing
  • ESM-first with CommonJS compatibility
2. Enhanced Developer Experience
  • Full TypeScript rewrite with improved type inference
  • Better tree-shaking support
  • Comprehensive documentation for each component
  • AI-friendly codebase with AGENTS.md and ADDING_NEW_COMPONENTS.md guides
3. Google-Compliant JSON-LD Components

All JSON-LD components have been rebuilt from scratch following Google's structured data gallery specifications:

  • More accurate schema implementation
  • Better validation and error messages
  • Support for latest schema.org properties
4. Simplified Pages Router API

Instead of components that manage Next.js internals, v7 exposes pure functions that you control:

// v6 (old)
import { NextSeo } from "next-seo";
<NextSeo title="My Page" description="..." />;

// v7 (new)
import Head from "next/head";
import { generateNextSeo } from "next-seo/pages";
<Head>{generateNextSeo({ title: "My Page", description: "..." })}</Head>;

💔 Breaking Changes

Complete API Redesign

This is not a drop-in replacement. Every aspect of the API has changed:

Pages Router Changes
Feature v6 v7
Component <NextSeo /> generateNextSeo() function
Default SEO <DefaultSeo /> generateDefaultSeo() function
Import next-seo next-seo/pages
Usage Direct component Wrap in <Head>
App Router Changes
Feature v6 v7
Usage Components with useAppDir={true} Direct component usage
Title prop Not required Built-in support
Placement page.js page.tsx/jsx
JSON-LD Component Changes

All components have completely new APIs. Properties have been renamed, restructured, or removed to match Google's specifications.

🔄 Migration Guide

Basic Pages Router Migration
Before (v6):
// pages/index.tsx
import { NextSeo } from "next-seo";

export default function Home() {
  return (
    <>
      <NextSeo
        title="My Homepage"
        description="Welcome to my website"
        canonical="https://example.com"
        openGraph={{
          url: "https://example.com",
          title: "My Homepage",
          description: "Welcome to my website",
        }}
      />
      <h1>Welcome</h1>
    </>
  );
}
After (v7):
// pages/index.tsx
import Head from "next/head";
import { generateNextSeo } from "next-seo/pages";

export default function Home() {
  return (
    <>
      <Head>
        {generateNextSeo({
          title: "My Homepage",
          description: "Welcome to my website",
          canonical: "https://example.com",
          openGraph: {
            url: "https://example.com",
            title: "My Homepage",
            description: "Welcome to my website",
          },
        })}
      </Head>
      <h1>Welcome</h1>
    </>
  );
}
JSON-LD Migration Example
Before (v6):
import { ArticleJsonLd } from "next-seo";

<ArticleJsonLd
  url="https://example.com/article"
  title="Article headline"
  images={["https://example.com/image.jpg"]}
  datePublished="2024-01-01"
  authorName="John Doe"
  publisherName="Example News"
  publisherLogo="https://example.com/logo.jpg"
  description="Article description"
/>;
After (v7):
import { ArticleJsonLd } from "next-seo";

<ArticleJsonLd
  url="https://example.com/article"
  headline="Article headline" // Changed from 'title'
  image="https://example.com/image.jpg" // Changed from 'images'
  datePublished="2024-01-01T00:00:00.000Z" // ISO 8601 format recommended
  author="John Doe" // Changed from 'authorName'
  publisher={{
    // Now an object instead of separate props
    "@&#8203;type": "Organization",
    name: "Example News",
    logo: "https://example.com/logo.jpg",
  }}
  description="Article description"
/>;

🛠️ Technical Improvements

Build System
  • tsup: Modern bundler with better ESM/CJS dual package support
  • Path aliases: Cleaner imports with ~ mapping to src
  • Optimized output: Smaller bundle sizes with better tree-shaking
Testing Infrastructure
  • Vitest: 10x faster test execution
  • Playwright: More reliable E2E tests
  • React Testing Library: Better integration testing
Developer Tooling
  • AI-Friendly Documentation: CLAUDE.md and ADDING_NEW_COMPONENTS.md for AI-assisted development
  • Modern ESLint: Flat config with latest rules
  • Prettier Integration: Consistent code formatting
  • Husky: Pre-commit hooks for quality assurance

📚 Documentation

The documentation has been completely rewritten:

  • Component-by-component guides with examples
  • Best practices for each component
  • Migration guides for common scenarios
  • AI-friendly contribution guides

🤝 Contributing

Version 7 makes contributing easier than ever:

  • AI agent-friendly codebase
  • Comprehensive guide for adding new components
  • Modern tooling that's familiar to developers
  • Clear patterns and conventions

🔮 Future Plans

  • Continue v6 maintenance with bug fixes and security updates
  • Add more JSON-LD components based on community needs
  • Further performance optimizations

📞 Support

⚠️ Final Recommendation

Unless you specifically need the new JSON-LD components or are starting a fresh project, we recommend staying on v6. The API changes are extensive and will require a complete rewrite of your SEO implementation. Version 6 remains stable, battle-tested, and will continue to receive maintenance updates.

Thank you for your continued support of Next SEO. I'm excited about the future of SEO in Next.js applications!

v6.8.0

Compare Source

v6.7.2

Compare Source

v6.7.1

Compare Source

  • chore: Add TypeScript definitions to package exports 148ef83
  • add link 36e2048

v6.7.0

Compare Source

  • chore: Update package.json to include exports and specify package manager 30b5e06

  • add outrank dea6abb

  • Update README.md 115b11b

  • Update README.md f005a75

v6.6.0

Compare Source

v6.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: garmeeh/next-seo@v6.4.0...v6.5.0

v6.4.0

Compare Source

v6.3.0

Compare Source

Misc

v6.2.0

Compare Source

v6.1.0

Compare Source

v6.0.0: V6

Compare Source

Breaking change:

If you are using the app directory you will need to migrate from NextSeo component to the built in generateMetaData method in Next.js

Notes:

For standard meta data (eg: , <title>) then it is highly recommended that you use the built in generateMetaData method. You can check out the docs here

For JSON-LD then the only change needed is you should add useAppDir={true} to the JSON-LD component in use. You should add use this component in your page.js and NOT your head.js.

Also better safe than sorry with SEO 😅

As this bug was fixed via #​1062 it may have some strange effects if you have a work around in place.

All other changes:

Configuration

📅 Schedule: Branch creation - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) December 21, 2025 06:51
@vercel
Copy link

vercel bot commented Dec 21, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
template-blog-webapp-nextjs Error Error Feb 17, 2026 8:57am

Request Review

@renovate renovate bot force-pushed the renovate/main-private-next-seo-7.x branch from 70ba860 to ffebc09 Compare December 23, 2025 11:09
@renovate renovate bot force-pushed the renovate/main-private-next-seo-7.x branch from ffebc09 to b13183e Compare December 24, 2025 02:51
@renovate renovate bot force-pushed the renovate/main-private-next-seo-7.x branch from b13183e to 4f83b52 Compare January 24, 2026 07:13
@renovate renovate bot force-pushed the renovate/main-private-next-seo-7.x branch from 4f83b52 to 137b48c Compare January 27, 2026 23:46
@renovate renovate bot force-pushed the renovate/main-private-next-seo-7.x branch from 137b48c to 68c8022 Compare February 17, 2026 00:15
@renovate renovate bot force-pushed the renovate/main-private-next-seo-7.x branch from 68c8022 to a973db6 Compare February 17, 2026 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@renovate-approve renovate-approve[bot] renovate-approve[bot] approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants