Blog SEO Audit
Audits blog posts for SEO, structure, links, metadata, and search intent.
Install
npx skills add appwrite/appwrite --skill auditing-seo -g -a claude-code -y- Repository
- appwrite/appwrite57.8k
- Category
- Marketing
- Updated
- 2d ago
- License
- BSD-3-Clause
- Context cost
- Mediumabout 1,744 tokens
- Runs scripts
- No, instructions only
What it does
Audits Appwrite blog posts for SEO, AEO, content structure, links, metadata, and search intent. Use when the user asks for an SEO audit, SEO review, search optimization check, or pre-publishing SEO assessment.
Repository layout (apps/console)
This skill targets the Console app at apps/console in appwrite/appwrite; paths are relative to it. Path mapping from the upstream appwrite/website skills:
| Artifact | Path |
|---|---|
| Blog post | src/content/blog/posts/<slug>.markdoc |
| Docs page | src/content/docs/{path}/index.markdoc |
| Changelog entry | src/content/changelog/entries/<YYYY-MM-DD>.markdoc |
| Cover image | public/images/blog/<slug>/cover.avif (min 1200px wide; run bun run generate:cover-manifest after adding) |
Also apply the unslop skill to all user-facing prose.
SEO Audit
How to run an audit
When asked to audit a blog post, read src/content/blog/posts/<slug>.markdoc and evaluate every item below. Identify the primary keyword from the title, slug, headings, and content. If the target keyword remains ambiguous, state the keyword you inferred and ask the user to confirm it.
Before scoring:
- Count title and
descriptioncharacters, including spaces. - Count body words, excluding frontmatter.
- Read the relevant local files under
src/content/docs/to verify Appwrite claims and internal doc links. - Check that internal and external links resolve when tools and network access allow it. Clearly mark any link you could not verify.
Do not rewrite the post unless the user asks. Report specific problems and exact fixes instead.
