[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-1680":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":15,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":30,"readmeContent":31,"aiSummary":32,"trendingCount":16,"starSnapshotCount":16,"syncStatus":33,"lastSyncTime":34,"discoverSource":35},1680,"agentic-seo","addyosmani\u002Fagentic-seo","addyosmani","Agentic SEO \u002F Agentic Engine Optimization (AEO) tools","",null,"JavaScript",229,34,7,3,0,11,36,9,4.63,"MIT License",false,"main",true,[26,5,27,28,29],"agent-seo","agents","seo","seo-optimization","2026-06-12 02:00:31","# agentic-seo\n\n[![npm version](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002Fagentic-seo.svg)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fagentic-seo)\n[![npm downloads](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fdm\u002Fagentic-seo.svg)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fagentic-seo)\n[![license](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fl\u002Fagentic-seo.svg)](https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagentic-seo\u002Fblob\u002Fmain\u002FLICENSE)\n[![node](https:\u002F\u002Fimg.shields.io\u002Fnode\u002Fv\u002Fagentic-seo.svg)](https:\u002F\u002Fnodejs.org)\n[![GitHub stars](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002Faddyosmani\u002Fagentic-seo.svg?style=social)](https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagentic-seo)\n\nAudit your documentation and website for **Agentic Engine Optimization (AEO)**: ensure your content is discoverable, parseable, and useful to AI coding agents.\n\nAI coding agents like Claude Code, Cursor, Cline, and Aider consume documentation fundamentally differently from humans. They issue single HTTP requests, strip HTML, count tokens, and either use your content as context or silently discard it. `agentic-seo` checks whether your documentation is ready for this new reality.\n\n## Quick Start\n\n```bash\n# Audit current directory (auto-detects framework)\nnpx agentic-seo\n\n# Audit a specific directory\nnpx agentic-seo .\u002Fmy-docs-site\n\n# Audit a live URL\nnpx agentic-seo --url https:\u002F\u002Fdocs.example.com\n\n# Scaffold missing AEO files\nnpx agentic-seo init\n```\n\n## What It Checks\n\n`agentic-seo` runs 10 checks across 5 categories, scoring your site out of 100:\n\n### Discovery (25 points)\n| Check | Points | What it looks for |\n|---|---|---|\n| `robots-txt` | 10 | AI crawlers not blocked, explicit allow rules |\n| `llms-txt` | 10 | Structured index with descriptions and token counts |\n| `agents-md` | 5 | AGENTS.md\u002FCLAUDE.md with project context |\n\n### Content Structure (25 points)\n| Check | Points | What it looks for |\n|---|---|---|\n| `content-structure` | 15 | Heading hierarchy, semantic HTML, code examples, tables |\n| `markdown-availability` | 10 | Markdown source available, low HTML noise, no JS dependency |\n\n### Token Economics (25 points)\n| Check | Points | What it looks for |\n|---|---|---|\n| `token-budget` | 15 | Per-page token counts, no oversized pages |\n| `meta-tags` | 10 | AI-friendly meta tags, descriptions, token count metadata |\n\n### Capability Signaling (15 points)\n| Check | Points | What it looks for |\n|---|---|---|\n| `skill-md` | 10 | Capability descriptions, inputs, constraints |\n| `agent-permissions` | 5 | Agent access rules and rate limits |\n\n### UX Bridge (10 points)\n| Check | Points | What it looks for |\n|---|---|---|\n| `copy-for-ai` | 10 | Copy-for-AI buttons, copy-to-clipboard, raw view links |\n\n## Grading\n\n| Grade | Score | Meaning |\n|---|---|---|\n| **A** | 90-100% | Excellent agent readiness |\n| **B** | 75-89% | Good with minor improvements needed |\n| **C** | 60-74% | Functional but missing key signals |\n| **D** | 40-59% | Significant gaps in agent readiness |\n| **F** | 0-39% | Not optimized for AI agents |\n\n## Installation\n\n```bash\n# Global install\nnpm install -g agentic-seo\n\n# Or use npx (no install needed)\nnpx agentic-seo\n```\n\n## Usage\n\n### Audit a Local Directory\n\n```bash\n# Auto-detects framework (Next.js, Docusaurus, 11ty, Astro, Hugo, etc.)\nagentic-seo .\u002Fmy-project\n\n# Explicitly specify build output directory\nagentic-seo --output-dir .\u002Fmy-project\u002Fbuild\n```\n\nSupported frameworks: Next.js, Docusaurus, Eleventy, Astro, Hugo, Jekyll, Gatsby, VitePress, MkDocs, Sphinx, Vite.\n\n### Audit with Local Server\n\n```bash\n# Spin up a server and run HTTP-based checks\nagentic-seo --serve .\u002Fbuild\n```\n\n### Audit a Live URL\n\n```bash\nagentic-seo --url https:\u002F\u002Fdocs.example.com\n```\n\n### CI Mode\n\n```bash\n# Exit with code 1 if score below threshold\nagentic-seo --json --threshold 60\n\n# Just the score\nagentic-seo score --json\n```\n\n### Scaffold AEO Files\n\n```bash\n# Create missing llms.txt, AGENTS.md, skill.md, agent-permissions.json\nagentic-seo init\n```\n\n### Run Specific Checks\n\n```bash\nagentic-seo --checks robots-txt,llms-txt,token-budget\n```\n\n## Configuration\n\nCreate `.aeorc.json` in your project root, or add an `\"aeo\"` key to `package.json`:\n\n```json\n{\n  \"outputDir\": \"_site\",\n  \"checks\": {\n    \"token-budget\": { \"maxTokensPerPage\": 25000 },\n    \"robots-txt\": { \"requiredAgents\": [\"ClaudeBot\", \"GPTBot\"] }\n  },\n  \"ignore\": [\"**\u002Fnode_modules\u002F**\", \"**\u002Fvendor\u002F**\"],\n  \"threshold\": 60\n}\n```\n\n## Programmatic API\n\n```js\nimport { audit, auditWithServer } from 'agentic-seo';\n\n\u002F\u002F Audit a directory\nconst report = await audit('.\u002Fmy-site');\nconsole.log(report.grade);      \u002F\u002F 'B'\nconsole.log(report.percentage);  \u002F\u002F 78\nconsole.log(report.findings.errors); \u002F\u002F [{ severity: 'error', message: '...' }]\n\n\u002F\u002F Audit with a local server\nconst report2 = await auditWithServer('.\u002Fbuild');\n\n\u002F\u002F Access individual checkers\nimport { checkers } from 'agentic-seo';\n```\n\n## How It Works\n\n`agentic-seo` does not require an API key. All checks are structural and heuristic:\n\n1. **Framework Detection**: Auto-detects your build tool and locates the output directory\n2. **File Analysis**: Checks for `robots.txt`, `llms.txt`, `AGENTS.md`, `skill.md`, and `agent-permissions.json`\n3. **Content Analysis**: Parses HTML with Cheerio and Markdown with Remark to evaluate structure\n4. **Token Counting**: Uses `gpt-tokenizer` to measure real token counts per page\n5. **Agent Simulation**: Evaluates what AI agents would actually see when fetching your pages\n\n## CLI Options\n\n```\nOptions:\n  --url, -u         Audit a live URL\n  --serve, -s       Start local server and audit via HTTP\n  --json            Output results as JSON\n  --verbose, -v     Show all findings including info messages\n  --threshold, -t   Minimum score percentage (exit 1 if below)\n  --checks          Comma-separated checker IDs to run\n  --output-dir      Explicitly specify build output directory\n  --help            Show help\n  --version         Show version\n```\n\n## Where to Start\n\nIf you're new to AEO, here's the recommended priority order:\n\n1. **Audit robots.txt**: Prevents silent agent lockout (10 min)\n2. **Add llms.txt**: Immediate discoverability gains (a few hours)\n3. **Measure token counts**: High-leverage insight into page sizes (weekend project)\n4. **Write skill.md**: Start with your most-used APIs\n5. **Add \"Copy for AI\" buttons**: Low effort, high signal for human+agent workflows\n6. **Set up AI traffic monitoring**: Gives you data to justify further investment\n\n## Disclaimer\n\nThis is not an official Google project and is not endorsed by Google or Google Search. The concepts, checks, and recommendations in this tool are a best-effort community offering based on publicly available research and emerging practices around AI agent documentation consumption. Scores and recommendations should be taken as directional guidance, not as guarantees of any particular outcome.\n\n## License\n\nMIT\n","Agentic SEO 是一个用于优化网站和文档以适应AI编码代理的工具，确保内容对这些代理来说是可发现、可解析且有用的。该项目使用JavaScript编写，提供了一套全面的检查机制，覆盖了从发现性到用户体验桥接等五个关键领域，通过10项具体测试来评估站点得分，并据此提出改进建议。适用于希望提高其在线资源对于像Claude Code这样的AI助手可见性和可用性的开发者或组织。它不仅能够帮助识别潜在问题，还能生成必要的文件结构来支持更好的AEO实践。",2,"2026-06-11 02:45:23","CREATED_QUERY"]