Update to DidYouSEO

{
  "description": "Audit a page or site with DidYouSEO and turn the results into a ranked fix plan with exact changes. Use when the user asks to audit a URL, find SEO problems, check why a page isn't ranking technically, or wants a prioritized SEO to-do list. Requires the DidYouSEO MCP connector.",
  "included_files": [],
  "name": "seo-audit-fix-plan",
  "skill_md_contents": "---\nname: seo-audit-fix-plan\ndescription: Audit a page or site with DidYouSEO and turn the results into a ranked fix plan with exact changes. Use when the user asks to audit a URL, find SEO problems, check why a page isn't ranking technically, or wants a prioritized SEO to-do list. Requires the DidYouSEO MCP connector.\n---\n\n# SEO audit to fix plan\n\nTurn a DidYouSEO audit into a short, ordered list of fixes the user can act on today.\n\n## Tools\n\n- `run_seo_audit` (url) - runs a 40+ point audit and returns score, issues and how to fix each one.\n- `list_sites`, `get_site_score` - when the user means a whole site already in their account.\n- `analyze_meta_tags`, `validate_schema` - to draft exact replacement tags or markup.\n\n## Steps\n\n1. Work out the target. A single URL means `run_seo_audit`. A site name (\"my site\", a domain) means `list_sites` first, then `get_site_score` for the latest crawl. If the site isn't in the account, audit its homepage with `run_seo_audit` and say so.\n2. Group issues by severity: critical first, then warnings. Ignore passed checks.\n3. Rank inside each group by effort and impact:\n   - Indexing blockers first (noindex, robots blocks, broken canonicals, 4xx/5xx).\n   - Then anything shown in search results (title, meta description, structured data).\n   - Then speed and Core Web Vitals.\n   - Then accessibility and best-practice items.\n4. For every fix, give the exact change. Draft the new title or description, the corrected JSON-LD, or the header to add. Use `analyze_meta_tags` or `validate_schema` if you need the current values.\n5. Do not invent issues the tools didn't report. If something looks wrong but wasn't flagged, say \"worth checking\" and keep it separate.\n\n## Output format\n\n```\nScore: <n>/100 for <url>\n\nFix first (critical)\n1. <issue> - why it matters in one line\n   Change: <exact change>\n\nFix next (warnings)\n...\n\nAlready fine: <one line naming the main areas that passed>\n```\n\nKeep it under 15 items. If there are more, show the top 15 and say how many were left out.\n\n## Limits\n\n- Audits and single-URL checks (`run_seo_audit`, `run_pagespeed_insights`, `analyze_meta_tags`, `check_robots_txt`, `validate_schema`, `serp_preview`, `check_core_web_vitals`, `check_open_graph`, `check_hreflang`) count as page checks. On the Free plan there are 10 a day. If a tool says \"Daily limit reached\", stop calling them, tell the user the limit resets at 00:00 UTC, and finish with the data you have.\n- On the Free plan, the Search Console and Google Analytics tools return a short preview. Say the results may be incomplete.\n- Don't mention prices or upgrades. If the user asks how to get more, say plan details are on didyouseo.com.\n"
}