| 开发者 |
navarroido
benwpco llmagnet |
|---|---|
| 更新时间 | 2026年8月25日 05:29 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/ or install via Plugins → Add Newhttps://your-site.com/llms.txtllms.txt is an emerging standard (like robots.txt for search engines) that helps AI models understand your site structure and content.
No. All file generation happens in the background with zero front-end impact.
ChatGPT, Claude, Perplexity, Gemini, Grok, Bing AI, Mistral, DeepSeek, Llama, and more.
Yes. On WordPress 6.9+ LLMagnet registers its analytics and llms.txt tools as WordPress abilities (under the llmagnet category). Install the official MCP Adapter plugin to let AI assistants like Claude securely query your AI SEO data using an Application Password. On older WordPress versions the plugin works normally; abilities are simply unavailable.
No. Core features work on any WordPress site. WooCommerce analytics are available for Plus and Enterprise plans.
It combines Bot Visibility (70%) – how often AI bots visit your product – with Content Quality (30%) – descriptions, tags, categories, and image ALT texts.
LLMagnet ships bundled translations for the plugin admin dashboard (menus, settings screens, React admin UI, and related notices). Supported locales: Hebrew (he_IL), Arabic (ar), and Spanish (Spain) (es_ES). Set your site language under Settings → General → Site Language; WordPress loads the matching translation files automatically. Brand names (LLMagnet) and technical terms (llms.txt, MCP, JSON-LD, product names, and similar) are kept in English. Additional languages can be contributed via the WordPress.org translation project or by adding custom .mo and .json files to the plugin's languages/ folder.
No. LLMagnet AI SEO Optimizer is a single-site plugin. It writes llms.txt, llms-full.txt, and the llms-docs/ Markdown files to the site root directory, which on a multisite network would be shared by every subsite - each subsite would overwrite the others' files. To prevent this, the plugin refuses to activate on multisite installations and shows an explanatory message instead. Please use it on a standalone (single-site) WordPress installation.
.md endpoint and the MCP content tools already refused protected content, but llms.txt, llms-full.txt and the /llms-docs/ markdown files did not — so a protected post's full body could be written to a publicly readable file. All export queries now exclude password-protected content, the writers refuse it individually, and protecting or unpublishing a post immediately deletes the markdown file it had already exported instead of leaving it until the next daily run.md URL is injected as an encoding / MediaObject field into Yoast SEO's own Article/WebPage schema piece, or into Rank Math's graph, rather than LLMagnet standing down and contributing nothing. Falls back to LLMagnet's own graph, or a minimal standalone block, when neither is present/.well-known/agent-skills/index.json with a $schema identifier and a SHA-256 digest per skill, alongside a real SKILL.md artifact that teaches agents how to read the site as markdown. The digest and the served file are computed from the same source, so they cannot drift apart. The previous /.well-known/agent-skills path keeps working and returns the same index/llms.txt and /llms-full.txt are now served by WordPress when the physical files are missing, so they work on hosts where the web root is not writable. An existing file always takes precedenceContent-Signal directive in robots.txt was emitted after a blank line, which ends a record — so it belonged to no user-agent group and parsers could ignore it. It is now emitted inside each AI crawler groupLink response headers advertise /.well-known/api-catalog and the Agent Skills index, both of which were already being served but never announcedmarkdown_url