seo-fix

Applies seo-audit findings as safety-tiered code fixes for Astro, Next.js, and Hugo sites.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill seo-fix-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seo-fix
Source: https://github.com/greglas75/zuvo/tree/main/skills/seo-fix
Command: npx skills add https://github.com/greglas75/zuvo --skill seo-fix-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running an SEO audit, manually patching sitemaps, robots.txt, JSON-LD schema, meta tags, and headers across framework-specific files is slow and error-prone. This Skill reads seo-audit JSON findings and applies the fixes automatically, classifying each by safety tier so risky changes never ship without review. ## Core Features & Use Cases - Safety-tiered fix application: Classifies findings as SAFE, MODERATE, or DANGEROUS; SAFE fixes apply automatically, MODERATE fixes pass 3-layer validation, and DANGEROUS fixes (like canonical changes) require explicit confirmation with a shown diff. - Framework-aware templates: Generates correct patches for Astro, Next.js, and Hugo, including sitemap integration, JSON-LD structured data, Open Graph meta tags, security headers, robots.txt AI-bot policy, and llms.txt/llms-full.txt generation with mandatory X-Robots-Tag noindex rules. - Verification and rollback: Runs the project build after fixes, verifies generated artifacts and endpoints, and rolls back individual files to snapshots if the build fails. - Use Case: After zuvo:seo-audit reports a 53/100 score with 16 findings, run seo-fix with --auto to apply all SAFE and MODERATE fixes, then review the report showing the estimated score improvement and items needing manual review. ## Quick Start Apply the safe fixes from my latest seo-audit JSON report and show me which findings still need manual review.

Frequently Asked Questions about seo-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix SEO audit findings in Astro or Next.js?

Run seo-fix after generating an audit JSON with seo-audit. It reads the findings, classifies each fix by safety tier, and applies SAFE fixes automatically. Use --auto to also apply MODERATE fixes with validation.

What is the difference between SAFE, MODERATE, and DANGEROUS SEO fixes?

SAFE fixes like adding llms.txt or viewport meta apply automatically. MODERATE fixes like sitemap or JSON-LD additions require 3-layer validation. DANGEROUS fixes like canonical URL changes are never auto-applied and require explicit user confirmation with a shown diff.

Does seo-fix support Hugo and static site generators?

Yes, seo-fix supports Astro, Next.js, and Hugo with framework-specific template targets. Hugo fixes write to static/ and layouts/partials/, while Astro and Next.js use public/ and their respective config conventions.

What happens if the build fails after applying SEO fixes?

seo-fix snapshots every file before modification. If the build exits with a non-zero code, it rolls back the responsible file, re-runs the build, and marks remaining findings as NEEDS_REVIEW if failures persist.

Can seo-fix change canonical URLs or robots.txt automatically?

Canonical fixes are DANGEROUS tier and always require explicit confirmation after showing the exact diff. Robots.txt fixes can be applied but are escalated to NEEDS_REVIEW when Cloudflare or another edge layer may override the file.

Why does seo-fix refuse to apply fixes from an old audit?

Audits older than 24 hours trigger stale audit protection. Default and dry-run modes proceed with a warning, but --auto and --all modes require user confirmation before mutating files based on potentially outdated findings.