{"id":83996,"plugin_id":"plugin_asdk_app_6ad8713615b0819191f7a3c9c7c68999","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-06T07:21:16.146Z","digest":"6780f26de39c684d00e21c0add459a2edfc0975b71065b43800f13a84fe744c3","against":null,"payload":{"description":"Run a go/no-go SEO check before a site, redesign or migration goes live - indexing, robots.txt, canonicals, structured data, hreflang, speed and social tags. Use when the user is launching a site, migrating, redesigning, moving from staging to production, or asks if a site is ready to go live. Requires the DidYouSEO MCP connector; most checks are free.","included_files":[],"name":"pre-launch-seo-check","skill_md_contents":"---\nname: pre-launch-seo-check\ndescription: Run a go/no-go SEO check before a site, redesign or migration goes live - indexing, robots.txt, canonicals, structured data, hreflang, speed and social tags. Use when the user is launching a site, migrating, redesigning, moving from staging to production, or asks if a site is ready to go live. Requires the DidYouSEO MCP connector; most checks are free.\n---\n\n# Pre-launch SEO check\n\nCatch the mistakes that quietly wreck a launch: a leftover noindex, a staging robots.txt, canonicals pointing at the old domain.\n\n## Tools\n\n- `check_robots_txt` (url)\n- `analyze_meta_tags` (url) - robots meta, canonical, title, description.\n- `validate_schema` (url)\n- `check_hreflang` (url) - only if the site has more than one language or region.\n- `run_pagespeed_insights` (url, strategy) - Lighthouse scores, real-user Core Web Vitals and the biggest speed fixes.\n- `check_open_graph` (url)\n- `run_seo_audit` (url) - full audit of the most important page, if the user is signed in.\n\n## Steps\n\n1. Ask for the 3-5 most important URLs (homepage, a main product or service page, a blog post, a contact page) if the user only gave a domain.\n2. Run `check_robots_txt` once on the domain. A `Disallow: /` for all user agents is an automatic no-go.\n3. For each URL run `analyze_meta_tags`, `validate_schema`, `check_open_graph` and `run_pagespeed_insights` (mobile). Run `check_hreflang` if relevant. A performance score under 50 on the homepage is a fix-this-week item, not a blocker.\n4. Check for launch-specific failures:\n   - `noindex` on pages that should rank\n   - canonicals pointing at a staging or old domain\n   - titles or descriptions still showing placeholder text, or identical across pages\n   - missing or broken structured data on key templates\n5. If the user is signed in, run `run_seo_audit` on the homepage for the full picture.\n\n## Output format\n\n```\nVerdict: GO | GO WITH FIXES | NO-GO\n\nBlockers (fix before launch)\n- <issue> on <url> - <exact fix>\n\nFix this week\n- <issue> - <fix>\n\nChecked and fine\n- <list>\n```\n\nA single blocker makes the verdict NO-GO. Be explicit about which item caused it.\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"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}