Claude Website Auditor connectorWhat Claude can audit for you with Website Auditor.
The Claude Website Auditor connector exposes 14 tools. 12 read: scores, audits, changes, rival comparisons, fixes, a schema draft. 2 write, and only to start or stop the weekly tracking of a site. 0 undocumented. It is a Claude Desktop extension, not a web connector.
Verified Trustpilot reviews · AI, automation & growth agency
What Claude learns about your site's AI visibility
Ask Claude whether AI assistants name your business, and the extension answers with data: a visibility score from 0 to 100, a breakdown per engine (ChatGPT, Perplexity, Claude, Gemini) and the competitor that shows up in your place. It also runs a classic technical audit covering SEO, security headers, broken links and performance, then tracks the score over time.
A score you can explain. get_ai_visibility returns the overall score, the per-engine split and the rival named instead of you, with 7- and 30-day trend data. When the result carries a name warning, the business name behind that score could not be verified.
A fix list, ranked. get_recommendations lists prioritized actions, each with why it matters, expected impact and effort, and generate_schema drafts structured data (JSON-LD, the code that describes a page to search engines) whose name placeholders you replace yourself.
Before and after, on a schedule. track_site adds weekly re-audits, and get_changes reports how the score moved between two comparable snapshots, or says why no comparison holds.
What it will not do: change your website. Every tool reads or reports, apart from the two that switch monitoring on and off; the schema arrives as a draft for you to place. Without an API key, only the sample report works. Weekly tracking runs on the publisher's side; Claude itself only acts while it answers you. Automation platforms for other recurring jobs are on the Integrations hub, and other connectors on the Claude integrations page.
Five words before you install Website Auditor
Five terms that come back throughout this page, explained once.
- Connector
- The link between Claude and an outside service. Here it is an extension installed in Claude Desktop that talks to the Website Auditor API.
- Tool
- One named thing the extension lets Claude do, like run_audit or track_site. Claude picks the ones it needs as it answers.
- Approval
- What Claude waits for from you before it runs a step that alters something, such as switching a site's monitoring on.
- Directory
- The official catalogue where each connector has a sheet: publisher, purpose, and the named list of tools it exposes.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude call an outside service such as Website Auditor.
Set up Website Auditor in Claude Desktop in three steps
- 01
Add the extension in Claude Desktop
The directory sheet lists Website Auditor as a local extension that works with Claude Desktop only. Open Claude Desktop, go through Customize then Connectors, find Website Auditor and add it. On a Team or Enterprise workspace, an Owner or Primary Owner enables it first.
- 02
Enter your API key, or skip it
In the extension's settings, the API key is optional at install. Left empty, only the sample report answers; every audit, check and comparison needs a key, and minting one takes an active Website Auditor subscription.
- 03
Restart Claude Desktop
The key is read once, when the extension starts. After you set or change it, quit Claude Desktop and reopen it, then ask for a sample audit to confirm the tools respond.
The 14 Website Auditor tools, by what they do
Website Auditor gives Claude 14 tools: 12 that read your account, 2 that change something in it.
Two groups: what Claude reads and reports, and the two tools that change your monitoring setup. The publisher describes all fourteen in its official manifest. Names stay exactly as Claude shows them.
- 12 read
- 2 write
What Claude reads and reports (12)
12 toolsTwelve tools that audit, score, compare and summarize, without changing your website.
get_sample_audit
Hands back a complete demo report for example.com, built in the exact shape of a real audit: scored summary, per-test results and the visibility breakdown across ChatGPT, Perplexity, Claude and Gemini. It works with no API key and no setup.
get_ai_visibility
Measures how visible a site is to AI assistants right now: an overall score from 0 to 100, one score per engine and the rival that appears instead. Trend data over 7 and 30 days comes from stored snapshots.
run_audit
Runs a one-time audit covering AI visibility, SEO, security headers, broken links and performance, then returns a scored summary by category and a link to the full report.
get_changes
Reports how a site's visibility score moved, but only between two snapshots that asked the same question with the same business name and queries. When no such pair exists, it explains why instead of giving a number.
compare_competitors
Puts a site head-to-head with named competitors on AI visibility, returning each one's score and the places where they appear and the site does not. It caps the work to your remaining daily quota and lists any rival it had to skip.
list_tracked_sites
Lists the domains currently under scheduled monitoring, each with its cadence and whether it is active, plus how many slots are used and how many remain.
get_monitoring_status
Gives a one-glance summary across every tracked site: latest score of each series, date of the last scheduled run, when the next one runs, and the latest like-for-like movement of the score, or the reason there is none.
get_benchmark
Places a site's AI visibility against its industry and location, returning a percentile, the peer median, the sample size and a short position summary rather than an absolute number.
get_recommendations
Produces a ranked list of specific actions to raise a site's visibility and audit scores, each explained with why it matters, the expected impact and the effort involved. Like the benchmark, it sits behind Website Auditor's own paid upgrade.
generate_schema
Drafts JSON-LD structured data tailored to a site, with placement notes on what to replace first and where to embed it. The name placeholders must be swapped for real names you confirm; the publisher forbids guessing them from the domain.
get_report
Returns a shareable report link plus the HTML snippet of the embeddable "Audited by Website Auditor" badge for a site. Upgrading the Website Auditor subscription is what unlocks it.
check_upgrade_status
Reports your own standing with Website Auditor: tier, status, period end and what upgrading would unlock. It works with any valid API key and uses none of your audit quota.
What Claude changes (2)
2 toolsTwo tools that start or stop monitoring, which the publisher marks as writing tracking state. No source describes a confirmation for them: the general rule below applies.
track_site
Approval: see the ruleSwitches on, or off, weekly monitoring of a site's AI visibility. Its weekly re-audits join the history that get_changes compares, while get_changes itself also accepts a domain that is not tracked.
untrack_site
Approval: see the ruleEnds the weekly monitoring of a site and frees one monitoring slot. Running it twice changes nothing more, since the publisher calls it idempotent.
What Claude asks before it changes your monitoring
Claude's baseline: each action it carries out on an account for you waits for your explicit yes, asked right in the chat.
In an organization on Team or Enterprise, it is up to the owners to let members skip the prompt for certain actions, and they can limit what a connector may do for the whole organization. Claude works with the access you give it and nothing more: here, that means the API key entered in the extension, which the publisher says is stored in the operating system's keychain by Claude Desktop. No tool in this extension reaches the audited website itself.
Which Claude plans include Website Auditor
None of the 819 sheets in the official directory shows availability by plan. For any single connector, that answer is published nowhere: a real gap in the catalogue.
What is published is the general rule: a desktop extension like this one installs in Claude Desktop; remote connectors, by contrast, are open to everyone on Claude, mobile, Claude Desktop and Cowork. On Team and Enterprise, an Owner or Primary Owner enables a connector before members use it. Check the extension's sheet in the official directory for its current state. The Website Auditor subscription is a separate matter, sold by the publisher.
Where Website Auditor stops
A connector is not an automation. Claude calls these tools while it answers you; the weekly re-audits are run by the publisher's service, not by Claude.
The tool list is an observed floor, not a promise: administrators can open actions that no public sheet shows. The verification badge in the directory is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools or vouch for how they behave. Only the publisher, Kevin Armstrong / SpikeyCoder, documents this extension; no Claude help page covers it. Treat its claims as the publisher's own.
Need help connecting Website Auditor to Claude?
A person reads every message.