
Woodander checks websites and helps them get found.
Without an account, ask for an SEO check or a speed check of any public page: every finding says what is wrong, why it matters and how to fix it, and the speed check explains Google PageSpeed in plain words. Connect your Woodander account (sign in, no token) and the assistant can also read your site audits with their issues and fixes, your Search Console clicks, queries and pages, Google Analytics, tracked keywords and rankings, and your projects in Woodander Discover.
Example path →
https://woodander.com/mcpFree for anyone, no account needed: (an SEO check of any public page, every finding with why and how to fix it) and (Google PageSpeed of any public page, explained); a few a day, more with a connected Woodander account. Access to the connected person's Woodander data: their SEO sites (Search Console, Google Analytics, audits), Discover products and analytics, articles, and Google Tag Manager. Start with whoami and list_sites. Lists use cursor pagination: pass meta.next_cursor back as cursor. Errors carry a stable code before the message. For a guided site review use the seo_review prompt. Tag Manager: read with and ; changes ( ...) follow the mode the owner set for the site: Manual stores a proposal the owner applies, Hybrid changes the separate "Woodander" workspace, publishing and deletes wait for the owner's confirmation in the Workspace (you get a confirm_url; you can never confirm yourself). A "queued" answer has an id: poll . Keywords: keyword_ideas spends one of the plan's daily keyword lookups per new search (whoami shows the limits); tracked_keywords, rank_history and rank_overview read stored rank checks (positions, tags, target pages, volumes, visibility, estimated traffic and the followed competitors); reads the AI answers stored for the tracked prompts (mentions, places, competitors, sources). Backlinks: and read the weekly backlink reports of a site and of the competitors monitored for it (stored, never a live call). Discover (Woodander MCP for Discover): read with and ; changes (, , ...) follow the mode the owner set for the product: Manual stores a proposal, Hybrid edits the draft and waits for confirmation of anything public (Briefs, review replies), Autonomous also publishes those. Page edits always land in the draft and go live only after Woodander editors approve the submitted draft. Poll with the id. index_status reads which URLs Google has indexed and why not (stored URL Inspection results); uptime_status reads the uptime monitors (state, uptime percentages, incidents) and list_reports the white-label PDF reports and scheduled client reports. Phase 3 changes (, update_article_draft, run_audit, queue_search_console_sync, queue_ga4_sync, inspect_urls, , reject_autopilot_piece, , update_market_listing, pause_market_listing) follow the mode the owner set per module in Settings → AI activity: Manual stores a proposal the owner applies (confirm_url), Hybrid and Autonomous run what is reversible; making something public (approving a piece) waits for the owner except in Autonomous, and discarding a piece always waits. Media drafts stay private and go through the editors; Market listings are never sent for review by an agent. Poll with the id; lists a module's requests.
None in the store listings or on the server