Apply safe SEO remediations from the latest /seo-audit report. Removes deprecated tags, inserts missing meta tags, refactors to semantic HTML, and proposes structured data with diff+confirm workflow.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Apply safe SEO remediations from the latest /seo-audit report. Removes deprecated tags, inserts missing meta tags, refactors to semantic HTML, and proposes structured data with diff+confirm workflow.
disable-model-invocation
true
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, float layouts, <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 route head, 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.
Step 1: Locate Latest Audit
Detect docs dir: check docs/, documentation/, .docs/ (same order as /seo-audit).
Read <docs-dir>/seo-audit/latest.md.
If missing: tell the user:
"No audit found at <docs-dir>/seo-audit/latest.md. Run /seo-audit first to generate the baseline audit."
Then stop.
Parse the audit to extract findings grouped by severity. Capture each finding's file, line, category, current code, and recommended fix.
Step 2: Context7 MCP Detection
Same check as /seo-audit:
If available, use Context7 for framework-API syntax validation before writing.
If not, use training-data knowledge and note the mode in terminal output.
Step 3: Framework Detection
Reuse the detection logic from /seo-audit: read package.json, config files, directory structure. Record framework + version. All fixes must use framework-idiomatic APIs.
Step 4: Classify Findings
Split findings into three buckets:
Safe-auto fixes (apply without asking content):
Remove <meta name="keywords"> tags
Remove <meta http-equiv="X-UA-Compatible"> tags
Remove IE conditional comments
Add rel="noopener noreferrer" to target="_blank" links
Add loading="lazy" to below-fold images (when position inferable from HTML order or explicit class/id markers)
Add decoding="async" to images
Add width/height to images where intrinsic dimensions are resolvable (check adjacent CSS, import-based imports like next/image, or static analysis of the image file if accessible)
Add async or defer to third-party <script> tags
Add missing <html lang="en"> (default to en; ask user if non-English project detected via i18n config)
Fix XHTML-style self-closing void elements (<br /> → <br>, <img /> → <img>) in HTML5 contexts
Replace <b>/<i> used for semantic emphasis with <strong>/<em> (when context shows emphasis intent, not stylistic)
Add <meta charset="UTF-8"> if missing
Add <meta name="viewport" content="width=device-width, initial-scale=1"> if missing
Content-requiring fixes (propose + confirm):
Writing meta <description> — propose based on page content analysis, ask for approval/edit
Writing <title> — propose based on <h1> or page content
Writing Open Graph / Twitter Card copy
Canonical URL (need domain — ask once, cache for session)
Structured data content (propose schema type + filled placeholders)
Ask user to confirm the batch once: "Apply safe auto-fixes across files?"
On confirm (or if --dry-run, just display): edit files.
Content-requiring:
For each finding, present the proposed content + show target file location:
File: app/layout.tsx
Adding meta description:
"150-160 char summary proposed from H1 'Portfolio of Charles Jones' and first paragraph of hero section."
Proposed: "Charles Jones — full-stack developer building accessible web apps with React, TanStack, and .NET. Case studies, open-source plugins, and contact info."
(a) accept, (e) edit, (s) skip
Use the AskUserQuestion tool for decisions.
On edit: accept free-text input for the new content.
On accept: apply via framework-idiomatic API.
Larger refactors:
Show the proposed diff.
Ask for explicit confirmation per file.
Skip any the user declines.
Step 6: --dry-run Mode
If --dry-run flag provided:
Perform all classification and proposals as usual.
Print the diff for every change that would be applied.
Write nothing to disk.
End with: "Dry run complete. N changes would be applied. Re-run without --dry-run to apply."
Step 7: Framework-Idiomatic Application
Translate raw HTML fixes into the detected framework's idiom:
Next.js (App Router):
Meta fixes → export const metadata or generateMetadata() in app/layout.tsx or per-route page.tsx
Robots → app/robots.ts
Sitemap → app/sitemap.ts
OG image → app/opengraph-image.tsx
Structured data → <script type="application/ld+json"> rendered in server component
Next.js (Pages Router):
Use next/head with explicit <Head> tags
Nuxt:
Use useSeoMeta({...}) in <script setup> or app.vue
Example 2: Propose meta description (content-requiring)
File: src/routes/__root.tsx (TanStack Start)
Missing: meta name="description"
Proposed (from H1 + first paragraph):
"Charles Jones — full-stack developer building accessible web apps with React, TanStack Start, and .NET. Portfolio, case studies, and open-source work."
(154 chars — within 150-160 target range)
(a) accept (e) edit (s) skip
