SkillsAdd

hainrixz/claude-seo-ai

seo-social-cards

Audit and generate Open Graph and Twitter/X social-card tags for a page — check og:title/description/url/type, og:image presence/size/reachability, and twitter:card/title/description/image, then inject complete card tags inferred from the page.

First seen Jun 2, 2026

Installation

$ npx skills add hainrixz/claude-seo-ai --skill seo-social-cards
View on skills.sh ↗ GitHub repository ↗

Summary

  • Audit and generate Open Graph and Twitter/X social-card tags for a page — check og:title/description/url/type, og:image presence/size/reachability, and twitter:card/title/description/image, then inject complete card tags inferred from the page.
  • Module M8.
  • Feeds the Search SEO score.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

stitch-design-taste Same topic
leonxlnx/taste-skill 287.7K installs
firecrawl-seo-audit Same topic
firecrawl/firecrawl-workflows

Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and hea…

31.6K installs
taste-design Same topic
google-labs-code/stitch-skills 17.5K installs
apify-ultimate-scraper Same topic
apify/agent-skills

Universal AI-powered web scraper for any platform. Scrape data from Instagram, Facebook, TikTok…

15.2K installs
clerk-vue-patterns Same topic
clerk/skills

Vue 3 patterns with Clerk — composables (useAuth, useUser, useClerk, useOrganization), Vue Rout…

11.4K installs
email-best-practices Same topic
resend/resend-skills

Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/…

8.9K installs

Also in this package

Other skills from hainrixz/claude-seo-ai · top by installs.

npx skills add hainrixz/claude-seo-ai
seo-schema-jsonld 157 fix 151 geo 150 audit 149 score 148 seo-eeat 147 seo-ai-crawlers 147 seo-internal-linking 146 seo-crawl-render 145 seo-indexability 145

Browse all from hainrixz/claude-seo-ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 57
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Grep, Glob, WebFetch, Bash

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,189 B
  • docs SUMMARY.md 309 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 143 installs

SKILL.md

seo-social-cards (M8)

Social cards control how a URL renders when shared on social, chat, and AI assistants — a CTR/sharing signal, not a ranking one (see Honesty). Open Graph metadata is the same <head>-level hygiene tier as the structured-data work in references/schema-tier1.md, so audit it alongside that module.

Inputs

Work from the PageSnapshot named in your dispatch envelope: read parsed from <rundir>/pages/<slug>.json (metas[] for og:/twitter:, canonicals[], images[]); Grep pages/<slug>.html for verbatim evidence; site artifacts live in <rundir>/site/{robots.json,sitemaps.json,discovery.json}. Deterministic findings already emitted by audit.mjs are listed in <rundir>/findings.deterministic.json — do not re-emit those ids; add model-judged findings only. If invoked directly with a URL/path and no snapshot exists, first run node "${CLAUDEPLUGINROOT}/scripts/snapshot.mjs" <target> --out "${CLAUDEPLUGIN_DATA}/runs" and use the printed snapshot path.

Audits

Working from the PageSnapshot (parsed_rendered when render.used is not none, else parsed):

  1. OG content: og:title, og:description, og:url, og:type present and non-empty; og:url matches the canonical; og:type sane for the page (e.g. article vs website).
  2. OG image: og:image present, ~1200x630 (1.91:1) and >=200x200, and reachable (HTTP 200, image content-type, absolute URL).
  3. Twitter/X: twitter:card (prefer summarylargeimage); twitter:title, twitter:description, twitter:image. Twitter falls back to OG when these are absent — note when it is relying on OG.
  4. Fallback behavior: when OG is absent entirely, record what crawlers would derive (<title>, meta description, first content <img>) so the finding shows the actual degraded card, not a guess.

Fixes

  • AUTO (fixable: auto): inject a complete OG + Twitter card block derived from the page's <title>/<h1>, meta description, canonical URL, and first in-content image. Additive, deterministic, emitted as a diff for fix.
  • The tool cannot create an image asset. It wires og:image/twitter:image once a real path exists; until then it leaves a clearly-marked TODO placeholder (no invented URL or dimensions). Never fabricate title/description text — derive from on-page content or leave the user a TODO.

Verification

  • dom_assert: the required <meta property="og:"> / <meta name="twitter:"> tags exist and are non-empty.
  • header_check: og:image returns 200 with an image content-type, and dimensions are ~1200x630.
  • When the image fetch or dimension probe is blocked (no network/egress), status is needs_api, never a false pass.

Findings

Emit findings per schema/finding.schema.json. Examples:

  • M8.og.missing_image — no og:image (status fail, severity 2, fixable: auto, axis search, confidence established).
  • M8.og.image_unreachable — og:image set but returns non-200 / wrong type (status fail, severity 2, fixable: proposed, axis search, confidence established).
  • M8.twitter.no_card — no twitter:card, page falls back to OG only (status warn, severity 2, fixable: auto, axis search, confidence directional).

Each finding: evidence.observed quotes the tag(s) (or their absence) on the page; verification.reproduce is a runnable domassert/headercheck command; expected_impact is banded + confidence-tagged (no naked %).

Honesty

Social cards are a sharing / click-through signal with near-zero direct ranking impact — Google does not use OG tags as a ranking factor. They improve how shared links and AI-assistant previews render, not where the page ranks. Fix them for CTR and brand consistency; do not over-invest expecting SERP movement.