Claude SEO tools are external SEO services that Claude calls through a connector built on the Model Context Protocol. Once a connector is on, you ask in plain language and Claude runs the matching tool: an index check, an indexing task, a backlink check or a rank report. Some of those calls only read data; others change your account and spend tokens, and that difference decides what you can run freely and what needs a budget.
The examples below use one indexing service as a concrete case, but the same questions apply to any SEO connector: what does each tool read, what does it change, and when does Claude ask before running it.
Four SEO jobs you can hand to Claude
- Index status checks – is a URL in Google, Yandex or Bing?
- Indexing submission – send URLs that are not indexed to Google or Yandex.
- Backlink liveness – do the donor pages you paid for still link to you?
- Rank tracking – where does the site appear in Google for its keywords?
Index status checks
An index check answers one question per URL: indexed or not. A single task takes up to 10,000 URLs and returns two lists, indexed and not indexed, with page titles for Google. Creating the check task spends tokens, so it is not one of the free read-only calls; reading its report afterwards is free.
Example prompt: “Check whether these URLs are in Google’s index: https://example.com/page-1, https://example.com/page-2.”
Indexing submission
Submission sends URLs to Google or Yandex, up to 10,000 per task. Google tasks are pay-per-indexed: tokens for URLs that do not get indexed come back automatically. A Google task can also be spread over 2–30 days with drip feed instead of sending every URL on the same day.
Example prompt: “Create a Google indexing task for the not-indexed URLs from that report, drip feed over 7 days.”
This call creates a task and spends tokens, so Claude shows an approval request before it runs.
Backlink liveness checks
A liveness check is not backlink discovery. You give the tool the donor pages, and it opens each one to confirm it still links to your domains. For every donor it reports the HTTP status, anchor text, nofollow flag, Moz Domain Authority and spam score; one check covers up to 50 target domains.
Example prompt: “Check whether these donor pages still link to example.com: https://donor-one.com/article, https://donor-two.com/post.”
Starting the check spends tokens; reading its status and report does not.
Rank tracking
Rank tracking covers desktop Google: projects with up to 5 regions and 10 competitors, positions and changes since the last check, trend history up to 90 checks, and whether Google’s AI Overview appears and cites the site. Creating a project and adding keywords is free. Running a check is paid, and its cost is shown in advance with rank_tracker_get_check_cost.
Free prompt: “Show current positions for my project.” Paid prompt: “Run a rank check for my project.”
Free reads vs token-spending calls
Take the SpeedyIndex MCP connector as an example. Its remote server exposes 22 tools. Fifteen only read data and are free, among them get_balance, list_tasks, get_task_status, get_task_report, get_backlink_check_report, rank_tracker_get_positions and rank_tracker_get_trend. Seven change the account, and five of those spend tokens: create_indexing_task, submit_single_url, create_index_check_task, create_backlink_check_task and rank_tracker_start_check.
| Job | Example prompt | Reads or changes the account | Spends tokens |
|---|---|---|---|
| Balance | “What is my SpeedyIndex balance?” | Reads | No |
| Task list and status | “List my tasks and their status.” | Reads | No |
| Index check | “Check these 100 URLs in Google.” | Changes (creates a task) | Yes |
| Indexing submission | “Submit these URLs to Google.” | Changes (creates a task) | Yes; Google tasks are pay-per-indexed |
| Backlink liveness | “Check whether these donor pages still link to example.com.” | Changes (creates a task) | Yes |
| Rank positions and trend | “Show positions and trend for my project.” | Reads | No |
| Rank check | “Run a rank check for my project.” | Changes (starts a check) | Yes |
How approvals work
Claude asks for approval before tool calls; you can set tools you trust to “Always allow”. The seven account-changing SpeedyIndex tools, including the five that spend tokens, always ask unless you set them to “Always allow”, so keep that setting for read-only tools if you want a confirmation before every paid step. Claude can only reach what you permitted during sign-in.
Video: adding the SpeedyIndex connector in Claude. YouTube
Connecting the server
In Claude (web or desktop) open Plugins, choose Add, then Add custom connector, name it SpeedyIndex and paste https://mcp.speedyindex.com/mcp. Select Continue and Connect; a SpeedyIndex sign-in page opens where you paste the API key from your account, so the key is never typed into the chat. Then turn the connector on in a chat via “+” → Connectors and ask for your balance. If you see tokens and credits, it works.
The connector itself is free; tasks are paid with SpeedyIndex tokens without a subscription, and new accounts get 100 free tokens.
FAQ
Which calls cost nothing?
The 15 read-only tools: balance, task lists, task status and reports, backlink check status and reports, rank positions, trend, keyword details, project lists, locations, limits and check cost. Creating a Rank Tracker project and adding keywords is also free.
Will Claude run a paid task without asking?
Not unless you allow it. The account-changing tools ask for confirmation each time unless you have set them to “Always allow”.
Can I use it on the Free Claude plan?
Yes. Custom connectors work on every Claude plan; the Free plan allows one custom connector, so a second one at the same time needs a paid plan.