Blog Seo Check

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

Step 3: Meta Description

Step 4: Heading Hierarchy

Step 5: Internal Links

Use Grep and Glob to scan the project for existing blog content and verify bidirectional linking where possible.

Step 5.5: Link Deduplication

For each duplicate found: 1. Normalize URLs (strip trailing slashes, query parameters, fragments) 2. Score each instance by anchor text descriptiveness (keyword-rich > generic) 3. Recommend keeping the highest-scored instance, removing others 4. Deduct 1 point per duplicate from SEO Optimization score

Google records 1-2 anchor texts per URL per page (Zyppy 2023). Optimal: link to same URL once in body content; 5-10 internal links per 2,000 words; max ~50 total links per page.

Step 6: External Links

FLOW evidence triple (citations)

For every public statistic in the post, verify all three components:

• Year anchor appears in prose ("In 2026," or "As of Q1 2026,") BEFORE the statistic, not buried in parentheses.
• Inline citation names the publisher AND the document title (or report name).
• Source block at the bottom of the post includes the URL plus retrieved YYYY-MM-DD for each cited source.

Posts that fail any of the three either drop the unverifiable claim or replace it with a verified alternative. See skills/blog/references/flow-alignment.md. For a one-shot prompt-driven check, see /blog flow optimize.

Step 7: Canonical URL

Step 8: OG Meta Tags

Step 9: Twitter Card

Step 10: URL Structure

Step 11: Generate Report

Output a comprehensive SEO validation report in this format:

## SEO Validation Report: [Title]

**File**: [path or URL]
**Date**: [check date]
**Overall**: [X/Y checks passed] - [PASS/NEEDS WORK/FAIL]

### Results

| # | Check | Status | Details | Fix |
|---|-------|--------|---------|-----|
| 1 | Title length | PASS | 52 chars | - |
| 2 | Title keyword | PASS | "keyword" in first half | - |
| 3 | Title power word | FAIL | No power word found | Add "Guide", "Essential", or "Complete" |
| 4 | Meta description length | PASS | 155 chars | - |
| 5 | Meta description stat | FAIL | No number found | Add a key statistic from the post |
| ... | ... | ... | ... | ... |

### Summary

**Passed**: [N] checks
**Failed**: [N] checks

### Priority Fixes
1. [Most impactful fix - what to change and where]
2. [Second most impactful fix]
3. [Third most impactful fix]

### Notes
- [Any observations about overall SEO health]
- [Suggestions for improvement beyond the checklist]

Status values:

• PASS - Meets the criteria
• FAIL - Does not meet the criteria, fix provided
• WARN - Partially meets criteria or edge case, recommendation provided
• N/A - Not applicable (e.g., no Twitter Card tags if site has no X account)

Optional: Live Performance Check (blog-google)

If the post has a published URL and blog-google credentials are available:

1. Check credentials: python3 skills/blog-google/scripts/run.py google_auth --check --json 2. If Tier 0+, run PageSpeed: python3 skills/blog-google/scripts/run.py pagespeed_check <url> --json 3. Append to report:

• Lighthouse Performance, Accessibility, Best Practices, SEO scores
• CWV field data (LCP, INP, CLS) with traffic-light ratings
• Top 3 opportunities with estimated savings

4. Falls back silently if credentials unavailable or URL not published.