geo-fix

Run geo-fix with no arguments to apply SAFE fixes from the latest geo-audit JSON, or use --auto to also apply MODERATE fixes. DANGEROUS fixes always require explicit per-fix confirmation, and --dry-run previews all planned changes without applying them.

Auto-applied fixes include schema.org JSON-LD additions, robots.txt AI bot allow rules, canonical tags, sitemap references, llms.txt generation, and frontmatter dateModified fields. Content-related findings like BLUF restructuring only receive structural scaffold comments, never generated body content.

Yes, geo-fix detects the framework by scanning for astro.config, next.config, or hugo.toml files and resolves framework-specific target files. For example, schema fixes go into the root layout for Astro, app/layout.tsx for Next.js, and layouts/partials/head.html for Hugo.

Geo-fix runs build verification after applying fixes and treats any non-zero exit code as failure. It rolls back the specific files that caused the failure, re-runs the build, and marks remaining findings as NEEDS_REVIEW if the build still fails.

Geo-fix reads prior seo-fix JSON reports and skips findings whose fix_type and file match an already-FIXED seo-fix action, marking them ALREADY_APPLIED_BY_SEO_FIX. This specifically covers equivalent operations like llms.txt generation across both skills.

It refuses when the audit JSON is over 24 hours old in --auto mode, when a target file has uncommitted changes, when a fix is DANGEROUS tier without confirmation, or when validation layers fail. Such findings are marked NEEDS_REVIEW or MANUAL with reasons.