fixing-metadata

Fix page metadata for titles, descriptions, canonicals, robots, social tags, and structured data.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/alslimany/tams --skill fixing-metadata-alslimany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixing-metadata
Source: https://github.com/alslimany/tams/tree/main/.cursor/skills/fixing-metadata
Command: npx skills add https://github.com/alslimany/tams --skill fixing-metadata-alslimany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship correct, complete metadata across pages to avoid duplicates, misrouting, and inconsistent user experiences.

Core Features & Use Cases

  • Ensures a single source of truth for page title, description, canonical URL, robots, og:image, and JSON-LD across the site.
  • Validates locale/alternate language handling and provides consistent metadata defaults for new and updated pages.
  • Use case: when adding or editing pages, run this to harmonize metadata and prevent conflicting tags.

Quick Start

Update or validate the metadata fields across a page to ensure consistency and correctness.

Frequently Asked Questions about fixing-metadata

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

FAQPage Schema
How do I fix duplicate page metadata and canonical URL issues across a website?

Fix metadata by enforcing a single source of truth per page for titles, descriptions, and canonical URLs. This validation process applies safe defaults and deterministic behavior to prevent duplicates and misrouting across pages.

What's the best way to validate structured data and social tags for consistency?

Validate structured data and social tags like og:image by harmonizing metadata fields across pages. This ensures JSON-LD and social tags remain correct, complete, and consistent, preventing conflicting tags from causing inconsistent user experiences.

How do I handle alternate language metadata and locale validation for SEO?

Locale and alternate language handling is validated during the metadata harmonization process. It enforces consistent metadata defaults for new and updated pages, ensuring alternate language tags are correctly configured for SEO.

Why does frontmatter metadata need a single source of truth per page?

Frontmatter metadata needs a single source of truth to avoid duplicates and misrouting. Enforcing deterministic behavior and safe defaults across page titles, robots, and canonical URLs prevents conflicting tags from degrading search rankings.

Can I use metadata validation for new pages or is it only for existing content?

Metadata validation applies to both new and updated pages. When adding or editing pages, running this validation harmonizes metadata fields and provides consistent defaults to prevent conflicting tags across the site.