fixing-metadata

Use it when:: You ship new pages, fix how links look when shared, or set up titles, canonical URLs or structured data.
It does:: Finds pages with missing or wrong metadata, checks them against ranked rules and fixes duplicates and indexing problems first.
You get:: A small, metadata-only diff in which title, description, canonical URL and og:url agree.
Checks:: Social cards on a real URL, not localhost.

TL;DR

Metadata here is what sits in a page's head: its title and description, the canonical URL (the address search engines should treat as the page's own), robots directives, Open Graph and Twitter card tags for link previews, favicons and the manifest, JSON-LD structured data, and language alternates. Its rules: define metadata in one place per page with no duplicate tags, keep values deterministic, escape dynamic strings and give every page a safe default title and description; use noindex only for private, duplicate or staging pages; use absolute image URLs, and summary_large_image Twitter cards by default; add JSON-LD only when it matches what the page renders, never with invented ratings, reviews or prices; add hreflang alternates only for pages that exist. It follows the project's existing pattern, such as the Next.js metadata API, react-helmet or a hand-written head, and doesn't migrate SEO libraries or touch unrelated code.

Summarizes the skill at 00db7d6.

npx skills add https://github.com/ibelick/ui-skills --skill fixing-metadata

skills.sh page Source on GitHub All skills from ibelick/ui-skills

Total Downloads: 19,500 on skills.sh, Nov 9, 2026
Repo stars: 10,844 ibelick/ui-skills
First seen: Jan 22, 2026 on skills.sh

Weekly Downloads

658

+70% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	388
Sep 28	355
Oct 5	313
Oct 12	302
Oct 19	549
Oct 26	1,111
Nov 2	654
Nov 9	658

Category	category:marketing SEO, copy, conversion, social media and e-commerce.
Type	type:workflow A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect	effect:local Its own steps create or change files, git state or local tools.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:community Everyone else. Unverified vendor claims default to community.
Topics	seo

SKILL.md

From ibelick/ui-skills at 00db7d6. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: fixing-metadata
description: >
  Audit and fix HTML metadata including page titles, meta descriptions, canonical URLs, Open Graph
  tags, Twitter cards, favicons, JSON-LD structured data, and robots directives. Use when adding
  SEO metadata, fixing social share previews, reviewing Open Graph tags, setting up canonical URLs,
  or shipping new pages that need correct meta tags.
version: 1.0.1
license: MIT

Workflow

Identify pages with missing or incorrect metadata (titles, descriptions, canonical, OG tags)
Audit against the priority rules below — fix critical issues (duplicates, indexing) first
Ensure title, description, canonical, and og:url all agree with each other
Verify social cards render correctly on a real URL, not localhost
Keep diffs minimal and scoped to metadata only — do not refactor unrelated code

when to apply

Reference these guidelines when:

adding or changing page titles, descriptions, canonical, robots
implementing Open Graph or Twitter card metadata
setting favicons, app icons, manifest, theme-color
building shared SEO components or layout metadata defaults
adding structured data (JSON-LD)
changing locale, alternate languages, or canonical routing
shipping new pages, marketing pages, or shareable links

rule categories by priority

priority	category	impact
1	correctness and duplication	critical
2	title and description	high
3	canonical and indexing	high
4	social cards	high
5	icons and manifest	medium
6	structured data	medium
7	locale and alternates	low-medium
8	tool boundaries	critical

quick reference

1. correctness and duplication (critical)

define metadata in one place per page, avoid competing systems
do not emit duplicate title, description, canonical, or robots tags
metadata must be deterministic, no random or unstable values
escape and sanitize any user-generated or dynamic strings
every page must have safe defaults for title and description

2. title and description (high)

every page must have a title
use a consistent title format across the site
keep titles short and readable, avoid stuffing
shareable or searchable pages should have a meta description
descriptions must be plain text, no markdown or quote spam

3. canonical and indexing (high)

canonical must point to the preferred URL for the page
use noindex only for private, duplicate, or non-public pages
robots meta must match actual access intent
previews or staging pages should be noindex by default when possible
paginated pages must have correct canonical behavior

4. social cards (high)

shareable pages must set Open Graph title, description, and image
Open Graph and Twitter images must use absolute URLs
prefer correct image dimensions and stable aspect ratios
og:url must match the canonical URL
use a sensible og:type, usually website or article
set twitter:card appropriately, summary_large_image by default

5. icons and manifest (medium)

include at least one favicon that works across browsers
include apple-touch-icon when relevant
manifest must be valid and referenced when used
set theme-color intentionally to avoid mismatched UI chrome
icon paths should be stable and cacheable

6. structured data (medium)

do not add JSON-LD unless it clearly maps to real page content
JSON-LD must be valid and reflect what is actually rendered
do not invent ratings, reviews, prices, or organization details
prefer one structured data block per page unless required

7. locale and alternates (low-medium)

set the html lang attribute correctly
set og:locale when localization exists
add hreflang alternates only when pages truly exist
localized pages must canonicalize correctly per locale

8. tool boundaries (critical)

prefer minimal changes, do not refactor unrelated code
do not migrate frameworks or SEO libraries unless requested
follow the project's existing metadata pattern (Next.js metadata API, react-helmet, manual head, etc.)

review guidance

fix critical issues first (duplicates, canonical, indexing)
ensure title, description, canonical, and og:url agree
verify social cards on a real URL, not localhost
prefer stable, boring metadata over clever or dynamic
keep diffs minimal and scoped to metadata only