audit_seoLABSCO SUMMARY
Auditing for answer engines is a different job from auditing for search, and treating them as one is the common mistake.
A page can rank well and still be useless to an assistant summarising it — buried claims, no structure, facts that only exist in an image. Checking both criteria in one pass is the right shape now that a growing share of readers arrive through a model rather than a result list. Pairing the tools with a skill file is the other good idea: the tools tell the agent what it can measure, the skill tells it what to do about the answer.
What it is
An SEO server that also covers AEO — answer engine optimisation, meaning how a page fares when an assistant rather than a search engine reads it. Its companion skill is installed separately; install_skill returns the installation commands for ranki-seo-skills.
What you get
- An audit of any URL across both search and answer-engine criteria
- Sitemap generation
- A separately installed companion skill file that hands the agent the working method, not just the tools
Requirements
For local stdio, have Node.js 20 or later and npx on your PATH. Fifteen tools need no Ranki.io account or key. The seven tools that read your Ranki.io account data—called “paid bridge tools” by Ranki.io—require RANKI_API_KEY in your environment, obtained at app.ranki.io/developer.
Setup effort
One command — npx -y @ranki.io/seo-aeo-mcp
USE CASES
01
Auditing a page
Search and answer-engine criteria in one pass.
02
Fixing discoverability
Generate the sitemap the audit calls for.
22 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
audit_aeoaudit_hidden_pagesaudit_speedaudit_core_web_vitalsoptimize_imagesgenerate_sitemap_xmlgenerate_llms_txtgenerate_robots_txtseo_starter_kitfind_topic_ideasfind_keyword_gappropose_titles_metasexplain_seo_termsinstall_skillget_accountlist_projectslist_articlesget_articlelist_rank_trackinglist_gsc_keywordsai_visibilityBEFORE YOU INSTALL
What to know first
Tools you get
22 tools when we connected. Ranki.io calls get_account, list_projects, list_articles, get_article, list_rank_tracking, list_gsc_keywords and ai_visibility “paid bridge tools”; they require RANKI_API_KEY, while the other 15 tools do not.
Requires
npx on PATH
Optional
RANKI_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @ranki.io/seo-aeo-mcpMCP Clients
Claude Desktop, Claude Code
JSON
{
"mcpServers": {
"ranki": {
"command": "npx",
"args": [
"-y",
"@ranki.io/seo-aeo-mcp"
],
"env": {
"RANKI_API_KEY": "<YOUR_RANKI_API_KEY>"
}
}
}
}
