Individual skill
seonix-fix-site
Fix the technical and on-page SEO issues that Seonix found on a website - turn the Site Health report into a fix plan, apply the fixes in the site's codebase (or let Seonix apply them on WordPress), rescan and verify. Use when the user asks to fix SEO issues, work through Site Health, clear the fix plan, apply Seonix fixes, or rescan the site.
plugins/seonix-ai/mcp/skills/seonix-fix-site/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,533
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- marketing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,077 bytes
Read excerpt
# Fix a site with Seonix
The loop is: Site Health -> fix plan -> fixes -> rescan -> verify. The
`fix_issues_in_code` playbook (`get_playbook`) has the long form; this is
the short one.
## 1. Read
1. `get_site_health` - health score, issue counts by severity, top tasks.
2. `get_fix_plan` - items grouped by issue code, each with the affected
pages, the fix and the target. Default is 10 items with 3 URLs each;
pass `verbose: true` for why/steps/warnings, `limit` and `max_pages` to
widen, `include_markdown: true` for a checklist.
3. `get_issue` for one issue when you need the crawled evidence.