For Claude Code
Check your pages from Claude Code.
Claude Code can generate thousands of pages in an afternoon. Connect Indexing Guard and the same agent can check them: what goes in the sitemap, what was held back, and what to fix in the data.
Connect
Store your key as INDEXING_GUARD_KEY first. The server address is https://guard.myartmyrules.com/mcp and it speaks Streamable HTTP. Run this once in your terminal:
claude mcp add --transport http indexing-guard https://guard.myartmyrules.com/mcp \ --header "Authorization: Bearer $INDEXING_GUARD_KEY"
Things to ask
- "Check the pages in dist/routes.json with Indexing Guard and tell me what was held back."
- "Which pages are missing a source? Add the source links from our data and check again."
What it can and can't do
check_pages: send a build's pages; get counts, every page held back with its reason, page warnings and the input to fix.list_runs: the last 50 checks with their counts.- It can't touch keys, plans or billing, and every check counts against your daily limit.
Other clients are on the AI agents page. For your build step, see the docs. Need a key? Pick a plan.
Questions
Do I need a paid plan to use Claude Code with Indexing Guard?
No. Your key works on a free trial first: up to 100 URLs per build and 3 builds a day, with counts only. The page-by-page reasons come with a paid plan.
What can Claude Code do with it?
Check a build's pages, read what was held back and the input to fix for each reason, and compare recent builds. It can't change your account, keys or billing.
Where does my key go?
In an environment variable named INDEXING_GUARD_KEY. Don't paste it into a chat.
Search engines decide what they index and rank. Indexing Guard controls what you submit. Questions: terrell@myartmyrules.com