बिबरन
Scan your WordPress site for broken links, missing image alt text, missing SEO meta descriptions and accessibility problems — and fix them without leaving the report.
Activate the plugin and it starts scanning straight away. No token, no API key, no Node.js, no terminal. About thirty seconds later you get a health score out of 100 and a list of real problems on your own site.
What it finds
Twelve checks, run one at a time so nothing times out.
Broken link checker — checks the links in your recent posts and pages and reports only the ones that are genuinely gone. Only a 404 or 410 counts. Anything ambiguous is retried a different way and left alone rather than reported as a false alarm.
Missing alt text — images your visitors using screen readers cannot see, and search engines cannot read.
Missing meta descriptions — published posts and pages with no SEO description, for Yoast SEO and RankMath.
Accessibility basics — links that announce nothing to a screen reader, “click here” links, more than one main heading, and headings that skip a level. Structural checks only; it does not claim to be a full WCAG audit.
Images missing dimensions — the cause of pages that jump around while they load, which Google measures as a Core Web Vital.
Images missing lazy loading — pictures further down a post that something has opted out, so visitors download them before they are ever seen.
Oversized media — files big enough to slow your pages down, with the space you would get back.
Orphaned files — uploads that nothing on your site appears to use.
Thin content — published pages with very few words. Read with judgement: a contact page is supposed to be short, and pages built from a shortcode, gallery or embed are left out.
Plugin and core health — pending updates, an unsupported PHP version, missing HTTPS, errors visible to visitors, a stalled cron.
Exposed WordPress files — readme.html, license.txt and a debug log left publicly readable. The first hands an attacker your exact version; the last can contain server paths and credentials.
XML-RPC — reported as a notice, with the tradeoff stated plainly. It is a brute-force vector, but the WordPress mobile app and Jetpack need it, so this is only worth turning off if you use neither. Sites running Jetpack are skipped entirely.
Fix it from the report
A list of complaints is not much use on its own. Write alt text straight into the report, replace a dead link, or trash a file you no longer need — one row at a time, with the score climbing as you go.
No AI and no API key required for any of it.
Your score is kept over time, so you can watch the site improve, and you can have a short report emailed to you when something changes.
Send the report to a client
A report is more useful when the person who needs to act on it can read it.
- PDF — opens a clean, printable page and your browser’s own print dialog. Choose “Save as PDF”. No bloated PDF library bundled into the plugin to do a job your browser already does well.
- CSV — every issue as a row: check, severity, issue, context, link and object ID. Opens correctly in Excel and Google Sheets, in any language.
- A shareable link — a public web page your client can open without a login, with an expiry you choose: 7, 30 or 90 days. There is no never-expires option.
Shared reports are redacted on purpose. They show the score, each check by name, and how many issues it found. They never show file names, page addresses, server paths, post or media IDs, edit links, or your plugin, theme, PHP and WordPress versions — and the two security checks are left out entirely, because publishing those would be publishing a vulnerability report about your own server. The page tells you exactly what a recipient will and will not see before you create the link, every link can be revoked instantly, and the report is a snapshot: re-scanning your site never changes what you already sent.
Optional: let an AI assistant do the work
Everything above works on its own. Connecting an AI assistant is an upgrade, not a requirement.
Built on the open standard Model Context Protocol (MCP) developed by Anthropic, this plugin exposes safely-gated capabilities to clients like Claude Desktop, Cursor, VS Code and Windsurf, so they can work on your site in plain language.
- Write and edit content — draft, edit, format or publish posts and pages.
- SEO audits — scan Yoast or RankMath metadata, optimise it for a keyword, update titles and descriptions.
- WooCommerce — list low-stock items, draft products, check recent orders, summarise sales.
- Diagnostics — inspect PHP error logs, check loopback status, look up site details.
- Zero-config setup — no hand-editing hidden JSON files. Copy one command from your dashboard, paste it into your terminal, and it connects.
Included modules: Content (9 abilities), SEO (6), Diagnostics (7), Media (6), Users (5), WooCommerce (12, registers only when WooCommerce is active). That is 33 abilities on a standard install, or 45 with WooCommerce. Every one is an individual switch, and a token can only call what you allow.
Security
- API tokens are SHA-256 hashed — the raw token is shown once and never stored.
- Every token is scoped to specific abilities. A token can only do what you explicitly allow.
- Optional IP allowlist restricts a token to specific addresses or CIDR ranges.
- Tokens are sent via the Authorization header, never in the URL.
- Every action is written to a searchable audit log with configurable retention.
What you need
The site scan and inline fixing need none of the following. These apply only if you choose to connect an AI assistant:
- Node.js — the desktop bridge (
mcp-remote) runs on your own computer. - HTTPS — so your API tokens stay encrypted in transit.
- Administrator access — to generate tokens and toggle module permissions.
Help translate this plugin
My Site Hand is available in English and Bengali. If you speak another language, you can help — no coding needed:
https://translate.wordpress.org/projects/wp-plugins/my-site-hand/
New to translating? Start here: https://make.wordpress.org/polyglots/handbook/translating/first-steps/
External Services
Link Checker (SEO Module)
When the check-broken-links ability is called via the MCP API, this plugin sends HTTP HEAD requests to URLs found in your post content to verify they are reachable. No personal user data is transmitted — only a standard HTTP request is made to each URL being checked. This is triggered only when explicitly called by an authorized API token holder.
Link Checker (Site Health scan)
The Broken Links check in the Site Health scan sends HTTP HEAD requests (and, where a server refuses HEAD, a single ranged GET) to the links found in your 50 most recent published posts and pages, to see whether they still resolve. The request identifies this plugin and your site URL in its user agent. No personal user data is transmitted. Results are cached for 12 hours. This runs when you start a scan from the admin, and during the scheduled scan if you leave that enabled — on sites with more than 500 published posts the link check is skipped on the schedule. Turning scheduled reports off in My Site Hand Settings stops the scheduled scan entirely.
Requests this plugin makes to your own site
The Exposed WordPress Files and XML-RPC checks ask your own site, over HTTP, whether /readme.html, /license.txt, /wp-config-sample.php, /wp-content/debug.log and /xmlrpc.php answer to an anonymous visitor. These are loopback requests to your own domain, not to any third party, and no data is sent in them. Results are cached for 12 hours. If your host blocks loopback requests, both checks report that they could not run rather than reporting your files as safe.
Shared report links
Creating a share link stores a redacted snapshot of your scan in your own database and serves it from your own site at a tokenized URL. Nothing is uploaded anywhere. The page is sent with X-Robots-Tag: noindex, nofollow, every link expires, and you can revoke one at any time.
No data is sent to any third-party analytics or tracking service by this plugin.
Screenshots










Installation
Search for My Site Hand in your WordPress dashboard, install, and activate it. You land on Site Health and the first scan starts by itself. That is the whole setup.
Connecting an AI assistant is optional, and fully guided:
- Generate a token — go to My Site Hand > API Tokens and click Create Token. Give it a label, e.g. “Claude Desktop”.
- Open the How to Use page in your dashboard.
- Run two commands — one installs the
mcp-remotebridge on your computer, the second (auto-generated, with your token) connects it. - Restart your AI client and start talking to your site.
FAQ
-
Is this a broken link checker?
-
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.
-
Will it report links that are not really broken?
-
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.
-
Can it find images with no alt text?
-
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.
-
Does it check accessibility?
-
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.
-
Does it work with Yoast SEO and RankMath?
-
Yes. The missing meta description check reads whichever of the two is active.
-
Do I need an AI assistant, an API key or a token to use this?
-
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.
-
Does the scan slow my site down?
-
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.
-
Should I turn XML-RPC off because the scan mentions it?
-
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.
-
Do I need Node.js?
-
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. -
Is this plugin secure?
-
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.
-
What AI applications are supported?
-
Any client that supports the Model Context Protocol (MCP): Claude Desktop, Cursor, VS Code via an MCP extension, and Windsurf.
-
Does this send my data to third-party servers?
-
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.
समीक्षा
Contributors & Developers
“My Site Hand – Broken Link Checker, Alt Text & Site Health Audit” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “My Site Hand – Broken Link Checker, Alt Text & Site Health Audit” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.2.0 – 6 September 2026
- New: six more checks — image dimensions, lazy loading, exposed WordPress files, XML-RPC, thin content, and accessibility basics. Twelve checks in total.
- New: PDF and CSV export. Send a client the report without giving them a login.
- New: shareable report links with an expiry you choose. Public reports show scores and counts only — never paths, IDs, versions or plugin names.
- New: Bengali translation, and the plugin is now fully ready for community translation.
- Improved: Score weighting was retuned for twelve checks, so an ordinary site still lands in a usable range rather than being marked critical for having twice as much measured.
1.1.0 – 26 August 2026
- New: Site Health Scan — one click, no setup. Find broken links, missing alt text, missing meta descriptions, oversized media, orphaned files, and plugin or core health problems.
- New: Quick Fix — repair issues inline from the report. No AI or API key required.
- New: Score history and trend so you can watch your site improve.
- New: Optional weekly email report. It stays quiet when there is nothing new to say.
- New: Plugin checks now appear in WordPress’s own Tools Site Health.
- Improved: Activation now takes you straight to a scan of your site instead of setup instructions. The MCP connection steps are still there, collapsed on the Dashboard as an optional upgrade.
- New: Redesigned admin interface. The left sidebar is replaced by a brand row and a tab bar, and every page now has a numbered index so you can jump straight to the section you came for.
- Improved: A single accent colour, flat surfaces, and a monospaced type scale make status, counts, and destructive actions easier to read at a glance.
- Improved: The dashboard now surfaces what needs your attention — missing HTTPS, tokens expiring within 30 days, or a stopped endpoint.
- Fixed: The “Trust proxy headers” and “Allow token in URL query string” settings did not save. Both now work.
- Fixed: The settings page could submit itself and blank stored options if you pressed Enter in a text field. Settings save individually as you change them, so the form has been removed.
1.0.2 – 24 August 2026
- Security: Tokens created without an explicit ability selection no longer default to full access. Existing tokens are migrated automatically and continue to work unchanged.
- Security: API tokens are no longer accepted via URL query string by default. Use the Authorization header instead. An opt-in setting remains available for clients that cannot send headers.
- New: Optional per-token IP allowlist with CIDR range support.
- New: Trusted proxy setting for sites behind Cloudflare or a reverse proxy.
- Improved: Token creation now clearly distinguishes full access from limited access.
- Fixed: Database schema version was not being stored after an upgrade, causing unnecessary schema checks on every page load.
1.0.1 – 9 June 2026
- Added a “Suggest a Feature” page so users can submit feature requests directly to the developer’s email.
- Improved email deliverability with dynamic “From” headers and real-time failure log captures.
- Styled and aligned the admin menu icon in the sidebar with a white background and centered flex alignment.
- Added automatic redirection to the dashboard immediately upon plugin activation for faster onboarding.
- Added a “How to Use” shortcut link directly on the Plugins page.
1.0.0
- Official initial release.
- Automated zero-config setup for Claude Desktop.
- Support for Content, SEO (Yoast, RankMath), WooCommerce, and Diagnostics.
- Secure token management and real-time audit logs.
