Opis
Demo: TasteWP
LLMagnet is AI analytics for WordPress. It tracks how often ChatGPT, Claude, Perplexity, and other AI engines crawl your site and send people back — then helps you raise that visibility for LLMs and agents.
It puts the technical layer in place: /llms.txt, markdown, and the discovery files those systems expect. You see which pages they visited, get an AI Visibility Score, and get concrete suggestions to improve it.
Connect MCP and work with that data from Claude Code, Codex, Cursor, ChatGPT, and more.
Works with Rank Math, Yoast, and the rest of your SEO stack. Scores and recommendations sit inside Gutenberg and Elementor.
What’s in LLMagnet Pro
LLMagnet Pro is a separate plugin at llmagnet.com. Install it next to this one. This plugin stays fully functional without it. Pro adds:
* Schema – Scan, generate, and publish JSON-LD so search engines and AI can read the page
* WebMCP – The live in-page runtime so agents can use the site’s tools, not only discover them
* Reports – Scheduled email reports and alerts when AI traffic changes
* WooCommerce – Catalog discovery for agents (no cart or checkout) and product-level AI analytics
* Images – Image export in llms.txt, plus ALT text help
* One-click fixes – Apply Agent Ready repairs from the audit instead of doing them by hand
How It Works
- Install & Activate – LLMagnet starts working immediately with guided onboarding
- Configure Content – Choose which post types to include
- Auto-Generation – llms.txt and llms-full.txt are served dynamically at /llms.txt and /llms-full.txt; markdown at {permalink}.md
- Track AI Visits – See which bots discover your content
- Connect Google (optional) – Link GA4 and Search Console to see AI referral traffic and search queries
- Follow Recommendations – Get actionable suggestions to improve AI visibility
SEO Plugin Compatibility
LLMagnet works seamlessly alongside your existing SEO setup:
* Rank Math & Yoast SEO – Excludes noindex posts from llms.txt, llms-full.txt, and markdown exports when those plugins mark content noindex
* Smart robots.txt Management – Registers llms.txt (and llms-full.txt when generation is enabled)
* Elementor Editor Integration – AI visibility scores in the Elementor editor. Per-page JSON-LD schema fields ship with LLMagnet Pro
* No conflicts with your current SEO workflow
Agent Ready
LLMagnet sets up the layer agents need to find, read, and use your site:
* Well-known discovery – agent-card.json, agent-skills, mcp.json, security.txt, and the API catalog
* WebMCP – /.well-known/mcp.json and agent skills so in-page agents can discover what the site can do
* Markdown endpoints – Clean {permalink}.md for every public page
* robots.txt & IndexNow – AI crawler rules, Content-Signal, and publish pings so engines recrawl faster
* Headers – Link headers for llms.txt and the agent card; optional security headers and Open Graph fill
* Agent Ready audit – A score with pass/warn/fail checks and suggested fixes
AIO / GEO / AEO Benefits
- AIO (AI Optimization) – Structured content that AI models can parse accurately
- GEO (Generative Engine Optimization) – Better representation in AI-generated answers
- AEO (Answer Engine Optimization) – Increased chances of being cited as a source
External services
The services below run only after an administrator connects, enables, or opts in. None of them run for anonymous site visitors. Bot logos are bundled. Usage analytics, product emails, and the news feed are separate opt-ins, all off by default.
Google (Analytics 4 & Search Console)
Used after you connect Google from Connections, so the dashboard can read AI referral and Search Console metrics you already have. The plugin sends OAuth requests to accounts.google.com and read-only API calls to googleapis.com / analyticsdata.googleapis.com / searchconsole.googleapis.com (sessions, landing pages, clicks, queries). Tokens stay encrypted on your site. Terms: https://policies.google.com/terms · Privacy: https://policies.google.com/privacy
IndexNow (api.indexnow.org)
Used after you enable IndexNow on Agent Ready, and only if Rank Math, AIOSEO, or Yoast Premium is not already pinging. On publish, update, or unpublish of included content, the plugin sends your host name, verification key, and changed public URLs (up to 500) to https://api.indexnow.org/indexnow so Bing and other IndexNow engines can recrawl faster. No visitor, post, or personal data. Terms: https://www.indexnow.org/terms · Privacy: https://privacy.microsoft.com/en-us/privacystatement · Engines: https://www.indexnow.org/
Agent Skills (schemas.agentskills.io)
Used after you enable Agent Skills discovery. The plugin serves /.well-known/agent-skills/index.json from your site and writes the public schema URL schemas.agentskills.io/discovery/0.2.0/schema.json into that file. Nothing is fetched from or sent to schemas.agentskills.io.
LLMagnet API (api.llmagnet.com)
Used for hosted Google OAuth (site URL, redirect URL, one-time tickets, and refresh tokens) and, after email opt-in, lifecycle contact/events. Production host is api.llmagnet.com; Google routes may fall back to llmagnet-api-server.vercel.app. Both are operated by LLMagnet. Terms: https://llmagnet.com/terms/ · Privacy: https://llmagnet.com/privacy-policy/ · Cookies: https://llmagnet.com/cookie-policy/
Brevo (via api.llmagnet.com)
Used after email opt-in (llmagnet_email_consent) for product lifecycle emails. The plugin posts admin email, site name, site URL, plugin version, onboarding status, and visibility score to api.llmagnet.com/lifecycle/* — never to api.brevo.com, and no Brevo key is shipped. Turning consent off sends an unsubscribe. Terms: https://www.brevo.com/legal/termsofuse/ · Privacy: https://www.brevo.com/legal/privacypolicy/
Mixpanel
Used after telemetry opt-in for in-plugin admin usage (page views, clicks, onboarding) plus plugin/WordPress versions, site language, and WooCommerce yes/no, identified by domain. Admin email and site URL are not sent. Session replay and autocapture are off. EU endpoint: api-eu.mixpanel.com. Terms: https://mixpanel.com/legal/terms-of-use/ · Privacy: https://mixpanel.com/legal/privacy-policy/
LLMagnet news feed (llmagnet-wp-news.vercel.app)
Used after news-feed opt-in (llmagnet_news_feed_consent) to load product news/promo JSON for administrators only. A generic GET with User-Agent: LLMagnet/{version} — no site URL, email, or identifiers. Images may load from *.public.blob.vercel-storage.com on LLMagnet admin screens. Turn off under System Information Privacy & Data. Terms: https://llmagnet.com/terms/ · Privacy: https://llmagnet.com/privacy-policy/
Feedback
Used only when an administrator submits the in-plugin form. wp_mail sends the message to support@llmagnet.com; if diagnostics are enabled, also site URL, WordPress/PHP versions, user login/roles, active plugins, and table prefix.
Data on your server
AI bot logs (bot name, user-agent, path, timestamp) stay in wp_llm_bot_visits and wp_llm_bot_page_clicks and are never sent externally. Retention is llmagnet_data_retention_days (30, 90, 180, 365, or 0 = keep; default 365). This plugin does not set visitor cookies.
Zrzuty ekranu
Instalacja
- Upload to
/wp-content/plugins/or install via Plugins Add New - Activate LLMagnet
- Go to LLMagnet in your admin menu
- Configure your content settings and click Generate Now
- Verify at
https://your-site.com/llms.txt
Najczęściej zadawane pytania
-
What is llms.txt?
-
llms.txt is an emerging standard (like robots.txt for search engines) that helps AI models understand your site structure and content.
-
Will this slow down my site?
-
No. Documents are built when requested and cached. There is no extra work on the public page for visitors.
-
Which AI bots can LLMagnet detect?
-
ChatGPT, Claude, Perplexity, Gemini, Grok, Bing AI, Mistral, DeepSeek, Llama, and more — 25 bots in total. All of them are detected, logged, and reported by name.
-
How many pages does the free version list?
-
All of them. The Pages screen lists every page that received AI bot traffic in the selected window.
-
Does LLMagnet work with the WordPress Abilities API / MCP?
-
Yes. On WordPress 6.9+ LLMagnet registers its analytics and llms.txt tools as WordPress abilities (under the
llmagnetcategory). 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. -
Do I need WooCommerce?
-
No. Core features work on any WordPress site. WooCommerce commerce analytics and UCP catalog discovery are part of the separate LLMagnet Pro add-on and also need WooCommerce to be active.
-
How is the site Visibility Score calculated?
-
It scores published content for AI crawler readiness (headings, meta description, length, image ALT coverage, and related checks). WooCommerce product visibility scores are part of the separate LLMagnet Pro add-on.
-
Which languages does the admin interface support?
-
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.moand.jsonfiles to the plugin’slanguages/folder. -
Does the plugin support WordPress multisite?
-
Yes. llms.txt, llms-full.txt, and markdown are served by WordPress for each site. The plugin does not write those files into a shared site root.
-
Why is there no physical llms.txt file in my site root?
-
LLMagnet serves
/llms.txtand/llms-full.txtthrough WordPress. Markdown is served at{permalink}.md. A physicalllms.txtalready in the site root, including one written by another plugin, is left in place and is what the web server serves. Older versions of this plugin remove files they created, once, during upgrade.
Recenzje
Kontrybutorzy i deweloperzy
„LLMagnet – AI Visibility & AI SEO for Claude, ChatGPT & More” jest oprogramowaniem open source. Poniższe osoby miały wkład w rozwój wtyczki.
Zaangażowani
Przetłumacz wtyczkę “LLMagnet – AI Visibility & AI SEO for Claude, ChatGPT & More” na swój język.
Interesuje cię rozwój wtyczki?
Przeglądaj kod, sprawdź repozytorium SVN lub czytaj dziennik rozwoju przez RSS.
Rejestr zmian
3.6.0
- llms.txt and llms-full.txt are served by WordPress at /llms.txt and /llms-full.txt. Markdown is served at each public permalink with a .md suffix. The plugin no longer writes those files into the site root.
- llms-full.txt is part of this plugin. Turn it on from LLMs.txt.
- Removed the in-admin account, pricing, and add-on screens from this build.
- Multisite can be activated. Each site is served its own documents.
- Admin bundles include a source comment. Human-readable React source remains under src/.
- Hardening: request values from the web server are sanitized before use.
- Reports: the Reports screen is not part of this plugin. Scheduled email reports are registered by LLMagnet Pro. PDF download of bot and page analytics stays on those screens.
3.5.3
- Security: lifecycle contact and event posts go to api.llmagnet.com only after telemetry opt-in; this plugin no longer fetches or stores a vendor Brevo key
- Privacy: malformed retention values can no longer become 0 (keep forever)
- Commerce: WooCommerce conversion tracking and the attribution cookie live only in the LLMagnet Pro add-on
- Agent Ready: toggle and auto fixes that this plugin owns run here; llms-full.txt and schema stay as manual guidance
- Reports: scheduled email settings live in Pro; PDF download stays in this plugin
- Admin: trial promotion is removed from the WordPress.org build; bot logos ship as plugin assets (generic agents use the bundled AI mark)
- Privacy: news and promo feeds stay off until an administrator approves loading them from the external source
- Docs: Pro extras are listed only under What’s in LLMagnet Pro; feedback goes to support@llmagnet.com
3.5.2
- Analytics: the free plugin now reports every detected AI bot by name and lists every page with AI traffic — the previous free-plan reporting limits (3 named bots, top 5 pages) are removed entirely
- Exports: any public post type can be included in llms.txt and markdown exports on the free plan
- UI: locked-looking upgrade controls replaced with clearly-labelled promotional notices for the separate Pro add-on
- Copy: trial and Pro notices mention only add-on features (llms-full.txt, schema JSON-LD, scheduled reports) — not analytics
- License: the in-plugin license screen lives in the Pro add-on; the free plugin no longer registers it
- Agent Ready: the one-click fix REST route is registered by Pro only; the get_agent_readiness MCP tool is available on every plan
- MCP: send_report_email, product AI stats, and the AI revenue funnel are registered by the Pro add-on only
- Privacy: news/promo feed requests use a generic plugin user-agent (no site URL); admin-screen feed loads are documented
- Trial: the first licensing notice uses the default 24-hour delay
- Privacy: onboarding telemetry is an explicit choice — Share usage data or Continue without sharing — and stays off unless you opt in
- Docs: added IndexNow and LLMagnet Terms of Use to External services; removed a stale repository link from the Source code section
- Source: the human-readable TypeScript/React source (
src/) and build tooling now ship inside the plugin
3.5.0
- Paid features now live in a licensed Pro runtime instead of being gated inside the free build. See What’s in LLMagnet Pro for the full split
- Free keeps: llms.txt, markdown exports, full bot analytics for all 25 crawlers, visibility score, agent-readiness audit, GA4 + Search Console, MCP read co-pilot, Elementor integration
- Pro adds: llms-full.txt, images and ALT text in exports, Schema JSON-LD scan/generate/publish, WebMCP, one-click audit fixes, scheduled reports and event alerts
- Plus adds: WooCommerce commerce analytics, UCP catalog discovery, and commerce schema
- Detection and logging remain uncapped on every plan, so your existing bot history stays complete when you upgrade — nothing is held back on the free plan
- Screens for Pro features show a promotional panel instead of blurred or placeholder data
3.4.8
- WordPress.org compliance: all local features (llms-full.txt, agent-readiness, one-click fixes, commerce analytics, UCP, email reports) are fully available without a paid license gate
- Privacy: Brevo API key provisioning no longer runs on activation or init — only after explicit telemetry opt-in
- Privacy: “Powered by LLMagnet” credit in report emails is opt-in and off by default
- Assets: Chart.js and fonts are bundled locally; removed remote CDN and Fontshare loads
- Admin: dashboard widget no longer loads the full React stylesheet on wp-admin/index.php (prevents admin layout bleed)
- Docs: added Source code and External services sections to readme.txt
- Maintenance: bundled libraries updated
3.4.7
- New: Connections — sign in with Google Analytics 4 and Search Console, pick a property, and see live traffic plus search queries
- New: Never visited filter on Pages and Products — find published content AI bots have not visited in the last 7, 30, or 90 days
- New: UCP catalog discovery (Plus/Ultra + WooCommerce) — agents can search and look up products; no cart, checkout, or payments
- Fix: noindex posts stay out of llms.txt, llms-full.txt, llms-docs, and MCP markdown (Yoast, Rank Math, All in One SEO, SEOPress, The SEO Framework)
- Fix: Connections no longer hangs after Google sign-in; pick a property from a searchable list, and disconnect anytime
- Tweak: Enterprise plan is now called Ultra
- Tweak: lifecycle emails and product analytics stay off until you opt in to sharing
3.4.6
- Fix: transction email not set
3.4.5
- New: the Overview visibility score now explains how it is calculated. Open the breakdown to see crawl frequency, bot quality, traffic volume, page health, and content quality — each with its weight and a short explanation. The score card can also switch between the circular gauge and a radar chart of the same criteria
- New: MCP connect guides for OpenClaw, NanoClaw, and Hermes, with copy-paste config and an agent prompt that can install the server for you
- Fix: recommendations in the WordPress editor sidebar and pre-publish checklist now show the real message text instead of blank or broken items
3.4.4
- Security: password-protected posts could be exposed through the generated exports. The per-page
.mdendpoint 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 - New: the markdown alternate is now advertised in structured data even when an SEO plugin owns JSON-LD. The
.mdURL is injected as anencoding/MediaObjectfield 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 - New: Agent Skills discovery now follows the published spec (draft v0.2.0). The index is served at
/.well-known/agent-skills/index.jsonwith a$schemaidentifier and a SHA-256 digest per skill, alongside a realSKILL.mdartifact 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-skillspath keeps working and returns the same index - New:
/llms.txtand/llms-full.txtare 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 precedence - Fix: the
Content-Signaldirective 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 group - Fix: the
Linkresponse headers advertise/.well-known/api-catalogand the Agent Skills index, both of which were already being served but never announced - Improvement: markdown front matter now includes the content type and a self-referencing
markdown_url
3.4.3
- Bug fix: fix the Schema JSON-LD for FAQs
- New: bundled admin translations for French (fr_FR), German (de_DE), Italian (it_IT), Japanese (ja), and Chinese (Simplified, zh_CN)
3.4.1
- Bug fix: admin pages (Pages, LLMs.txt, and other lazy-loaded screens) could fail after upgrading with a React „useState” error when the browser served stale JavaScript from cache
- Bug fix: React admin bundles now append the plugin version to lazy-loaded chunk URLs so caches invalidate on every release
- Bug fix: a dismissible admin notice prompts a hard refresh after plugin updates when stale assets may still be cached
- New: bundled admin translations for Hebrew (he_IL), Arabic (ar), and Spanish (Spain, es_ES)
3.4.0
- New: AI assistant connectivity via the WordPress Abilities API and an on-plugin MCP server (Claude, ChatGPT, Cursor). MCP and OAuth are now opt-in and disabled by default for security
- New: guided onboarding wizard and in-dashboard feedback/bug reporting (attaching the debug log is opt-in, and obvious secrets are masked)
- New: internationalization (i18n) infrastructure for the admin experience
- Security: rate limiting on dynamic OAuth client registration; safer analytics error states instead of silent placeholder data
- Maintenance: raised the minimum required PHP version to 7.4 to match the codebase, plus build/packaging and CI improvements
3.3.9
- Security hardening: removed leftover development/debug artifacts from the alt-text manager (hardcoded attachment ID fallback, local test URL map, verbose request logging)
- Removed diagnostic test.php file from the distributed plugin
- Multisite: activation is now blocked on multisite networks with a clear
explanation (the plugin is single-site only; root-level llms.txt files would
conflict between subsites).
3.3.8
- Schema.org JSON-LD now apply automaticly when publish the schema
- Bug fixes and stability improvements for AI tracking visits from llms
3.3.7
- Schema.org JSON-LD – scan, recommendations, guided generation, and publish structured data from the dashboard
- Improved experience across the admin UI and workflows
- Bug fixes and stability improvements
3.3.0
- Pages & Posts Content Analysis – AI-readiness scores and content quality analysis for all pages and blog posts, just like WooCommerce products
- PDF Report Downloads – Export your AI visibility reports as PDF files
- Notification Center – In-dashboard alerts and updates to keep you informed
- Improved Onboarding – Revamped onboarding flow with better guidance for new users
- Bug fixes and performance improvements
3.2.0
- Added full llms-full.txt support with extended metadata
- Enhanced llms.txt format with improved structure
- Automatic robots.txt integration for AI crawler guidance
- Full compatibility with RankMath and Yoast SEO
- New recommendations system with actionable visibility improvements
- Enhanced onboarding wizard with better user guidance
- Smart suggestions for meeting AI crawler standards
3.1.4
- WooCommerce Commerce Analytics (Plus & Ultra)
- Product Visibility Score with optimization recommendations
- AI Revenue Funnel tracking
- Product Optimization Drawer with tag autocomplete
- Google Lighthouse-style score display
3.0.3
- Fix count visit in table and cards
3.0.2
- Change owner to company profile
3.0.0
- Add clicks analytics from LLM bots via UTM tracking
- Add table view with impressions, clicks, CTR, and trends
- Toggle between card and table views
- Improved analytics dashboard
2.0.8
- Add ALT text management for images
- Improved plugin activation
2.0.0
- Analytics per LLM bot agent
- Improved bot detection
- Email reports
1.0.0
- Initial release