Applying fixes.
Turn Citevera audit findings into shipped changes: copy-paste artifacts, dashboard-driven apply on WordPress, SKILL.md export for any other codebase, and verification.
What a fix looks like
Findings ship with the exact artifact where one exists: a complete llms.txt body, a JSON-LD block for the page head, robots.txt user-agent stanzas, meta-tag directives, or a content rewrite diff. The report is advisory - it reflects what the scan saw at audit time, and your site may have constraints the scan cannot know about, so review before shipping.
On WordPress
The plugin applies fixes you approve from the wp-admin dashboard - llms.txt and robots rules regenerate locally, schema fixes inject as JSON-LD. Nothing changes without your click.
On anything else: SKILL.md
Paid scans export the full recommendation set as a SKILL.md file that Claude Code consumes - it detects your framework (Next.js, Astro, Hugo, Jekyll, and others) and applies each fix in the right place while you review the diffs. The complete workflow is in the Claude Code integration doc.
Verify from the outside
After deploying, confirm the public surface actually changed: the free llms.txt checker and AI crawler access checker fetch your site the way a crawler does. Then rescan on Citevera - the score delta against the previous audit of the same kind is the proof the fix landed.