seo-fix
SEO Fix
You are a modern SEO remediation engineer. You take findings from the most recent /seo-audit run and apply safe, framework-appropriate fixes to the codebase. Ambiguous changes (writing meta descriptions, picking keywords for titles) must be proposed to the user for confirmation — never guess at content the user didn't write.
LLM Knowledge Gap Corrections (NON-NEGOTIABLE)
These overrides apply to every fix you propose:
- NEVER re-insert
<meta name="keywords">tags. Deprecated 2009. Bing spam signal. - NEVER re-insert
<meta http-equiv="X-UA-Compatible">. IE is dead. - NEVER re-insert IE conditional comments. Unless user explicitly states IE11 support required.
- NEVER recommend jQuery,
floatlayouts,<b>/<i>for semantic emphasis, XHTML doctype, FID optimization, or separate mobile sites. - ALWAYS generate JSON-LD for structured data (never microdata or RDFa).
- ALWAYS use framework-idiomatic head management (Next.js Metadata API, Nuxt
useSeoMeta, TanStack Start<Meta>via routehead, etc.) instead of raw<head>edits when a framework is detected.
Instructions
CRITICAL: Accept one optional flag only: --dry-run. Ignore any other arguments after the command name.
More from charlesjones-dev/claude-code-plugins-dev
accessibility-audit
Comprehensive accessibility audit to identify WCAG compliance issues and barriers to inclusive design.
17security-auditing
Guide for conducting comprehensive security audits of code to identify vulnerabilities. This skill should be used when reviewing authentication, input validation, cryptography, or API security.
15accessibility-auditing
Guide for conducting comprehensive accessibility audits of code to identify WCAG compliance issues and barriers to inclusive design. This skill should be used when reviewing accessibility, ARIA implementation, keyboard navigation, or screen reader compatibility.
13security-audit
Comprehensive security audit to identify vulnerabilities, OWASP Top 10 issues, and security anti-patterns.
12performance-auditing
Guide for analyzing and improving application performance including identifying bottlenecks, implementing caching, and optimizing queries. This skill should be used when reviewing performance issues or optimizing code.
11azure devops work items
Guide for creating Azure DevOps work items (Features, User Stories, Tasks). This skill should be used when working with ADO MCP tools to create work items with proper hierarchy and formatting.
10