| 开发者 | builtbytanin |
|---|---|
| 更新时间 | 2026年9月23日 20:50 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
mcp-remote) runs on your own computer.mcp-remote bridge on your computer, the second (auto-generated, with your token) connects it.Yes, among other things. It checks the links in your 50 most recent published posts and pages and reports the ones that are genuinely gone. Unlike a dedicated link crawler it does not run continuously in the background, so it will not slow your site down — it runs when you start it, or on a schedule you choose.
It tries hard not to. Only 404 and 410 count as gone. Anything ambiguous — a 403, a 405, a server error — is retried a different way, and if it is still unclear the link is not reported at all. A single false alarm would make you distrust the whole report.
Yes, and you can write the alt text straight into the report without opening the media library or the post editor. The score updates as you go.
It checks four structural problems: links that announce nothing to a screen reader, "click here" link text, more than one H1 on a page, and heading levels that skip. It is a useful first pass, not a full WCAG audit, and it does not claim to be one.
Yes. The missing meta description check reads whichever of the two is active.
No. The scan and inline fixing work on their own, with nothing to install and nothing to configure. Connecting Claude, Cursor or VS Code is an optional upgrade.
No. It runs only when you start it, or on the schedule you choose, and it works in small batches so no single request runs long enough to time out. Scheduled scans skip the link check on sites with more than 500 published posts.
The score, the name of each check, and how many issues each one found. Nothing else. No file names, no page addresses, no server paths, no post or media IDs, no edit links, and no plugin, theme, PHP or WordPress version numbers. The two security checks are excluded from public reports entirely. Every link expires — 7, 30 or 90 days, your choice — and you can revoke one at any time.
No, and deliberately so. It opens a clean printable page and your browser's own print dialog, where you choose "Save as PDF". Bundling a PDF library would multiply the size of the plugin to do something every browser already does well.
Only if you do not use the WordPress mobile app, Jetpack, or a desktop publishing tool — all of which need it. That is why it is reported as a notice rather than a warning, and why sites running Jetpack are skipped entirely. Disabling it on a site that needs it breaks that site, which is worse than leaving it alone.
Not for the scan or inline fixing. Node.js is only needed if you choose to connect an AI assistant, because the desktop bridge (mcp-remote) runs on your own computer.
API tokens are SHA-256 hashed and shown once. You choose exactly which abilities each token may call, and you can revoke access instantly. The built-in audit log records what ran, who ran it, and when.
Any client that supports the Model Context Protocol (MCP): Claude Desktop, Cursor, VS Code via an MCP extension, and Windsurf.
No. MCP communication happens directly between your local AI client and your WordPress site. The plugin does not track, collect or store your data on external servers. The only outbound requests are the link checks described under External Services.