{ "skill_name": "seo", "evals": [ { "id": 1, "prompt": "Can you do an SEO audit of our SaaS website? We're getting about 2,000 organic visits/month but feel like we should be getting more. URL: https://example.com", "expected_output": "Should route to traditional.md. Should check for product-marketing-context.md first. Should ask clarifying questions about priority keywords, Search Console access, recent changes, and competitors. Should follow the audit framework priority order: Crawlability & Indexation, Technical Foundations, On-Page Optimization, Content Quality, Authority & Links. Should check robots.txt, XML sitemap, site architecture. Should evaluate title tags, meta descriptions, heading structure, and content optimization. Should NOT report on schema markup based solely on web_fetch (must note the detection limitation). Output should follow the Audit Report Structure: Executive Summary, Technical SEO Findings, On-Page SEO Findings, Content Findings, and Prioritized Action Plan.", "assertions": [ "Routes to traditional.md sub-skill", "Checks for product-marketing-context.md", "Asks clarifying questions about keywords, Search Console, recent changes", "Follows audit priority order: crawlability first, then technical, on-page, content, authority", "Checks robots.txt and XML sitemap", "Evaluates title tags, meta descriptions, heading structure", "Does NOT claim 'no schema found' based on web_fetch alone", "Notes schema markup detection limitation", "Output has Executive Summary", "Output has Prioritized Action Plan", "Each finding has Issue, Impact, Evidence, Fix, and Priority" ], "files": [] }, { "id": 2, "prompt": "Why am I not ranking for 'project management software'? We have a page targeting that keyword but it's stuck on page 3.", "expected_output": "Should route to traditional.md. Should trigger on the casual 'why am I not ranking' phrasing. Should investigate both on-page and off-page factors. On-page: check title tag, H1, URL alignment with keyword; evaluate content depth vs competitors; check for keyword cannibalization. Technical: check indexation status, canonical tags, crawlability. Content quality: assess E-E-A-T signals, content depth, user engagement. Should provide specific, actionable fixes organized by priority. Should mention competitive analysis against current top-ranking pages.", "assertions": [ "Routes to traditional.md sub-skill", "Triggers on casual 'why am I not ranking' phrasing", "Checks title tag, H1, URL alignment with target keyword", "Evaluates content depth vs competitors", "Checks for keyword cannibalization", "Checks indexation status and canonical tags", "Assesses E-E-A-T signals", "Mentions competitive analysis against top-ranking pages", "Provides actionable fixes organized by priority" ], "files": [] }, { "id": 3, "prompt": "We just migrated from WordPress to Next.js and our organic traffic dropped 40% in the last month. Help!", "expected_output": "Should route to traditional.md. Should treat this as an urgent migration diagnostic. Should immediately check: redirect mapping (301s from old URLs to new), canonical tags on new pages, robots.txt not blocking crawlers, XML sitemap submitted and updated, meta tags preserved. Should check for common migration issues: redirect chains/loops, soft 404s, lost internal links, changed URL structures without redirects. Should reference Search Console coverage report for indexation issues. Should provide a prioritized recovery plan with critical fixes first. Should mention monitoring timeline expectations (recovery can take weeks).", "assertions": [ "Routes to traditional.md sub-skill", "Treats as urgent migration diagnostic", "Checks redirect mapping (301s)", "Checks canonical tags on new pages", "Checks robots.txt not blocking crawlers", "Checks XML sitemap updated and submitted", "Checks for redirect chains or loops", "Checks for soft 404s", "References Search Console coverage report", "Provides prioritized recovery plan", "Mentions recovery timeline expectations" ], "files": [] }, { "id": 4, "prompt": "Review the technical SEO of our e-commerce site. We have about 50,000 products and use faceted navigation.", "expected_output": "Should route to traditional.md. Should focus on e-commerce-specific technical issues: faceted navigation creating duplicate content, crawl budget management for large product catalog, parameterized URLs, product schema markup (with the caveat about detection limitations). Should check for thin category pages, duplicate product descriptions, out-of-stock page handling. Should address crawl budget issues: pagination, infinite scroll handling, session IDs in URLs. Should provide structured findings with Impact ratings and specific fixes.", "assertions": [ "Routes to traditional.md sub-skill", "Addresses faceted navigation duplicate content", "Addresses crawl budget for large catalog", "Checks for parameterized URL issues", "Mentions product schema with detection limitation caveat", "Checks for thin category pages", "Checks for duplicate product descriptions", "Addresses out-of-stock page handling", "Addresses pagination and infinite scroll", "Findings include Impact ratings and specific fixes" ], "files": [] }, { "id": 5, "prompt": "Can you check our blog posts for on-page SEO issues? We publish 4 posts per week but traffic has been flat for 6 months.", "expected_output": "Should route to traditional.md. Should apply the Content/Blog Sites framework: check for outdated content not refreshed, keyword cannibalization, missing topical clustering, poor internal linking, missing author pages. Should audit on-page elements: title tags, meta descriptions, heading structure, keyword targeting per post. Should assess E-E-A-T signals for blog content. Should check for content depth issues and whether posts answer search intent. Should recommend a content audit process and provide a prioritized action plan for the existing content library.", "assertions": [ "Routes to traditional.md sub-skill", "Applies Content/Blog Sites framework", "Checks for outdated content", "Checks for keyword cannibalization", "Checks for topical clustering", "Checks for internal linking quality", "Checks for author pages and E-E-A-T signals", "Audits title tags, meta descriptions, heading structure", "Assesses whether content answers search intent", "Recommends content audit process", "Provides prioritized action plan" ], "files": [] }, { "id": 6, "prompt": "I run a local plumbing business with 3 locations. My website barely shows up when people search for 'plumber near me' in our areas. What's wrong?", "expected_output": "Should route to traditional.md. Should apply the Local Business site-type framework. Should check for: inconsistent NAP (Name, Address, Phone) across the site, missing local schema markup (with detection limitation caveat), Google Business Profile optimization, missing individual location pages for each of the 3 locations, and missing local content. Should also check standard technical and on-page factors. Should recommend local-specific fixes: location-specific pages with unique content, local schema on each, GBP optimization, citation consistency.", "assertions": [ "Routes to traditional.md sub-skill", "Applies Local Business framework", "Checks NAP consistency", "Checks for local schema markup with detection caveat", "Addresses Google Business Profile optimization", "Recommends individual location pages for each location", "Recommends local content strategy", "Checks standard technical SEO factors too", "Provides prioritized local SEO action plan" ], "files": [] }, { "id": 7, "prompt": "Our site loads really slowly, especially on mobile. Pages take 5-6 seconds to load. Is this hurting our SEO?", "expected_output": "Should route to traditional.md. Should focus on Site Speed and Core Web Vitals. Should explain CWV thresholds: LCP < 2.5s, INP < 200ms, CLS < 0.1, and that 5-6s load time is well above acceptable. Should investigate speed factors: server response time (TTFB), image optimization, JavaScript execution, CSS delivery, caching headers, CDN usage, font loading. Should recommend specific tools: PageSpeed Insights, WebPageTest, Chrome DevTools, Search Console CWV report. Should explain that yes, page speed is a ranking factor and directly impacts SEO. Should provide prioritized fixes.", "assertions": [ "Routes to traditional.md sub-skill", "Focuses on Core Web Vitals", "Explains CWV thresholds (LCP, INP, CLS)", "Identifies 5-6s as well above acceptable", "Investigates specific speed factors", "Recommends specific diagnostic tools", "Confirms page speed impacts SEO rankings", "Provides prioritized speed fixes", "Addresses mobile-specific performance" ], "files": [] }, { "id": 8, "prompt": "I want to add FAQ schema to my product pages. Can you help me set that up?", "expected_output": "Should route to traditional.md. Should recognize this is a schema markup implementation task. May briefly mention that FAQ schema can enable rich results, then help implement it directly with JSON-LD examples. Should not attempt a full SEO audit for this request.", "assertions": [ "Routes to traditional.md sub-skill", "Recognizes this as schema markup implementation", "Provides practical JSON-LD guidance", "Does not attempt a full SEO audit", "May briefly mention FAQ schema benefits" ], "files": [] }, { "id": 9, "prompt": "How do I make sure our SaaS product shows up in AI search results? We're a project management tool and we keep getting left out of ChatGPT and Perplexity recommendations when people ask about project management software.", "expected_output": "Should route to ai-seo.md. Should check for product-marketing-context.md first. Should apply the three pillars framework: Structure (make content extractable), Authority (make content citable), Presence (be where AI looks). Should run through the AI Visibility Audit checklist across platforms (Google AI Overviews, ChatGPT, Perplexity, etc.). Should check content extractability (clear definitions, structured comparisons, statistics). Should reference Princeton GEO research findings (citations improve visibility +40%, statistics +37%). Should check AI bot access in robots.txt. Should provide a prioritized action plan.", "assertions": [ "Routes to ai-seo.md sub-skill", "Checks for product-marketing-context.md", "Applies three pillars framework (Structure, Authority, Presence)", "Runs AI Visibility Audit across platforms", "Checks content extractability", "References Princeton GEO research findings", "Checks AI bot access in robots.txt", "Provides prioritized action plan" ], "files": [] }, { "id": 10, "prompt": "Should we block AI crawlers like GPTBot and PerplexityBot in our robots.txt? We're worried about content theft.", "expected_output": "Should route to ai-seo.md. Should address the AI bot access question directly. Should explain the tradeoff: blocking AI bots prevents training on your content but also prevents AI platforms from citing and recommending you. Should reference the specific bots and their purposes (GPTBot, Google-Extended, PerplexityBot, ClaudeBot, etc.). Should provide the recommended robots.txt configuration. Should explain that blocking may hurt AI visibility more than it protects content. Should provide a nuanced recommendation based on business goals.", "assertions": [ "Routes to ai-seo.md sub-skill", "Addresses the blocking tradeoff directly", "Explains impact on AI visibility vs content protection", "Lists specific AI bot user agents", "Provides recommended robots.txt configuration", "Gives nuanced recommendation based on business goals", "Explains what each bot does" ], "files": [] }, { "id": 11, "prompt": "What kind of content gets cited most by AI systems? We want to create content specifically optimized for AI search.", "expected_output": "Should route to ai-seo.md. Should reference the content types that get cited most, including comparisons (~33% of AI citations), definitive guides (~15%), and other high-citation content types. Should explain why these formats work (they provide the structured, extractable, authoritative information AI systems need). Should provide specific recommendations for creating AI-optimized content: clear definitions, structured data, original statistics, comparison tables, expert quotes. Should reference the Princeton GEO research on what increases citation probability.", "assertions": [ "Routes to ai-seo.md sub-skill", "References specific content types with citation rates", "Mentions comparisons as highest-cited format", "Explains why these formats work for AI", "Provides specific content creation recommendations", "References Princeton GEO research", "Mentions structured data, statistics, and clear definitions" ], "files": [] }, { "id": 12, "prompt": "we noticed our competitors are showing up in google AI overviews but we're not. what do we need to change?", "expected_output": "Should route to ai-seo.md. Should trigger on casual phrasing. Should focus specifically on Google AI Overviews visibility. Should explain how AI Overviews selects sources (authoritative, well-structured, directly answers queries). Should run through the Structure pillar checklist: content extractability, heading hierarchy, answer-first format, structured data. Should check Authority signals: domain authority, citations, E-E-A-T. Should recommend specific content structure changes. Should suggest monitoring approach.", "assertions": [ "Routes to ai-seo.md sub-skill", "Triggers on casual phrasing", "Focuses on Google AI Overviews specifically", "Explains how AI Overviews selects sources", "Checks Structure pillar (extractability, headings, answer-first)", "Checks Authority signals", "Recommends specific content structure changes", "Suggests monitoring approach" ], "files": [] }, { "id": 13, "prompt": "Can you audit our website for AI search readiness? We want to know how visible we are across ChatGPT, Perplexity, Google AI Overviews, and other AI platforms.", "expected_output": "Should route to ai-seo.md. Should run the full AI Visibility Audit. Should check each platform in the landscape (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot). Should evaluate all three pillars: Structure (content extractability, JSON-LD, clear definitions), Authority (citations, backlinks, E-E-A-T signals), Presence (AI bot access, platform-specific factors). Should provide findings organized by pillar. Should provide a prioritized action plan with specific fixes.", "assertions": [ "Routes to ai-seo.md sub-skill", "Runs full AI Visibility Audit", "Checks multiple AI platforms", "Evaluates all three pillars (Structure, Authority, Presence)", "Checks content extractability", "Checks AI bot access", "Provides findings organized by pillar", "Provides prioritized action plan" ], "files": [] }, { "id": 14, "prompt": "Our organic search traffic has dropped 30% this quarter. Can you do a full SEO audit to figure out what's going on?", "expected_output": "Should route to traditional.md (this is a traditional SEO audit request, not AI SEO). Should recognize traffic drops as a traditional SEO concern. May mention AI search as one factor to investigate but should focus on traditional audit framework: crawlability, technical foundations, on-page optimization, and content quality.", "assertions": [ "Routes to traditional.md sub-skill", "Recognizes this as a traditional SEO audit request", "Does not attempt a full traditional SEO audit using AI SEO patterns", "May mention AI search as one factor to consider" ], "files": [] } ] }