Agent skill · Security

blog-seo-check

Post-writing SEO validation with pass/fail checklist covering title tag length and keyword placement, meta description quality, heading hierarchy and keyword density, internal/external link audit with anchor text analysis, canonical URL verification, Open Graph meta tags (og:title, og:description, og:image), Twitter Card validation, URL structure optimization, and image alt text presence. Produces prioritized fix list with specific recommendations. Use when user says "seo check", "check seo", "validate seo", "blog seo", "seo validation", "on-page seo", "title tag check", "meta description chec

Infrasity-Labsgithub.com/Infrasity-LabsGitHub ↗
claude-codeMIT
Install
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-seo-check --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Path: .claude/skills/blog-seo-check/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 97
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Blog SEO Check: Post-Writing Validation Runs a comprehensive on-page SEO validation against a completed blog post and generates a pass/fail checklist with specific fixes for each failure. Designed to run after writing - catches issues before publishing. ## Workflow ### Step 1: Read Content Read the target file and extract: - **Frontmatter** - title, description, date, lastUpdated, author, tags, canonical, og:image, slug/URL - **Heading structure** - H1, H2, H3 hierarchy with full text - **Links** - All internal and external links with anchor text - **Meta tags** - OG tags, Twitter Card tags, canonical URL - **Body content** - Full text for keyword and structural analysis If the user provides a URL instead of a file path, use WebFetch to retrieve the page and extract the relevant elements. ### Step 2: Title Tag Validation | Check | Pass Criteria | |-------|---------------| | Character count | 40-60 characters (no truncation in SERPs) | | Keyword placement | Primary keyword in first half of title | | Power word | Contains at least one power word (e.g., Guide, Best, How, Why, Essential, Proven, Complete) | | Truncation risk | No critical meaning lost if truncated at 60 chars | | Uni

What's inside
Steps it walks through
  1. Workflow
  2. Step 1: Read Content
  3. Step 2: Title Tag Validation
  4. Step 3: Meta Description
  5. Step 4: Heading Hierarchy
  6. Step 5: Internal Links
  7. Step 5.5: Link Deduplication
  8. Step 6: External Links
  9. FLOW evidence triple (citations)
  10. Step 7: Canonical URL
  11. Step 8: OG Meta Tags
  12. Step 9: Twitter Card
  13. Step 10: URL Structure
  14. Step 11: Generate Report
More from dev-gtm-claude-skills
All skills →
About this skill
What does the blog-seo-check skill do?

Post-writing SEO validation with pass/fail checklist covering title tag length and keyword placement, meta description quality, heading hierarchy and keyword density, internal/external link audit with anchor text analysis, canonical URL verification, Open Graph meta tags (og:title, og:description, og:image), Twitter Card validation, URL structure optimization, and image alt text presence. Produces prioritized fix list with specific recommendations. Use when user says "seo check", "check seo", "validate seo", "blog seo", "seo validation", "on-page seo", "title tag check", "meta description chec

How do I install it?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-seo-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going