[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C5KCKSQFTKC80SA9K2EDJS":3,"skill-same:01M7C5KCKSQFTKC80SA9K2EDJS":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":32,"commitSha":33,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":49},"01M7C5KCKSQFTKC80SA9K2EDJS","seo-schema",null,"Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says \"schema\", \"structured data\", \"rich results\", \"JSON-LD\", or \"markup\".","susantedit\u002Fclaude-skills","susantedit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192408503?v=4","01M7C4A1834JZ5GN4HZY57ZNV6","Susant edit","01M7C4A18RENMDYZV7918MQEZM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-schema\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-schema\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-schema\ndescription: >\n  Detect, validate, and generate Schema.org structured data. JSON-LD format\n  preferred. Use when user says \"schema\", \"structured data\", \"rich results\",\n  \"JSON-LD\", or \"markup\".\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.2.4\"\n  category: seo\n---\n\n# Schema Markup Analysis & Generation\n\n## Detection\n\n1. Scan page source for JSON-LD `\u003Cscript type=\"application\u002Fld+json\">`\n2. Check for Microdata (`itemscope`, `itemprop`)\n3. Check for RDFa (`typeof`, `property`)\n4. Always recommend JSON-LD as primary format (Google's stated preference)\n\n## Validation\n\n- Check required properties per schema type\n- Validate against Google's supported rich result types\n- Test for common errors:\n  - Missing @context\n  - Invalid @type\n  - Wrong data types\n  - Placeholder text\n  - Relative URLs (should be absolute)\n  - Invalid date formats\n- Flag deprecated types (see below)\n\n## Schema Type Status (as of June 2026)\n\nRead `..\u002Fseo\u002Freferences\u002Fschema-types.md` for the full list. Key rules:\n\n### ACTIVE (recommend freely):\nOrganization, LocalBusiness, SoftwareApplication, WebApplication, Product (with Certification markup as of April 2025), ProductGroup, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting\n\n### VIDEO & SPECIALIZED (recommend freely):\nBroadcastEvent, Clip, SeekToAction, SoftwareSourceCode\n\nSee `schema\u002Ftemplates.json` for ready-to-use JSON-LD templates for these types.\n\n> **JSON-LD and JavaScript rendering:** Per Google's December 2025 JS SEO guidance, structured data injected via JavaScript may face delayed processing. For time-sensitive markup (especially Product, Offer), include JSON-LD in the initial server-rendered HTML.\n\n### NO RICH RESULTS, KEEP IF USEFUL:\n- **FAQPage**: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov\u002Fhealth restriction). No Google SERP rich-result benefit; flag existing FAQPage at Info (not Critical) rather than removal. For genuine user Q&A pages, use **QAPage**.\n\n### DEPRECATED (never recommend):\n- **HowTo**: Rich results removed September 2023\n- **SpecialAnnouncement**: Deprecated July 31, 2025\n- **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 2025\n- **ClaimReview**: Retired from rich results June 2025\n- **VehicleListing**: Retired from rich results June 2025\n- **Practice Problem**: Deprecation notice 2025-11-05; Search Console \u002F Rich Results Test support removed 2026-01-06\n- **Book Actions**: Deprecated\u002Fremoved from Google rich results; do not recommend it for SERP features.\n- Search Console \u002F Rich Results Test \u002F appearance-filter support for CourseInfo, EstimatedSalary, LearningVideo, SpecialAnnouncement, VehicleListing was removed 2025-09-09; Practice Problem support was removed 2026-01-06.\n\n### Supported for Dataset Search only:\n- **Dataset**: Not discontinued; consumed by Google Dataset Search, with no Google Search rich-result surface. Don't advise removal as if it were killed.\n\n### Still supported (do not flag):\n- QAPage (expanded comment-thread properties 2026-03-24), DiscussionForumPosting, Education Q&A (Quiz \u002F `eduQuestionType=Flashcard`). For e-commerce, **hasAdultConsideration** (added 2026-05-22; value `https:\u002F\u002Fschema.org\u002FSexualContentConsideration`) is required for adult products.\n\n## Generation\n\nWhen generating schema for a page:\n1. Identify page type from content analysis\n2. Select appropriate schema type(s)\n3. Generate valid JSON-LD with all required + recommended properties\n4. Include only truthful, verifiable data. Use placeholders clearly marked for user to fill\n5. Validate output before presenting\n\n## Common Schema Templates\n\n### Organization\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Organization\",\n  \"name\": \"[Company Name]\",\n  \"url\": \"[Website URL]\",\n  \"logo\": \"[Logo URL]\",\n  \"contactPoint\": {\n    \"@type\": \"ContactPoint\",\n    \"telephone\": \"[Phone]\",\n    \"contactType\": \"customer service\"\n  },\n  \"sameAs\": [\n    \"[Facebook URL]\",\n    \"[LinkedIn URL]\",\n    \"[Twitter URL]\"\n  ]\n}\n```\n\n### LocalBusiness\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"LocalBusiness\",\n  \"name\": \"[Business Name]\",\n  \"address\": {\n    \"@type\": \"PostalAddress\",\n    \"streetAddress\": \"[Street]\",\n    \"addressLocality\": \"[City]\",\n    \"addressRegion\": \"[State]\",\n    \"postalCode\": \"[ZIP]\",\n    \"addressCountry\": \"US\"\n  },\n  \"telephone\": \"[Phone]\",\n  \"openingHours\": \"Mo-Fr 09:00-17:00\",\n  \"geo\": {\n    \"@type\": \"GeoCoordinates\",\n    \"latitude\": \"[Lat]\",\n    \"longitude\": \"[Long]\"\n  }\n}\n```\n\n### Article\u002FBlogPosting\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"[Title]\",\n  \"author\": {\n    \"@type\": \"Person\",\n    \"name\": \"[Author Name]\"\n  },\n  \"datePublished\": \"[YYYY-MM-DD]\",\n  \"dateModified\": \"[YYYY-MM-DD]\",\n  \"image\": \"[Image URL]\",\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"[Publisher]\",\n    \"logo\": {\n      \"@type\": \"ImageObject\",\n      \"url\": \"[Logo URL]\"\n    }\n  }\n}\n```\n\n## Output\n\n- `SCHEMA-REPORT.md`: detection and validation results\n- `generated-schema.json`: ready-to-use JSON-LD snippets\n\n### Validation Results\n| Schema | Type | Status | Issues |\n|--------|------|--------|--------|\n| ... | ... | ✅\u002F⚠️\u002F❌ | ... |\n\n### Recommendations\n- Missing schema opportunities\n- Validation fixes needed\n- Generated code for implementation\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |\n| No schema markup found | Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |\n| Invalid JSON-LD syntax | Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |\n| Deprecated schema type detected | Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |\n","# Schema Markup Analysis & Generation\n\n## Detection\n\n1. Scan page source for JSON-LD `\u003Cscript type=\"application\u002Fld+json\">`\n2. Check for Microdata (`itemscope`, `itemprop`)\n3. Check for RDFa (`typeof`, `property`)\n4. Always recommend JSON-LD as primary format (Google's stated preference)\n\n## Validation\n\n- Check required properties per schema type\n- Validate against Google's supported rich result types\n- Test for common errors:\n  - Missing @context\n  - Invalid @type\n  - Wrong data types\n  - Placeholder text\n  - Relative URLs (should be absolute)\n  - Invalid date formats\n- Flag deprecated types (see below)\n\n## Schema Type Status (as of June 2026)\n\nRead `..\u002Fseo\u002Freferences\u002Fschema-types.md` for the full list. Key rules:\n\n### ACTIVE (recommend freely):\nOrganization, LocalBusiness, SoftwareApplication, WebApplication, Product (with Certification markup as of April 2025), ProductGroup, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting\n\n### VIDEO & SPECIALIZED (recommend freely):\nBroadcastEvent, Clip, SeekToAction, SoftwareSourceCode\n\nSee `schema\u002Ftemplates.json` for ready-to-use JSON-LD templates for these types.\n\n> **JSON-LD and JavaScript rendering:** Per Google's December 2025 JS SEO guidance, structured data injected via JavaScript may face delayed processing. For time-sensitive markup (especially Product, Offer), include JSON-LD in the initial server-rendered HTML.\n\n### NO RICH RESULTS, KEEP IF USEFUL:\n- **FAQPage**: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov\u002Fhealth restriction). No Google SERP rich-result benefit; flag existing FAQPage at Info (not Critical) rather than removal. For genuine user Q&A pages, use **QAPage**.\n\n### DEPRECATED (never recommend):\n- **HowTo**: Rich results removed September 2023\n- **SpecialAnnouncement**: Deprecated July 31, 2025\n- **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 2025\n- **ClaimReview**: Retired from rich results June 2025\n- **VehicleListing**: Retired from rich results June 2025\n- **Practice Problem**: Deprecation notice 2025-11-05; Search Console \u002F Rich Results Test support removed 2026-01-06\n- **Book Actions**: Deprecated\u002Fremoved from Google rich results; do not recommend it for SERP features.\n- Search Console \u002F Rich Results Test \u002F appearance-filter support for CourseInfo, EstimatedSalary, LearningVideo, SpecialAnnouncement, VehicleListing was removed 2025-09-09; Practice Problem support was removed 2026-01-06.\n\n### Supported for Dataset Search only:\n- **Dataset**: Not discontinued; consumed by Google Dataset Search, with no Google Search rich-result surface. Don't advise removal as if it were killed.\n\n### Still supported (do not flag):\n- QAPage (expanded comment-thread properties 2026-03-24), DiscussionForumPosting, Education Q&A (Quiz \u002F `eduQuestionType=Flashcard`). For e-commerce, **hasAdultConsideration** (added 2026-05-22; value `https:\u002F\u002Fschema.org\u002FSexualContentConsideration`) is required for adult products.\n\n## Generation\n\nWhen generating schema for a page:\n1. Identify page type from content analysis\n2. Select appropriate schema type(s)\n3. Generate valid JSON-LD with all required + recommended properties\n4. Include only truthful, verifiable data. Use placeholders clearly marked for user to fill\n5. Validate output before presenting\n\n## Common Schema Templates\n\n### Organization\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Organization\",\n  \"name\": \"[Company Name]\",\n  \"url\": \"[Website URL]\",\n  \"logo\": \"[Logo URL]\",\n  \"contactPoint\": {\n    \"@type\": \"ContactPoint\",\n    \"telephone\": \"[Phone]\",\n    \"contactType\": \"customer service\"\n  },\n  \"sameAs\": [\n    \"[Facebook URL]\",\n    \"[LinkedIn URL]\",\n    \"[Twitter URL]\"\n  ]\n}\n```\n\n### LocalBusiness\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"LocalBusiness\",\n  \"name\": \"[Business Name]\",\n  \"address\": {\n    \"@type\": \"PostalAddress\",\n    \"streetAddress\": \"[Street]\",\n    \"addressLocality\": \"[City]\",\n    \"addressRegion\": \"[State]\",\n    \"postalCode\": \"[ZIP]\",\n    \"addressCountry\": \"US\"\n  },\n  \"telephone\": \"[Phone]\",\n  \"openingHours\": \"Mo-Fr 09:00-17:00\",\n  \"geo\": {\n    \"@type\": \"GeoCoordinates\",\n    \"latitude\": \"[Lat]\",\n    \"longitude\": \"[Long]\"\n  }\n}\n```\n\n### Article\u002FBlogPosting\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"[Title]\",\n  \"author\": {\n    \"@type\": \"Person\",\n    \"name\": \"[Author Name]\"\n  },\n  \"datePublished\": \"[YYYY-MM-DD]\",\n  \"dateModified\": \"[YYYY-MM-DD]\",\n  \"image\": \"[Image URL]\",\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"[Publisher]\",\n    \"logo\": {\n      \"@type\": \"ImageObject\",\n      \"url\": \"[Logo URL]\"\n    }\n  }\n}\n```\n\n## Output\n\n- `SCHEMA-REPORT.md`: detection and validation results\n- `generated-schema.json`: ready-to-use JSON-LD snippets\n\n### Validation Results\n| Schema | Type | Status | Issues |\n|--------|------|--------|--------|\n| ... | ... | ✅\u002F⚠️\u002F❌ | ... |\n\n### Recommendations\n- Missing schema opportunities\n- Validation fixes needed\n- Generated code for implementation\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |\n| No schema markup found | Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |\n| Invalid JSON-LD syntax | Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |\n| Deprecated schema type detected | Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |\n",{"name":5,"license":15,"metadata":25,"description":29,"argument-hint":30,"user-invocable":31},{"author":26,"version":27,"category":28},"AgriciDaniel","2.2.4","seo","Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says \"schema\", \"structured data\", \"rich results\", \"JSON-LD\", or \"markup\".\n","[url]",true,"main","e53589ef82615852f3c1465c81f84248be6a540d","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Fsusantedit","2026-10-12 22:39:26",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":31},[39,42,45],{"tool":40,"command":41},"npx","npx skills add susantedit\u002Fclaude-skills --skill seo-schema",{"tool":43,"command":44},"bunx","bunx skills add susantedit\u002Fclaude-skills --skill seo-schema",{"tool":46,"command":47},"pnpm","pnpm dlx skills add susantedit\u002Fclaude-skills --skill seo-schema","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-schema\u002FSKILL.md",[50,55],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",143,{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fdeprecated-types-2024-2026.md","REFERENCE","参考文档",5061,"https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-schema\u002Freferences\u002Fdeprecated-types-2024-2026.md",[62,70,77,85,92,100],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":20},"01M7C5XFR6FX0Z4GWM1Y9JFT1N","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":71,"name":28,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":20},"01M7C5QDRC7E3HCT7D7GEG0M6S","Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability, indexability, Core Web Vitals with INP), schema markup, content quality (E-E-A-T), image optimization, sitemap analysis, and GEO for AI Overviews\u002FChatGPT\u002FPerplexity. Industry detection for SaaS, e-commerce, local, publishers, agencies. Triggers on: SEO, audit, schema, Core Web Vitals, sitemap, E-E-A-T, AI Overviews, GEO, technical SEO, content quality, page speed.","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M7C5P67VHTWC2VXZQW9TY6TX","seo-technical","Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says \"technical SEO\", \"crawl issues\", \"robots.txt\", \"Core Web Vitals\", \"site speed\", or \"security headers\".","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-technical\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-technical\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":20},"01M7C5N0NK6KK4ZJB6E4XSG5QB","seo-sxo","Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says \"SXO\", \"search experience\", \"page type mismatch\", \"SERP analysis\", \"user story\", \"persona scoring\", \"why isn't my page ranking\", \"intent mismatch\", or \"wireframe\".","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-sxo\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M7C5MDWRE0SHEEWHD13P6D63","seo-sitemap","Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says \"sitemap\", \"generate sitemap\", \"sitemap issues\", or \"XML sitemap\".","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-sitemap\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-sitemap\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":20},"01M7C5JBZKT3ZQC382W7YBSZSW","seo-programmatic","Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says \"programmatic SEO\", \"pages at scale\", \"dynamic pages\", \"template pages\", \"generated pages\", or \"data-driven SEO\".","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-programmatic\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsusantedit\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fseo-programmatic\u002FSKILL.md",[],[]]