106.9K+Download
Skip to the usage guide
Fixing Metadataby ibelick

Fixing Metadata Skill.

Repair page identity, indexing signals and social share previews.

  • Metadata
  • Social Previews
Download OpenDesignView Usage Guide
Source Review · fixing-metadataSKILL.md
Task Repair page identity, indexing signals and social share previews. Produces A prioritized list of metadata defects on the scoped pages. Before You Start The source excludes unrelated refactors and framework or SEO-library migrations.
Editorial summary · source reviewed 2026-11-02 · not a generated example

01 What It Does

Repair page identity, indexing signals and social share previews

Audit canonical URLs, robots, titles, social cards and JSON-LD with focused metadata changes that follow the project's existing system.

Source-based workflowNot an execution benchmark

The Working Approach

Fixing Metadata reviews the information a page exposes to search engines, social previews and browser surfaces. It starts with conflicting or duplicate tags, then checks whether the title, description, canonical URL and Open Graph identity describe the same page. This is useful when a visually complete page still shares the wrong image or exposes inconsistent indexing instructions.

The source prioritizes narrow repairs within the project's current metadata implementation. It covers icons, manifests, structured data and real language alternatives as well as social cards. Its verification boundary matters: a social image that exists locally still needs checking on a real reachable URL.

Expected Deliverables

  • A prioritized list of metadata defects on the scoped pages.
  • Focused corrections using the existing framework or head-management pattern.
  • Verification notes for canonical identity, indexing intent and real-URL social previews.
See the Example Brief

From Brief to Review

  1. 01
    Inspect page identity

    Find missing or conflicting title, description, canonical and robots tags. Establish the preferred URL and the intended public or private status before changing directives.

  2. 02
    Repair the highest-impact conflicts

    Remove duplicate definitions and align canonical with og:url. Set plain-text descriptions and stable social image URLs using the project's existing metadata mechanism.

  3. 03
    Review secondary surfaces

    Check icons, manifest and relevant JSON-LD against actual rendered content. Verify real localized alternatives, then inspect social cards at a reachable URL.

02 When to Use It

When to Use It

The source excludes unrelated refactors and framework or SEO-library migrations.

A Good Fit

  • Incorrect share previewsA public page shares the wrong title, image or destination identity.
  • Metadata release reviewA new page needs consistent indexing and browser metadata before publication.

Limits to Check

  • Focused changesThe source excludes unrelated refactors and framework or SEO-library migrations.
  • Evidence-based schemaStructured data must reflect real content; ratings, prices and organization details cannot be invented.
  • Reachable previewLocalhost checks alone do not establish that external social cards render correctly.

Bring These Inputs

  • Scoped pagesProvide the page routes and the shared metadata code they use.
  • Access intentIdentify public pages, private areas and staging routes.
  • Actual assetsSupply canonical destinations, share images and existing locale alternatives.

03 Decisions That Matter

Decisions That Matter

  1. One page identity

    Canonical and social metadata can be checked together for disagreement.

  2. Priority order

    Duplicate and indexing conflicts are addressed before lower-impact polish.

  3. Minimal integration

    Repairs follow the product's established metadata ownership.

04 Try a Focused Brief

Try a Focused Brief

The example brief below has not been tested. Check the skill’s setup before using it.

Review the Source and Setup

Provide the page routes and the shared metadata code they use.

Upstream Source File
https://github.com/ibelick/ui-skills/blob/4907a526b07943b3a338177558d42fae4fdf0a86/skills/fixing-metadata/SKILL.md

The reference below opens the upstream instructions. Review the repository setup before using them; it is not an installation command.

Start With One Deliverable

Adapt the scope, source material and constraints in this brief before running the skill.

Example Brief
Use fixing-metadata to audit the product overview and its localized versions. Inspect the current metadata implementation and rendered head for duplicates. Verify the intended canonical URL, robots directive, page title and og:url before editing. Check that share images use absolute URLs and that locale alternatives really exist. Keep changes within metadata and do not add unsubstantiated JSON-LD fields. Provide a concise issue list, the focused fixes, and the real URLs used for social-card verification. Label anything that could only be checked locally.

Inspect the Result

Check the actual output against these observable criteria.

  • Each page emits one consistent set of core identity tags.
  • Structured data and locale alternatives match real page content.
  • Share image URLs and social previews are verified outside localhost.

OpenDesign provides a local design workspace for coding agents. This listing does not mean the skill is bundled or that its external tools, credentials and software dependencies are included.

Download OpenDesignRead the Quickstart

05 Source and License

Source and License

This page describes the pinned source revision linked below. Upstream behavior and requirements can change.

Source Owner
ibelick
Repository
ibelick/ui-skills
Skill File
SKILL.md
License
MIT
Reviewed Snapshot
2026-11-02 · 4907a526b079
Editorial Source Summary
Repair page identity, indexing signals and social share previews.

Original summary by OpenDesign, based on the linked source. Repository stars are a dated popularity signal, not skill usage or a quality score.

06 Questions Before You Start

Questions Before You Start

Will it migrate our SEO library?

The source directs the agent to preserve the existing metadata pattern unless migration is requested.

Should every page receive JSON-LD?

Only when a suitable schema maps clearly to content that is actually rendered.

How are staging pages handled?

The source recommends noindex for previews where possible, while keeping directives aligned with the actual access intent.

OpenDesign

Keep Your Brief and Design Work Together.

Keep your brief, source material and design work together in a local workspace. Check the skill’s own setup before adding it to your workflow.

Download OpenDesignBrowse Design Skills
Upstream Source File
https://github.com/ibelick/ui-skills/blob/4907a526b07943b3a338177558d42fae4fdf0a86/skills/fixing-metadata/SKILL.md