Index Harmony
| 开发者 | indexharmony |
|---|---|
| 更新时间 | 2026年8月6日 17:25 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Install → run the setup wizard → done. No key, no account, no paid tier: every module and every measurement screen in this plugin is free and fully usable.
Index Harmony prepares your WordPress site for AI assistants, answer engines and their crawlers (ChatGPT, Claude, Perplexity, Gemini and others) without touching your files or content — and then shows you what actually happened. Every fix is virtual and reversible: turn a module off and it disappears without a trace.
What makes it different: most plugins in this space stop at generating llms.txt. Index Harmony pairs the output side with a first-party measurement side that no search-console integration can see: its own AI-bot traffic log with cryptographic-grade bot verification (official vendor IP lists), daily per-page counters, a per-page evidence panel showing which engine fetched which page on demand, a crawl-freshness funnel, an attention-decay radar, recovery for 404 URLs that assistants invent, a change log that marks every GEO-affecting setting change on your traffic chart, plus an agent-facing Site MCP endpoint and WordPress Abilities/WebMCP surfaces. llms.txt is one of its 18 modules, not the product.
All 18 fix modules (free, no key needed):
- llms.txt + llms-full.txt (virtual endpoints, refreshed daily; hand-pick the highlighted pages or edit the file body yourself)
- AI bot manager for robots.txt (explicit allow rules for 24 AI bots; your existing rules are kept intact)
- JSON-LD schema injector (Organization / WebSite / Article / FAQ / Breadcrumb / Product) — defers to Yoast, Rank Math, AIOSEO and SEOPress to avoid duplicates
- Meta completer (description / Open Graph / Twitter — only when no SEO plugin handles it)
- WordPress core sitemap enablement + robots.txt declaration
- /.well-known/security.txt
- WooCommerce product feed + Product schema completeness
- hreflang auditor (reports only — it never writes a file and never emits an hreflang tag)
- /AGENTS.md — a site usage guide for agents (virtual)
- Markdown negotiation (Accept: text/markdown or ?format=md)
- .well-known discovery endpoints (api-catalog RFC 9727; mcp.json and agent-skills only when configured — no fake manifests)
- Agent-discovery Link headers + robots.txt Content-Signal declaration
- AI bot traffic log (which bot visited when)
- AI policy publishing (ai.txt + TDMRep + Content-Signal header)
- Security headers — six optional response headers (X-Content-Type-Options, Referrer-Policy, Permissions-Policy, HSTS, CSP-Report-Only, X-Frame-Options); all off by default and picked one by one under Settings → Advanced
- IndexNow instant indexing (Bing/Yandex/Seznam/Naver — opt-in)
- WebMCP (in-browser agent surface for your site's public information)
- AI traffic share (opt-in daily channel counters)
- Bot traffic dashboard — a 30-day chart and per-bot breakdown of AI crawler visits
- Bot verification (opt-in) — once enabled, downloads public bot IP lists once a day to flag spoofed bots; no visitor data leaves your site
- Bot blocking & spike alerts (opt-in) — pick the bots to watch, then turn blocking on whenever you decide to, behind an explicit confirmation; the panel recommends a 7-day monitoring window first and warns you if you enable it earlier, but nothing is time-locked and you can stop blocking with one click; optional email when traffic spikes
- Page analysis — daily per-page counters (GDPR-neutral: no IPs, no user agents) feed a per-page evidence panel showing which engine fetched which page on demand, a crawl-freshness funnel (which pages changed after the last crawl), and a 28-day attention-decay radar for pages AI is losing interest in
- AI-404 phantom URL recovery — a report of URLs assistants think exist (404 hits with an AI user-agent or AI-platform referrer), the closest real page suggested by edit distance, and an optional per-row 301 applied ONLY to AI-originated requests
- GEO change log — every visibility-affecting setting change is marked on the traffic chart with an honest before/after delta (correlation, not causation)
- Bot health alarms — a silence sentinel for regular crawlers that go quiet and a spoof-surge guard with an explicitly confirmed, one-click "403 spoofed-only" switch
- Page readiness score + Triage — a per-page content-readiness sub-score with an in-editor meta box and a site-wide triage view
- Weekly (or daily) digest email (opt-in) — a summary of bot traffic, fading pages and your weakest pages
- No files are written — everything is served virtually and switches off without a trace.
- No cloaking — humans and bots see the same content; only the format may differ when a client asks for it.
- No fake manifests — discovery files are published only when they describe something real.
- No upsell surfaces — this plugin never asks you for a key and never stores one.
屏幕截图:
常见问题:
Does it modify my files or content?
No. Nothing is written to your files and your post content is never changed. All endpoints (llms.txt, AGENTS.md, the product feed…) are served virtually. Disable a module and it is gone without a trace.
Do I need a key or an account?
No. There is no key field anywhere in this plugin, nothing to activate and nothing to buy. All 18 modules and every measurement screen work as soon as you switch them on.
Where does the scan result appear?
On the service's own page, in the browser tab that opens when you press "Scan". The plugin does not fetch the report back into wp-admin and does not store it.
Does the plugin send data anywhere on its own?
With everything at its defaults, no: there is no telemetry and no outbound call happens on its own. If you enable an opt-in module, it makes only the calls described in the "External services" section — IndexNow submits a URL when you publish or update a post, and bot verification downloads public crawler IP lists about once a day. The plugin never phones home.
Will it conflict with my SEO plugin?
No. When Yoast SEO, Rank Math, AIOSEO or SEOPress is detected, Index Harmony defers the overlapping schema/meta output to them and tells you so in the panel.
Is this cloaking?
No. Visitors and bots always receive the same content. Markdown negotiation only changes the format when a client explicitly asks for it.
更新日志:
0.9.38
- First release on WordPress.org: 18 fix modules, setup wizard, tabbed settings, 17-language admin panel, virtual & traceless fix architecture — no key, no account, no paid tier anywhere in the plugin.
- Measurement & insights: bot traffic dashboard, opt-in bot verification, bot blocking & spike alerts, page readiness score + Triage, and an opt-in weekly/daily digest.
- Page-analysis suite: GDPR-neutral daily per-page counters powering a per-page AI evidence panel, a crawl-freshness funnel, a 28-day attention-decay radar, AI-404 phantom URL recovery with optional AI-only 301s, a GEO change log with before/after impact, and bot health alarms (silence sentinel + spoof-surge guard with an explicitly confirmed spoofed-only 403).
- Content scope & curation: opt other plugins' public content types into your llms.txt, AGENTS.md and page scoring, hand-pick which pages your llms.txt highlights with a live search picker, or edit the published llms.txt body directly.
- Security headers now have a selection screen (Settings → Advanced): six optional response headers, each off by default and switched on one at a time.
- Guideline & hardening pass: this build contains no licensing, unlock or update-check code at all, and nothing in it is limited by time, by usage or by anything you could pay for — bot blocking in particular is never time-locked, it only recommends a monitoring window and warns you if you switch it on early. It also defers sitemaps and Product schema to your SEO plugin and WooCommerce correctly, adds cache invalidation for llms.txt and the product feed, moves audits off visitor requests, and registers a personal-data exporter/eraser for author profile fields.
- Polish pass: working Amazonbot IP verification, panel-language number/date formatting on measurement screens, an honest warning (plus withheld advertising) for .well-known endpoints on subdirectory installs (RFC 8615), and Index Harmony-branded public identifiers (REST index-harmony/v1, block index-harmony/nap, index_harmony_* shortcodes).