| 开发者 | armstr13 |
|---|---|
| 更新时间 | 2026年11月4日 11:36 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[tallyrank_badge] in a footer, page or widget to show your verified AI visibility score. Use [tallyrank_badge theme="light"] on dark backgrounds.
No. The checks run on your server. If you connect a website-auditor.io account, the audit service reads your public pages the way a visitor would and asks AI assistants about your business by name; nothing private is sent.
Only if you ask it to. It reads your site and reports what it finds; it does not edit files, settings or your robots.txt. If you turn on Visits from AI, it adds website-auditor.io's tracking code to the head of your public pages until you turn it off. On the Fixes tab, a Pro member can apply the audit's security-header fixes (such as X-Content-Type-Options or Referrer-Policy), one at a time: the plugin then sends those headers on your public pages, unless a page already carries them. Remove any of them on the same tab, whether or not you still subscribe. Everything else from the audit is shown for you to apply yourself.
The plugin only applies conservative values, whatever the service sends: X-Frame-Options SAMEORIGIN (so page-builder previews keep working); a strict Referrer-Policy; a Permissions-Policy that only switches off camera, microphone and geolocation; an enforced Content-Security-Policy that only limits framing to your own site, fixes base URLs and upgrades insecure requests; a stricter policy that is report-only and reports nowhere; and Strict-Transport-Security of a day to a year, on this host alone, with no preload. Strict-Transport-Security and the enforced policy are offered only when your site address is HTTPS. Browsers remember Strict-Transport-Security for the time it names, so removing it does not undo it straight away: apply it only once your whole site works over HTTPS. If your host or a security plugin already sends a header, apply it there instead.
A page served from a full-page cache (a caching plugin, your host's cache or a CDN) skips WordPress, so it keeps the headers it was cached with until the cache is cleared. Clear it after applying or removing a header. A page that already carries the header keeps that one: this plugin does not add a header WordPress or another plugin has already set. It cannot see headers your web server or CDN adds, so if they add one, apply it there instead.
That's fine. Those plugins handle classic SEO, and several of them can add the business markup, sitemap and llms.txt these checks look for. This plugin checks what AI assistants need and measures whether they actually recommend you.
robots.txt and llms.txt only count at the root of a domain, so the checks read the files at your domain's root.
It asks four AI assistants several questions each about your business and waits for every answer. It runs in the background, so you can leave the page.
Blocking training crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot) is your choice and does not remove you from live answers. Blocking the answer-time crawlers or Googlebot/Bingbot does, which is why the checks treat those differently.