Follow Recommendations<\/strong> \u2013 Get actionable suggestions to improve AI visibility<\/li>\n<\/ol>\n\nSEO Plugin Compatibility<\/h3>\n\n
LLMagnet works seamlessly alongside your existing SEO setup:\n* Rank Math & Yoast SEO<\/strong> \u2013 Excludes noindex posts from llms.txt, llms-full.txt, and markdown exports when those plugins mark content noindex\n* Smart robots.txt Management<\/strong> \u2013 Registers llms.txt (and llms-full.txt when generation is enabled)\n* Elementor Editor Integration<\/strong> \u2013 AI visibility scores in the Elementor editor. Per-page JSON-LD schema fields ship with LLMagnet Pro\n* No conflicts with your current SEO workflow<\/p>\n\nAIO \/ GEO \/ AEO Benefits<\/h3>\n\n\n- AIO (AI Optimization)<\/strong> \u2013 Structured content that AI models can parse accurately<\/li>\n
- GEO (Generative Engine Optimization)<\/strong> \u2013 Better representation in AI-generated answers<\/li>\n
- AEO (Answer Engine Optimization)<\/strong> \u2013 Increased chances of being cited as a source<\/li>\n<\/ul>\n\n
Source code<\/h3>\n\n
The plugin's admin interface ships as compiled React bundles (assets\/react-build\/js\/*<\/code> and assets\/react-build\/css\/*<\/code>). The complete, human-readable TypeScript\/React source is included in this plugin under src\/<\/code>, together with the build tooling (package.json<\/code>, package-lock.json<\/code>, and the Vite\/TypeScript\/PostCSS\/Tailwind configuration files).<\/p>\n\nTo rebuild the admin assets from source:<\/p>\n\n
\n- Install Node.js 18+ and npm.<\/li>\n
- Run
npm ci<\/code> in the plugin root.<\/li>\n- Run
npm run build<\/code> to regenerate assets\/react-build\/<\/code>.<\/li>\n- The TypeScript\/React source lives under
src\/<\/code>; PHP lives under includes\/<\/code> and the main plugin file.<\/li>\n<\/ol>\n\nExternal services<\/h3>\n\n
This plugin contacts some external services whenever an administrator opens an LLMagnet admin screen (bot logos and the in-plugin news\/promo feeds). Other services run only after you enable the related feature or opt in (Freemius, Google, IndexNow, Brevo, Mixpanel). Nothing below runs for anonymous site visitors unless noted.<\/p>\n\n
Freemius (account, licensing & updates)<\/h4>\n\n
When:<\/strong> The plugin uses the Freemius SDK for its account screen and for checkout of the separate LLMagnet Pro add-on. On activation you are shown an opt-in screen with a Skip<\/strong> option; no profile data is sent unless you opt in. Independently of that choice, Freemius is contacted when you activate or validate a license for that add-on. Endpoints: api.freemius.com<\/code>, wp.freemius.com<\/code>.<\/p>\n\nWhat is sent:<\/strong> On opt-in \u2014 site URL, administrator email and name, site language, WordPress version, PHP version and plugin version; the list of active plugins and themes is sent only if you grant that permission separately. On license\/update checks \u2014 site URL, plugin version and license key. Skipping the opt-in keeps profile data local.<\/p>\n\nTerms & privacy:<\/strong> Freemius Terms of Service \u2014 https:\/\/freemius.com\/terms\/ \u00b7 Freemius Privacy Policy \u2014 https:\/\/freemius.com\/privacy\/<\/p>\n\nGoogle (Analytics 4 & Search Console)<\/h4>\n\n
When:<\/strong> Only after an administrator connects Google from Connections<\/strong> and completes OAuth.<\/p>\n\nWhat is sent:<\/strong> OAuth authorization requests to Google (accounts.google.com<\/code>); after connect, read-only API calls to googleapis.com<\/code> \/ analyticsdata.googleapis.com<\/code> \/ searchconsole.googleapis.com<\/code> for GA4 and Search Console metrics you already have (sessions, landing pages, clicks, queries). Tokens are stored encrypted on your site.<\/p>\n\nTerms & privacy:<\/strong> Google Terms of Service \u2014 https:\/\/policies.google.com\/terms \u00b7 Google Privacy Policy \u2014 https:\/\/policies.google.com\/privacy<\/p>\n\nIndexNow (api.indexnow.org)<\/h4>\n\n
When:<\/strong> Only if you enable the IndexNow<\/strong> feature toggle on the Agent Ready screen (off by default), and only if no other SEO plugin (Rank Math Instant Indexing, AIOSEO IndexNow, Yoast Premium) is already handling IndexNow pings. When you publish, update, or unpublish content of an included post type, the affected URLs are queued and sent about five minutes later as one batched request to https:\/\/api.indexnow.org\/indexnow<\/code>, so participating search engines (such as Microsoft Bing and others in the IndexNow network) can re-crawl your content quickly.<\/p>\n\nWhat is sent:<\/strong> Your site host name, the plugin-generated IndexNow verification key (also served publicly at https:\/\/your-site.com\/{key}.txt<\/code>), and the list of public URLs that changed (up to 500 per batch). No visitor data, no post content, and no personal data are included.<\/p>\n\nTerms & privacy:<\/strong> IndexNow Terms of Use \u2014 https:\/\/www.indexnow.org\/terms \u00b7 The service is operated with participating search engines; see Microsoft's Privacy Statement \u2014 https:\/\/privacy.microsoft.com\/en-us\/privacystatement and https:\/\/www.indexnow.org\/ for the participating engines.<\/p>\n\nAgent Skills schema identifier (schemas.agentskills.io)<\/h4>\n\n
When:<\/strong> Only if you enable Agent Skills discovery on the Agent Ready screen (off by default). The plugin then serves \/.well-known\/agent-skills\/index.json<\/code> (and the related SKILL.md<\/code>) from your own site.<\/p>\n\nWhat is used:<\/strong> The published schema identifier schemas.agentskills.io\/discovery\/0.2.0\/schema.json is written into that JSON as a $schema<\/code> string so agents can recognize the document. The plugin never fetches schemas.agentskills.io and never sends data there.<\/p>\n\nTerms & privacy:<\/strong> The identifier is a public schema URL. No site data leaves your WordPress install for this purpose.<\/p>\n\nLLMagnet API broker (api.llmagnet.com, fallback llmagnet-api-server.vercel.app)<\/h4>\n\n
When:<\/strong>\n* Google Connections \u2014 only after an administrator starts a connection from Connections<\/strong> and uses the hosted OAuth broker (not your own Google credentials). The broker builds the authorization start URL, exchanges the returned one-time ticket for tokens, and refreshes tokens when they expire.\n* Lifecycle contact and event posts \u2014 only after<\/strong> you opt in to product emails (llmagnet_email_consent<\/code>). See Brevo below.<\/p>\n\nThe production host is api.llmagnet.com. If that host is unreachable the plugin may fall back to llmagnet-api-server.vercel.app for Google broker routes only. Both hosts are operated by LLMagnet.<\/p>\n\n
What is sent:<\/strong> For Google \u2014 site URL\/domain, the return URL for the OAuth redirect, and broker-specific one-time tickets. When a Google connection is refreshed in the background, the Google refresh token is sent through api.llmagnet.com (or llmagnet-api-server.vercel.app) to obtain a new access token. For lifecycle \u2014 the fields listed under Brevo below. No visitor analytics and no site content.<\/p>\n\nTerms & privacy:<\/strong> Terms of Use \u2014 https:\/\/llmagnet.com\/terms\/ \u00b7 Privacy Policy \u2014 https:\/\/llmagnet.com\/privacy-policy\/ \u00b7 Cookie Policy \u2014 https:\/\/llmagnet.com\/cookie-policy\/<\/p>\n\nBrevo (email \/ CRM, via api.llmagnet.com)<\/h4>\n\n
When:<\/strong> Only after explicit email<\/strong> opt-in (llmagnet_email_consent<\/code>), which is separate from Mixpanel usage analytics. This plugin never talks to api.brevo.com and never ships a Brevo API key. Requests go to api.llmagnet.com\/lifecycle\/contact and api.llmagnet.com\/lifecycle\/event; the vendor key stays on that first-party server. Turning email consent off sends an unsubscribe event for the admin address.<\/p>\n\nWhat is sent:<\/strong> Admin email, site name, site URL, plugin version, onboarding status, visibility score, and plan name \u2014 for lifecycle emails and contact sync.<\/p>\n\nTerms & privacy:<\/strong> Brevo Terms of Use \u2014 https:\/\/www.brevo.com\/legal\/termsofuse\/ \u00b7 Brevo Privacy Policy \u2014 https:\/\/www.brevo.com\/legal\/privacypolicy\/<\/p>\n\nMixpanel (product analytics)<\/h4>\n\n
When:<\/strong> Only after explicit telemetry opt-in on LLMagnet admin screens.<\/p>\n\nWhat is sent:<\/strong> In-plugin admin usage events (page views, button clicks, onboarding progress) plus plan name, plugin\/WordPress versions, site language, and WooCommerce active yes\/no. Identified by site domain. Admin email and site URL are not sent to Mixpanel.<\/strong> EU endpoint: api-eu.mixpanel.com<\/code>. The bundled Mixpanel library includes session-replay (rrweb) code that LLMagnet does not enable.<\/p>\n\nTerms & privacy:<\/strong> Mixpanel Terms of Use \u2014 https:\/\/mixpanel.com\/legal\/terms-of-use\/ \u00b7 Mixpanel Privacy Policy \u2014 https:\/\/mixpanel.com\/legal\/privacy-policy\/<\/p>\n\nLLMagnet news feed (llmagnet-wp-news)<\/h4>\n\n
This is in-plugin product news and occasional upgrade notices for administrators \u2014 not visitor tracking and not Mixpanel\/Brevo telemetry. It never runs on the front end, never runs on other wp-admin screens, and does not send your site URL, admin email, or any other identifier.<\/p>\n\n
When:<\/strong> Only after an administrator opts in (llmagnet_news_feed_consent<\/code>). The first click on the notification bell asks for approval; that choice is stored so the prompt is not shown again. Until then, LLMagnet does not request the remote news or promo JSON. After opt-in, the notification center and promo modal request the feed through a manage_options<\/code> REST route. The result is cached for 30 minutes. Default endpoints: llmagnet-wp-news.vercel.app\/data\/notifications.full-sample.json and llmagnet-wp-news.vercel.app\/data\/promo-modals.json. Override with the LLMAGNET_NEWS_JSON_URL<\/code> \/ LLMAGNET_PROMO_MODAL_JSON_URL<\/code> constants in wp-config.php<\/code>, or with the llmagnet_news_json_url<\/code> \/ llmagnet_promo_modal_json_url<\/code> filters; returning an empty string from the promo-modal filter uses the bundled sample file instead of any remote request. You can turn the feed off again under System Information \u2192 Privacy & Data.<\/p>\n\nWhat is sent:<\/strong> A server-side, unauthenticated HTTP GET. The plugin sets a generic User-Agent: LLMagnet\/{version}<\/code> so WordPress does not send your site URL. No site data and no identifiers are included. This feed is operated by LLMagnet.<\/p>\n\nImages:<\/strong> Some feed items display images hosted on *.public.blob.vercel-storage.com<\/code> (Vercel Blob, operated with the news feed). Those images load in the administrator\u2019s browser on LLMagnet admin screens only.<\/p>\n\nTerms & privacy:<\/strong> Terms of Use \u2014 https:\/\/llmagnet.com\/terms\/ \u00b7 Privacy Policy \u2014 https:\/\/llmagnet.com\/privacy-policy\/ \u00b7 Cookie Policy \u2014 https:\/\/llmagnet.com\/cookie-policy\/<\/p>\n\nFeedback form<\/h4>\n\n
When:<\/strong> Only when an administrator submits the in-plugin feedback form (onboarding \/ support). The message is sent with wp_mail<\/code> to support@llmagnet.com.<\/p>\n\nWhat is sent:<\/strong> The message and subject you typed. If you enable diagnostics, the email also includes site URL, WordPress\/PHP versions, the submitting user\u2019s login and roles, the active plugin list, and the database table prefix. Nothing is sent until you submit the form.<\/p>\n\nData & Privacy<\/h4>\n\n
LLMagnet is designed to be privacy-first. Usage analytics, product emails, and the remote news\/promo feed are separate opt-ins, all off by default.<\/strong> Bot vendor logos on admin screens are bundled with the plugin. The news\/promo feeds do not run for site visitors.<\/p>\n\nUsage data (llmagnet_telemetry_consent<\/code>).<\/strong> Mixpanel dashboard events only. No admin email and no site URL are sent.<\/p>\n\nProduct emails (llmagnet_email_consent<\/code>).<\/strong> Lifecycle emails to the WordPress admin address via api.llmagnet.com (Brevo on the server). Turning this off sends an unsubscribe event. Change either choice under System Information or POST to llm-analytics\/v1\/privacy\/settings<\/code>.<\/p>\n\nGoogle Analytics 4 & Search Console (optional).<\/strong> Only if you click Connect<\/strong> on the Connections screen. Sign-in uses Google OAuth. LLMagnet stores encrypted tokens on your site and reads GA4 \/ Search Console metrics (AI referrals, landing pages, clicks, queries) for the dashboard. Disconnect removes that link. This is separate from the telemetry opt-in above.<\/p>\n\nVisitor analytics stay on your server.<\/strong> AI bot visit logs (bot name, user-agent string, page path, timestamp) are stored locally in the wp_llm_bot_visits<\/code> and wp_llm_bot_page_clicks<\/code> database tables and are never sent to any external service<\/strong>. These tables log AI crawlers - not human visitors. Logs older than the configured retention window are pruned automatically by a daily background task; the window is controlled by the llmagnet_data_retention_days<\/code> option (allowed values: 30, 90, 180, 365, or 0 to keep forever; default 365).<\/p>\n\nThis plugin does not set visitor cookies.<\/p>\n\n\n
\n- Upload to
\/wp-content\/plugins\/<\/code> or install via Plugins \u2192 Add New<\/li>\n- Activate LLMagnet<\/strong><\/li>\n
- Go to LLMagnet<\/strong> in your admin menu<\/li>\n
- Configure your content settings and click Generate Now<\/strong><\/li>\n
- Verify at
https:\/\/your-site.com\/llms.txt<\/code><\/li>\n<\/ol>\n\n\n\nWhat is llms.txt?<\/h3><\/dt>\nllms.txt is an emerging standard (like robots.txt for search engines) that helps AI models understand your site structure and content.<\/p><\/dd>\n
Will this slow down my site?<\/h3><\/dt>\nNo. All file generation happens in the background with zero front-end impact.<\/p><\/dd>\n
Which AI bots can LLMagnet detect?<\/h3><\/dt>\nChatGPT, Claude, Perplexity, Gemini, Grok, Bing AI, Mistral, DeepSeek, Llama, and more \u2014 25 bots in total. All of them are detected, logged, and reported by name.<\/p><\/dd>\n
How many pages does the free version list?<\/h3><\/dt>\nAll of them. The Pages screen lists every page that received AI bot traffic in the selected window.<\/p><\/dd>\n
Does LLMagnet work with the WordPress Abilities API \/ MCP?<\/h3><\/dt>\nYes. On WordPress 6.9+ LLMagnet registers its analytics and llms.txt tools as WordPress abilities (under the llmagnet<\/code> 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.<\/p><\/dd>\nDo I need WooCommerce?<\/h3><\/dt>\nNo. 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.<\/p><\/dd>\n
How is the site Visibility Score calculated?<\/h3><\/dt>\nIt 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.<\/p><\/dd>\n
Which languages does the admin interface support?<\/h3><\/dt>\nLLMagnet ships bundled translations for the plugin admin dashboard (menus, settings screens, React admin UI, and related notices). Supported locales: Hebrew<\/strong> (he_IL<\/code>), Arabic<\/strong> (ar<\/code>), and Spanish (Spain)<\/strong> (es_ES<\/code>). Set your site language under Settings \u2192 General \u2192 Site Language<\/strong>; 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<\/code> and .json<\/code> files to the plugin's languages\/<\/code> folder.<\/p><\/dd>\nDoes the plugin support WordPress multisite?<\/h3><\/dt>\nNo. LLMagnet AI SEO Optimizer is a single-site plugin. It writes llms.txt,\nllms-full.txt, and the llms-docs\/ Markdown files to the site root directory,\nwhich on a multisite network would be shared by every subsite - each subsite\nwould overwrite the others' files. To prevent this, the plugin refuses to\nactivate on multisite installations and shows an explanatory message instead.\nPlease use it on a standalone (single-site) WordPress installation.<\/p><\/dd>\n\n<\/dl>\n\n\n
3.5.3<\/h4>\n\n\n- 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<\/li>\n
- Privacy: malformed retention values can no longer become 0 (keep forever)<\/li>\n
- Commerce: WooCommerce conversion tracking and the attribution cookie live only in the LLMagnet Pro add-on<\/li>\n
- Agent Ready: toggle and auto fixes that this plugin owns run here; llms-full.txt and schema stay as manual guidance<\/li>\n
- Reports: scheduled email settings live in Pro; PDF download stays in this plugin<\/li>\n
- Admin: Freemius trial promotion is removed from the WordPress.org build; bot logos ship as plugin assets (generic agents use the bundled AI mark)<\/li>\n
- Privacy: news and promo feeds stay off until an administrator approves loading them from the external source<\/li>\n
- Docs: Pro extras are listed only under What's in LLMagnet Pro; feedback goes to support@llmagnet.com<\/li>\n<\/ul>\n\n
3.5.2<\/h4>\n\n\n- Analytics: the free plugin now reports every detected AI bot by name and lists every page with AI traffic \u2014 the previous free-plan reporting limits (3 named bots, top 5 pages) are removed entirely<\/li>\n
- Exports: any public post type can be included in llms.txt and markdown exports on the free plan<\/li>\n
- UI: locked-looking upgrade controls replaced with clearly-labelled promotional notices for the separate Pro add-on<\/li>\n
- Copy: trial and Pro notices mention only add-on features (llms-full.txt, schema JSON-LD, scheduled reports) \u2014 not analytics<\/li>\n
- License: the in-plugin license screen lives in the Pro add-on; the free plugin no longer registers it<\/li>\n
- Agent Ready: the one-click fix REST route is registered by Pro only; the get_agent_readiness MCP tool is available on every plan<\/li>\n
- MCP: send_report_email, product AI stats, and the AI revenue funnel are registered by the Pro add-on only<\/li>\n
- Privacy: news\/promo feed requests use a generic plugin user-agent (no site URL); admin-screen feed loads are documented<\/li>\n
- Trial: the first Freemius trial notice uses the default 24-hour delay<\/li>\n
- Privacy: onboarding telemetry is an explicit choice \u2014 Share usage data or Continue without sharing \u2014 and stays off unless you opt in<\/li>\n
- Docs: added IndexNow and LLMagnet Terms of Use to External services; removed a stale repository link from the Source code section<\/li>\n
- Source: the human-readable TypeScript\/React source (
src\/<\/code>) and build tooling now ship inside the plugin<\/li>\n<\/ul>\n\n3.5.0<\/h4>\n\n\n- Paid features now live in a licensed Pro runtime instead of being gated inside the free build. See What's in LLMagnet Pro<\/strong> for the full split<\/li>\n
- 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<\/li>\n
- 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<\/li>\n
- Plus adds: WooCommerce commerce analytics, UCP catalog discovery, and commerce schema<\/li>\n
- Detection and logging remain uncapped on every plan, so your existing bot history stays complete when you upgrade \u2014 nothing is held back on the free plan<\/li>\n
- Screens for Pro features show a promotional panel instead of blurred or placeholder data<\/li>\n<\/ul>\n\n
3.4.8<\/h4>\n\n\n- 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<\/li>\n
- Privacy: Brevo API key provisioning no longer runs on activation or init \u2014 only after explicit telemetry opt-in<\/li>\n
- Privacy: \u201cPowered by LLMagnet\u201d credit in report emails is opt-in and off by default<\/li>\n
- Assets: Chart.js and fonts are bundled locally; removed remote CDN and Fontshare loads<\/li>\n
- Admin: dashboard widget no longer loads the full React stylesheet on wp-admin\/index.php (prevents admin layout bleed)<\/li>\n
- Docs: added Source code and External services sections to readme.txt<\/li>\n
- Maintenance: Freemius SDK updated to 2.13.4<\/li>\n<\/ul>\n\n
3.4.7<\/h4>\n\n\n- New: Connections \u2014 sign in with Google Analytics 4 and Search Console, pick a property, and see live traffic plus search queries<\/li>\n
- New: Never visited filter on Pages and Products \u2014 find published content AI bots have not visited in the last 7, 30, or 90 days<\/li>\n
- New: UCP catalog discovery (Plus\/Ultra + WooCommerce) \u2014 agents can search and look up products; no cart, checkout, or payments<\/li>\n
- 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)<\/li>\n
- Fix: Connections no longer hangs after Google sign-in; pick a property from a searchable list, and disconnect anytime<\/li>\n
- Tweak: Enterprise plan is now called Ultra<\/li>\n
- Tweak: lifecycle emails and product analytics stay off until you opt in to sharing<\/li>\n<\/ul>\n\n
3.4.6<\/h4>\n\n\n- Fix: transction email not set<\/li>\n<\/ul>\n\n
3.4.5<\/h4>\n\n\n- 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 \u2014 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<\/li>\n
- New: MCP connect guides for OpenClaw, NanoClaw, and Hermes, with copy-paste config and an agent prompt that can install the server for you<\/li>\n
- Fix: recommendations in the WordPress editor sidebar and pre-publish checklist now show the real message text instead of blank or broken items<\/li>\n<\/ul>\n\n
3.4.4<\/h4>\n\n\n- Security: password-protected posts could be exposed through the generated exports. The per-page
.md<\/code> endpoint and the MCP content tools already refused protected content, but llms.txt, llms-full.txt and the \/llms-docs\/<\/code> markdown files did not \u2014 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<\/li>\n- New: the markdown alternate is now advertised in structured data even when an SEO plugin owns JSON-LD. The
.md<\/code> URL is injected as an encoding<\/code> \/ MediaObject<\/code> 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<\/li>\n- New: Agent Skills discovery now follows the published spec (draft v0.2.0). The index is served at
\/.well-known\/agent-skills\/index.json<\/code> with a $schema<\/code> identifier and a SHA-256 digest per skill, alongside a real SKILL.md<\/code> 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<\/code> path keeps working and returns the same index<\/li>\n- New:
\/llms.txt<\/code> and \/llms-full.txt<\/code> 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 precedence<\/li>\n