og-metadata-audit

Audit OpenGraph and Twitter metadata across Next.js App Router projects.

16|3|Updated May 5, 2026
One-click install
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill og-metadata-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: og-metadata-audit
Source: https://github.com/Kevin-Liu-01/Agent-Machines/tree/main/knowledge/skills/og-metadata-audit
Command: npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill og-metadata-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Metadata inconsistencies across a Next.js App Router project lead to broken previews and confusing SEO signals. This skill identifies missing or misconfigured OpenGraph and Twitter card data across pages, layouts, and middleware, then provides fixes or guidance to align them.

Core Features & Use Cases

  • Inventory and cross-check all metadata exports (metadata, generateMetadata) across the app.
  • Validate root layout and per-page alternates (canonical URLs) to ensure correct SEO signals.
  • Recommend and apply DRY refactors for shared OpenGraph/Twitter blocks to improve consistency.

Quick Start

Run an OG/Twitter metadata audit across your Next.js App Router project and report any inconsistencies.

Frequently Asked Questions about og-metadata-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit OpenGraph and Twitter metadata in a Next.js App Router project?

Audit OpenGraph and Twitter metadata by inventorying all metadata exports across layouts and pages to detect missing fields, canonical issues, and inconsistent images. Validate root layout and per-page alternates to ensure correct SEO signals across the Next.js project.

Why does my OpenGraph metadata show broken previews in Next.js?

Broken OpenGraph previews often stem from misconfigured metadataBase resolution or missing fields in per-page openGraph blocks. Check root layout exports and ensure shared OpenGraph/Twitter blocks use DRY patterns to prevent inconsistencies.

What is the best way to fix inconsistent Twitter cards across Next.js pages?

Fix inconsistent Twitter cards by applying DRY refactors using a helper like buildPageMetadata to centralize shared Twitter block configurations. Cross-check generateMetadata exports to ensure all pages emit consistent image and canonical data.

Can I check canonical URLs and robots directives in Next.js middleware?

Yes, you can check canonical URLs and robots directives by auditing middleware alongside root layout and per-page alternates. Validate metadata exports to detect canonical issues and ensure correct robots directives are applied across the App Router.

Does this metadata audit work with generateMetadata exports in Next.js App Router?

Yes, the metadata audit works with generateMetadata exports by inventorying and cross-checking them across the Next.js App Router project. It validates metadataBase resolution, openGraph blocks, and canonical alternates to detect missing or misconfigured fields.