[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JC1P32X2D6X7AQJX15Q6FS":3,"skill-same:01M6JC1P32X2D6X7AQJX15Q6FS":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6JC1P32X2D6X7AQJX15Q6FS","ai-search-optimization",null,"Use when building or auditing a site for SEO visibility in AI Overviews, AI Mode, or generative search (AEO \u002F GEO \u002F answer-engine optimization), or when someone asks how to \"optimize for ChatGPT\u002FGemini\u002FAI search\", whether to add llms.txt or AI text files, how grounding \u002F query fan-out \u002F RAG pick pages, indexability and snippet-eligibility for AI features, structured data for AI, or agentic\u002FUCP commerce readiness. Codifies Google's official AI-optimization guidance and debunks AI-SEO myths.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fcontent\u002Fai-search-optimization\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"ai search optimization","search","Optimization","pick","features","mode","commerce","how to","ai-seo","query","optimize","files","google","text","how","data","rag","official","llms","agentic","2026-11-10 10:12:30",false,"---\nname: ai-search-optimization\ndescription: Use when building or auditing a site for SEO visibility in AI Overviews, AI Mode, or generative search (AEO \u002F GEO \u002F answer-engine optimization), or when someone asks how to \"optimize for ChatGPT\u002FGemini\u002FAI search\", whether to add llms.txt or AI text files, how grounding \u002F query fan-out \u002F RAG pick pages, indexability and snippet-eligibility for AI features, structured data for AI, or agentic\u002FUCP commerce readiness. Codifies Google's official AI-optimization guidance and debunks AI-SEO myths.\n---\n\n# AI Search Optimization (AEO \u002F GEO)\n\nGoogle's AI features (AI Overviews, AI Mode) use the **same crawl, index, and core ranking** as classic Search, plus grounding (RAG) and **query fan-out** (the model generates related sub-queries and pulls pages for each). There is **no separate AI ranking system**. Good classic SEO IS AI visibility. Source: developers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fai-optimization-guide.\n\n## Eligibility checklist (same as Search eligibility)\nA page can only surface in AI features if it is:\n- [ ] **Indexed** — not blocked by `noindex`, in the index, not a duplicate canonicalized away\n- [ ] **Crawlable** — `robots.txt` allows it; JS unblocked so rendered content is visible\n- [ ] **Publicly accessible** — no login\u002Fpaywall wall on the content that should rank\n- [ ] **Snippet-eligible** — no `nosnippet` \u002F `max-snippet:0` \u002F `data-nosnippet` on the content you want quoted\n- [ ] Meets Search **technical requirements** + **spam policies** (no cloaking, scaled-content abuse)\n\nNote: meeting every requirement does **not** guarantee crawl, index, or serving.\n\n## Content: people-first + unique POV\n- Write for humans. Offer a **unique point of view, first-hand experience, original data, or expertise** the model can't synthesize from everyone else.\n- Avoid commodity summaries an LLM could generate itself — those don't earn citation.\n- Avoid **scaled content abuse** (mass keyword\u002Flocation variations to manipulate).\n- No ideal length. Clear headings, sections, short paragraphs. Self-contained answers near the top help, but do **not** chunk content into tiny fragments.\n\n## DEBUNKED — do NOT waste effort on these\n| Myth | Reality |\n|------|---------|\n| `llms.txt` \u002F AI text files \u002F `ai.txt` | Google Search ignores them. Zero benefit. |\n| Special markdown \u002F \"machine-readable AI\" copies | Not used. Serve normal HTML. |\n| \"Chunk\" content into micro-pieces for the LLM | No benefit; harms readability. |\n| Write copy *specifically for* generative AI | Write for people; ranking follows. |\n| Chase inauthentic \"mentions\" \u002F brand name-drops | Not a ranking signal; can be spam. |\n| Separate \"AEO\u002FGEO ranking system\" to game | Doesn't exist. Same index + ranking. |\n\n## Structured data\nNot required for AI features, but **still recommended** — it powers overall SEO and rich-result eligibility. Use valid schema.org JSON-LD: `Organization`\u002F`LocalBusiness`, `Product`, `FAQPage`, `Article`, `BreadcrumbList`. (See `seo-technische-seo`.)\n\n## Multimodal\nHigh-quality, relevant images\u002Fvideo create **more opportunities** to appear in AI responses. Follow image\u002Fvideo SEO best practices (descriptive alt text, captions, structured data, fast delivery).\n\n## Local \u002F ecommerce\n- **Google Business Profile** feeds local info into AI responses (hours, location, reviews).\n- **Merchant Center** product feeds power product details in AI shopping answers.\n- **Business Agent** enables conversational experiences over your data.\n\n## Technical \u002F crawlability\nUnblock JS, use semantic human-readable HTML (imperfect HTML is fine), reduce duplicate content, fast + mobile page experience, clear separation of main content vs chrome\u002Fnav.\n\n## Agentic \u002F UCP (emerging)\nAI agents read sites via DOM, accessibility tree, and screenshots. Keep markup accessible and agent-friendly. The **Universal Commerce Protocol (UCP)** for agentic checkout is emerging — track it for ecommerce clients.\n\n## Example — commodity vs unique-POV (the difference that earns a citation)\n\n```text\nCOMMODITY (won't get cited — LLM already knows this):\n  H1: What is SEO?\n  \"SEO is the practice of optimizing a website to rank higher\n   in search engines. It includes keywords, backlinks, and\n   technical optimization.\"\n\nUNIQUE POV (citable — first-hand, specific, original):\n  H1: SEO results timeline: what 40 Dutch MKB sites taught us\n  \"Across 40 client sites we launched in 2025, position-1\n   rankings took a median of 4.5 months. The fastest (6 weeks)\n   all shared one trait: a LocalBusiness schema + 15+ Google\n   reviews live at launch. Here is the month-by-month data...\"\n```\n\n## Quick audit snippet (indexability)\n```bash\ncurl -sI https:\u002F\u002Fexample.com\u002Fpage | grep -i 'x-robots-tag'         # nosnippet\u002Fnoindex?\ncurl -s https:\u002F\u002Fexample.com\u002Fpage | grep -i '\u003Cmeta name=\"robots\"'    # page-level robots\ncurl -s https:\u002F\u002Fexample.com\u002Frobots.txt | grep -i 'disallow'         # crawl blocks\n# Then: Search Console > URL Inspection — confirm \"Indexed\" + rendered content visible.\n```\n\n## Cross-skill references\n- `seo-technische-seo` — crawl\u002Findex\u002Fschema foundation (prerequisite)\n- `seo-landing-page-audit` — apply this on landing\u002Fconversion pages\n- `coding\u002Fseo` — umbrella; this is the AI-features layer\n- `seo-bezoekersmagneet` \u002F `seo-keyword-strategie` — the same signals AI ranking uses\n","# AI Search Optimization (AEO \u002F GEO)\n\nGoogle's AI features (AI Overviews, AI Mode) use the **same crawl, index, and core ranking** as classic Search, plus grounding (RAG) and **query fan-out** (the model generates related sub-queries and pulls pages for each). There is **no separate AI ranking system**. Good classic SEO IS AI visibility. Source: developers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fai-optimization-guide.\n\n## Eligibility checklist (same as Search eligibility)\nA page can only surface in AI features if it is:\n- [ ] **Indexed** — not blocked by `noindex`, in the index, not a duplicate canonicalized away\n- [ ] **Crawlable** — `robots.txt` allows it; JS unblocked so rendered content is visible\n- [ ] **Publicly accessible** — no login\u002Fpaywall wall on the content that should rank\n- [ ] **Snippet-eligible** — no `nosnippet` \u002F `max-snippet:0` \u002F `data-nosnippet` on the content you want quoted\n- [ ] Meets Search **technical requirements** + **spam policies** (no cloaking, scaled-content abuse)\n\nNote: meeting every requirement does **not** guarantee crawl, index, or serving.\n\n## Content: people-first + unique POV\n- Write for humans. Offer a **unique point of view, first-hand experience, original data, or expertise** the model can't synthesize from everyone else.\n- Avoid commodity summaries an LLM could generate itself — those don't earn citation.\n- Avoid **scaled content abuse** (mass keyword\u002Flocation variations to manipulate).\n- No ideal length. Clear headings, sections, short paragraphs. Self-contained answers near the top help, but do **not** chunk content into tiny fragments.\n\n## DEBUNKED — do NOT waste effort on these\n| Myth | Reality |\n|------|---------|\n| `llms.txt` \u002F AI text files \u002F `ai.txt` | Google Search ignores them. Zero benefit. |\n| Special markdown \u002F \"machine-readable AI\" copies | Not used. Serve normal HTML. |\n| \"Chunk\" content into micro-pieces for the LLM | No benefit; harms readability. |\n| Write copy *specifically for* generative AI | Write for people; ranking follows. |\n| Chase inauthentic \"mentions\" \u002F brand name-drops | Not a ranking signal; can be spam. |\n| Separate \"AEO\u002FGEO ranking system\" to game | Doesn't exist. Same index + ranking. |\n\n## Structured data\nNot required for AI features, but **still recommended** — it powers overall SEO and rich-result eligibility. Use valid schema.org JSON-LD: `Organization`\u002F`LocalBusiness`, `Product`, `FAQPage`, `Article`, `BreadcrumbList`. (See `seo-technische-seo`.)\n\n## Multimodal\nHigh-quality, relevant images\u002Fvideo create **more opportunities** to appear in AI responses. Follow image\u002Fvideo SEO best practices (descriptive alt text, captions, structured data, fast delivery).\n\n## Local \u002F ecommerce\n- **Google Business Profile** feeds local info into AI responses (hours, location, reviews).\n- **Merchant Center** product feeds power product details in AI shopping answers.\n- **Business Agent** enables conversational experiences over your data.\n\n## Technical \u002F crawlability\nUnblock JS, use semantic human-readable HTML (imperfect HTML is fine), reduce duplicate content, fast + mobile page experience, clear separation of main content vs chrome\u002Fnav.\n\n## Agentic \u002F UCP (emerging)\nAI agents read sites via DOM, accessibility tree, and screenshots. Keep markup accessible and agent-friendly. The **Universal Commerce Protocol (UCP)** for agentic checkout is emerging — track it for ecommerce clients.\n\n## Example — commodity vs unique-POV (the difference that earns a citation)\n\n```text\nCOMMODITY (won't get cited — LLM already knows this):\n  H1: What is SEO?\n  \"SEO is the practice of optimizing a website to rank higher\n   in search engines. It includes keywords, backlinks, and\n   technical optimization.\"\n\nUNIQUE POV (citable — first-hand, specific, original):\n  H1: SEO results timeline: what 40 Dutch MKB sites taught us\n  \"Across 40 client sites we launched in 2025, position-1\n   rankings took a median of 4.5 months. The fastest (6 weeks)\n   all shared one trait: a LocalBusiness schema + 15+ Google\n   reviews live at launch. Here is the month-by-month data...\"\n```\n\n## Quick audit snippet (indexability)\n```bash\ncurl -sI https:\u002F\u002Fexample.com\u002Fpage | grep -i 'x-robots-tag'         # nosnippet\u002Fnoindex?\ncurl -s https:\u002F\u002Fexample.com\u002Fpage | grep -i '\u003Cmeta name=\"robots\"'    # page-level robots\ncurl -s https:\u002F\u002Fexample.com\u002Frobots.txt | grep -i 'disallow'         # crawl blocks\n# Then: Search Console > URL Inspection — confirm \"Indexed\" + rendered content visible.\n```\n\n## Cross-skill references\n- `seo-technische-seo` — crawl\u002Findex\u002Fschema foundation (prerequisite)\n- `seo-landing-page-audit` — apply this on landing\u002Fconversion pages\n- `coding\u002Fseo` — umbrella; this is the AI-features layer\n- `seo-bezoekersmagneet` \u002F `seo-keyword-strategie` — the same signals AI ranking uses\n",{"name":5,"description":7},"master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fcontent\u002Fai-search-optimization",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add S3YED\u002Fappie-kit --skill ai-search-optimization",{"tool":62,"command":63},"bunx","bunx skills add S3YED\u002Fappie-kit --skill ai-search-optimization",{"tool":65,"command":66},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill ai-search-optimization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fcontent\u002Fai-search-optimization\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"DISTRIBUTION.md","REFERENCE","参考文档",1586,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fcontent\u002Fai-search-optimization\u002FDISTRIBUTION.md",[77,109,143,168,199,224],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":90,"publishedAt":43},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[83,86,89],{"categoryNo":84,"categoryName":85,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":123,"publishedAt":43},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[115,118],{"categoryNo":116,"categoryName":117,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[124,42,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142],"design","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":151,"publishedAt":43},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[149,150],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},[42,152,128,153,154,155,130,156,24,157,158,159,160,161,162,163,164,165,166,167],"elements","agentic webdesign agent elements","MCP","ai agent","registry","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":178,"publishedAt":43},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[174,177],{"categoryNo":175,"categoryName":176,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":43},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[205],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223],"workflows","quality","software","software quality workflows","review","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification","for",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":237,"publishedAt":43},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[230,233,236],{"categoryNo":231,"categoryName":232,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":234,"categoryName":235,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[238,239,240,241,242,243,244,245,182,246,247,130,248,185,249,216,250,251,252,253],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]