How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

seo - Skill - OpenSmartRoute

Name: seo
Author: iannuttall

Imported from iannuttall/seo (skills/seo/SKILL.md) via skills.sh. Install upstream with npx skills add iannuttall/seo --skill seo. Copyright stays with the author.

seo

seo reads Search Console, Google Analytics, Bing Webmaster Tools and Clicky data, crawls sites, checks live pages, and gets keyword and backlink data from DataForSEO or Ahrefs.

Use the MCP tools when they are connected (hosted at https://seoskill.dev/mcp, or local with seo mcp serve). Otherwise use the CLI: seo, or npx -y seo. Add --json for JSON.

seo crawl --url <url> needs no sign-in and works on any site, local and staging too. The other commands need the person's data: seo login prints a link for them to approve, then run it again.

CLI	MCP tool	Returns
`seo report --site <site>`	`seo_report`	Search Console overview and sections; with no site, last week across the sites in the weekly site audit beta
`seo page --url <url>`	`seo_page`	One URL: live page, index status, queries
`seo compare --site <site> --date <date>`	`seo_compare`	Before and after a date, with Google updates
`seo index --site <site>`	`seo_index`	Google's indexing reasons, labelled, and pages that lost their clicks
`seo research <action>`	`seo_research`	Keywords, SERP, competitors, backlinks, AI answer citations
`seo data --site <site>`	`seo_data`	Raw Search Console, Bing, Clicky or Google Analytics rows
`seo crawl --url <url>`	`seo_crawl`	Technical issues across a site
`seo internal-links --site <site>` or `--url <url>`	`seo_internal_links`	Links to add across a site, or to one page
`seo sites`	`seo_sites`	The properties the person can read

Each result ends with the command to run next. Start small and ask for more: a site, then a --section (section), then --detail rows or full. seo <command> --help shows the options.

Indexing reasons each week

seo index inspects known URLs in a fixed order (lost-click pages, Search Console pages by clicks, the sitemap, the rest), 100 by default, and labels each Google reason fix, check, expected or indexed from a live check. In the CLI or local MCP, --max-urls (max_urls) asks for more, up to today's quota, and reuses saved inspections up to 7 days old, so paging or --detail full costs no quota. Run it once for a baseline and keep the full result (--detail full). Run it again each week with the same number and compare by URL and reason: a new reason, or a URL that moved to fix, is what to report. seo keeps no history, so you store the results. Once this runs weekly, the person can turn off Search Console's indexing emails. For one URL from such an email, run seo page --url <url>.

Install seo and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "iannuttall-seo-seo", "kind": "skill", "name": "seo", "description": "Free Google Search Console MCP server and CLI for AI agents. Reads your real Search Console, Google Analytics, Bing Webmaster Tools and Clicky data, plus DataForSEO and Ahrefs keyword research. Use it for any SEO question - why Google traffic or clicks dropped, organic traffic decline, quick wins, low CTR, striking distance keywords, content decay and declining pages, keyword cannibalization, indexing and URL inspection, one page's queries, Google update impact, the questions people ask AI that show in Search Console, competitor keywords, backlinks, technical SEO crawls, redirects, internal links and client SEO reports. Returns facts from your own data, never guesses.", "publisher": "iannuttall", "version": "1.0.0", "capabilities": { "domains": [ "marketing" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Free Google Search Console MCP server and CLI for AI agents. Reads your real Search Console, Google Analytics, Bing Webmaster Tools and Clicky data, plus DataForSEO and Ahrefs keyword research. Use it for any SEO question - why Google traffic or clicks dropped, organic traffic decline, quick wins, low CTR, striking distance keywords, content decay and declining pages, keyword cannibalization, indexing and URL inspection, one page's queries, Google update impact, the questions people ask AI that show in Search Console, competitor keywords, backlinks, technical SEO crawls, redirects, internal links and client SEO reports. Returns facts from your own data, never guesses." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/iannuttall/seo", "path": "skills/seo/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/iannuttall/seo/seo", "key": "iannuttall/seo/skills/seo/SKILL.md" } }, "instructions": "# seo\n\n`seo` reads Search Console, Google Analytics, Bing Webmaster Tools and Clicky\ndata, crawls sites, checks live pages, and gets keyword and backlink data from\nDataForSEO or Ahrefs.\n\nUse the MCP tools when they are connected (hosted at\n`https://seoskill.dev/mcp`, or local with `seo mcp serve`). Otherwise use the\nCLI: `seo`, or `npx -y seo`. Add `--json` for JSON.\n\n`seo crawl --url <url>` needs no sign-in and works on any site, local and\nstaging too. The other commands need the person's data: `seo login` prints a\nlink for them to approve, then run it again.\n\n| CLI | MCP tool | Returns |\n|--", "cost": { "context_tokens": 643 } }

seo

About

seo

Indexing reasons each week

Install seo and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews