| FMRS | 64 / 100 · C | 76 / 100 · B |
|---|
| Reliability | 10 / 20 | 13 / 20 |
|---|
| Security and permissions | 13 / 20 | 14 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - Site owners who want a clear audit and a ranked fix list without learning a heavy dashboard
- AI agents that need real crawl, Search Console, analytics, keyword, and competitor evidence through MCP
- Developers who want to embed the same report engine in a script, CI job, or TypeScript app
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Users expecting a hosted dashboard or cloud data storage — data stays on the local machine
- Users needing official endorsement from Google or an SEO vendor — the project is third-party maintained
- Users without a Node 22+ runtime
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Read the local config directory to store project profiles, crawl reports, and provider caches
- Access the system keychain for Google OAuth tokens, Bing API key, IndexNow key, and similar credentials, falling back to a private 0600 file
- Network requests to audited sites, Google Search Console, Google Analytics, Bing Webmaster, Clicky, and selected research providers when enabled
- Optional access to Chrome UX Report, IndexNow, and the npm registry
- Optional CI use of a Google service account JSON key and environment variables such as SEO_GOOGLE_SERVICE_ACCOUNT_JSON, SEO_BING_API_KEY, SEO_CLICKY_SITEKEY, and SEO_INDEXNOW_KEY
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - Optional external enrichment can send selected Search Console query or derived seed text to the chosen research provider only when explicitly enabled; it does not send Google credentials, property IDs, Search Console metrics, or Google Analytics rows
- When the system keychain is used, processes that cannot access it may read credentials readable by the same process user; without a keychain the CLI falls back to a private local file
- Research providers can charge for API requests; reports show estimated and actual cost, but spend limits are your responsibility
- Crawling issues many requests to the target site and may trigger access blocks; the report retains HTTP status, provider indicators, and access guidance
- User-agent names can be spoofed, so the server-log report describes request strings found in the log rather than verified crawler identity
- An accepted IndexNow request confirms receipt only and does not prove a URL was crawled, indexed, ranked, or shown
- Provider traffic, volume, difficulty, and visibility values are estimates and are not search-engine measured data
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Codex, Claude Code, Claude Desktop, Cursor | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 4 | 15 |
|---|