Blog SEO Validator
Validate on-page SEO before publication and turn failures into prioritized, actionable fixes.
The skill explicitly limits itself to reading local content and using WebFetch, Grep, and Glob for page and link audits, so the apparent permission scope is moderate; however, it does not explain fetched-content data flow, sensitive-data handling, user confirmation, external-request boundaries, rollback, or recovery. The optional Google credential check also fails silently, so points are deducted.
The workflow and checklists are detailed, with PASS/FAIL/WARN/N/A states and concrete fixes; however, static evidence does not establish that the key paths run. WebFetch, HTML/meta extraction, bidirectional-link checks, and the optional PageSpeed path lack clear failure diagnostics, and Step 5 is duplicated, so points are deducted.
The description, trigger phrases, argument hint, and file/URL input modes are clear enough for post-writing blog SEO audits; however, non-fit boundaries, input constraints, site-structure variation, and Chinese-language adaptation are under-specified. URL retrieval and external verification may also depend on services reachable from mainland China, so points are deducted.
The file has structured workflow sections, tables, an output template, status definitions, and MIT licensing; however, it lacks its own version, changelog, maintenance owner, installation/dependency guidance, FAQ, and systematic limitation disclosure. Several external tools and paths are assumed rather than documented, so points are deducted.
The skill can produce a directly usable SEO validation report with statuses, details, and prioritized fixes, and its core task is clear; however, several rules are mechanical or weakly contextualized, such as mandatory power words, statistics in meta descriptions, and a fixed H2 question ratio. Static review cannot verify actual SEO outcomes, so points are deducted.
The explicit criteria and report structure make parts of the audit traceable; however, the selected skill contains no source citations, dedicated tests, or third-party execution evidence. General repository tests do not validate this SKILL.md's key paths, so only limited credit is justified.
- WebFetch brings external page content into the model context, but the skill provides no explicit boundary for indirect prompt injection or sensitive content.
- External link checks, Google credentials, and PageSpeed checks depend on external services that may be unavailable or incomplete from mainland-China networks.
- Several SEO thresholds are presented as hard rules and should be manually reviewed against search-engine behavior, site type, language, and intent.
- This review did not execute the skill and found no dedicated execution evidence for the assessed path.
What does this skill do, and when should you use it?
Blog SEO Check is an invokable skill in the claude-blog suite for validating completed blog posts. It checks titles, meta descriptions, heading structure, keywords, internal and external links, canonical URLs, Open Graph tags, Twitter Cards, URL structure, and image alt text. The result is a pass/fail validation report with concrete recommendations for failed checks. It fits teams and writers who already have an article file or page and need a pre-publication SEO review.
Reads the target file’s frontmatter, heading hierarchy, body text, links, and metadata; when given a URL, it uses WebFetch to retrieve the page and extract relevant elements. It evaluates title length and keyword placement, meta-description quality, H1-H3 structure, keyword usage, internal and external links, link deduplication, the FLOW evidence triple, canonical URLs, Open Graph tags, Twitter Cards, URL slugs, and image alt text. It can use Grep and Glob to scan project blog content for possible bidirectional internal linking. It produces an SEO Validation Report with per-check status, details, fixes, totals, notes, and prioritized recommendations.
- A solo blogger has finished a Markdown post and wants to catch title, metadata, and structure problems before publishing.
- A marketing team is preparing an article and needs a consistent review of canonical URLs, social metadata, and link quality.
- An editor inherits an existing blog file and needs a checklist-based pass/fail report with actionable fixes.
- A site maintainer wants to inspect URL slugs, internal links, external links, and image alt text across a post.
What are this skill's strengths and limitations?
- Provides a concrete checklist spanning on-page SEO, social metadata, links, canonical URLs, and image alt text.
- Returns explicit statuses and prioritized fixes suitable for pre-publication review.
- Supports both local content files and URL-based page retrieval.
- Includes link deduplication and FLOW evidence-triple validation for cited statistics.
- It is a post-writing validator, not a complete blog-writing or publishing workflow.
- External-link reachability checks require network access; the optional live performance check also requires a published URL and blog-google credentials.
- Bidirectional-link verification depends on other blog content being available in the project, and the source only specifies Grep and Glob scanning rather than a standalone verifier.
- The source does not provide independent test results for this individual skill, so its rule coverage cannot be assessed separately from the suite.
How do you install this skill?
This skill is located at skills/blog-seo-check/SKILL.md in AgriciDaniel/claude-blog. The README documents installation for the full collection: in Claude Code, run /plugin marketplace add AgriciDaniel/claude-blog, then /plugin install claude-blog@agricidaniel-claude-blog. The repository is MIT-licensed.
How do you use this skill?
After installing the collection and restarting Claude Code, run /blog seo-check <file-path> against a completed post. Supported trigger phrases include “seo check,” “check seo,” “validate seo,” “blog seo,” and “on-page seo.” A URL can be supplied instead of a file path; external-link checks and some project-wide checks require network and filesystem access.
How does this skill compare with similar options?
Compared with asking Claude or ChatGPT for a one-off SEO review, this skill supplies fixed pass criteria and a prioritized correction report. Compared with manual inspection, it covers metadata, link duplication, canonical URLs, social cards, and URL structure systematically, but it still requires a completed post or accessible page as input.