Frontierline AIO Toolkit

By frontierline2015

0+ active installationsVersion 0.2.0

Make your site AI-ready and see the result: llms.txt, AI crawler rules, JSON-LD, plus a log of which AI crawlers and assistants visit.

Description

Frontierline AIO Toolkit prepares your WordPress site for LLMs and AI-powered search. It focuses on the few things that actually decide whether an AI assistant can read, understand and cite your site — and does them automatically, from one simple settings screen.

How this differs from other llms.txt plugins

An llms.txt file on its own is only part of the picture. Being readable by an AI assistant takes three things working together, and this plugin is built to cover all three from a single screen:

  1. Content the model can read — llms.txt, plus a full-text llms-full.txt that is cached and size-capped.
  2. Permission to fetch it — rules for 23 named AI crawlers appended to your virtual robots.txt, after other SEO plugins have written theirs, so nothing is overwritten.
  3. Context the model can parse — schema.org JSON-LD for posts, pages, the front page and authors.

And then it shows you whether it worked: an AI activity report logs which AI crawlers fetch your pages and your llms.txt, and counts the visitors that AI assistants such as ChatGPT, Perplexity, Gemini, Claude and Copilot send to you.

It is also built to sit next to an existing SEO plugin rather than fight it. The robots.txt rules are appended at filter priority 100000, after plugins such as Yoast SEO that rebuild the whole file late, so neither output is lost; and when Yoast SEO, Rank Math, All in One SEO or SEOPress is detected the settings screen says so, next to the checkbox that turns this plugin’s JSON-LD off, so you can avoid duplicate structured data.

Features

  • llms.txt (auto-generated) – A concise, machine-friendly overview of your site: summary, company info and key pages, served dynamically at /llms.txt.
  • llms-full.txt (auto-generated) – A full-text aggregation of your published posts and pages for LLM ingestion, with caching and a configurable size cap, served at /llms-full.txt.
  • AI crawler rules – Adds rules for 23 major AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot and more) to your virtual robots.txt. Choose “allow all” or “allow AI search and assistants, block model-training crawlers”. Your site-wide Disallow rules are repeated for each AI crawler (a named group does not inherit User-agent: *), and crawlers that already have their own rules are left untouched.
  • AI crawler log – See which AI crawlers visited in the last 7 days, how often they read llms.txt, when they were last seen and the trend against the previous week. Crawlers never show up in Google Analytics; this log fills that gap.
  • Visits from AI assistants – Counts visitors arriving from ChatGPT, Perplexity, Gemini, Claude, Copilot, DeepSeek, Grok and others, with their landing pages. Works with page caching.
  • Google Analytics 4 integration – Optionally sends an ai_referral event (parameter ai_source) through the GA4 or Google Tag Manager tag already on your site, and gives you a ready-made regex for a GA4 custom channel group that covers assistants Google’s built-in “AI Assistant” channel misses.
  • AI readiness checks and dashboard widget – Flags common blockers (a physical robots.txt or llms.txt file, “Plain” permalinks, “Discourage search engines”, a missing site summary) and shows a 7-day summary on the dashboard.
  • JSON-LD structured data – Injects schema.org markup automatically: Article for posts, WebPage for pages, Organization + WebSite for the front page, Person for authors and ImageObject for featured images.
  • Simple settings – One tabbed screen under Settings → AIO Toolkit. Nothing to configure to get started; sensible defaults are on out of the box.

Privacy first

Password-protected, private and draft content is never included in the generated feeds. Activity is stored on your own server as daily totals only — no IP addresses, cookies or personal data. (The visitor counter sets a session-only browser storage flag so a reload is not counted twice, and keeps a salted hash of the IP for up to 10 minutes to limit repeated counting.) The plugin sends nothing to Frontier Line or any other third party; the optional Google Analytics event only goes through the GA tag you already use, and is off by default.

Built for developers

Lightweight, dependency-free, multisite-aware and translation-ready. Filters: flaio_ai_crawlers, flaio_llms_txt, flaio_llms_full_txt, flaio_llms_full_post_types, flaio_llms_full_max_posts, flaio_schema_graph.

The feed queries do not suppress query filters, so membership and access-control plugins can exclude their restricted content from llms-full.txt as they do elsewhere on the site.

Installation

  1. Upload the plugin files to /wp-content/plugins/frontierline-aio-toolkit, or install it through the WordPress Plugins screen.
  2. Activate the plugin through the “Plugins” screen in WordPress.
  3. Visit Settings → AIO Toolkit to see the AI activity report and review the options (all core features are enabled by default).
  4. Confirm your feeds at /llms.txt and /llms-full.txt.

FAQ

Do I need to configure anything?

No. After activation, llms.txt, llms-full.txt, the AI crawler allow-list and JSON-LD are all enabled with sensible defaults. You can refine the site summary, company info and toggles under Settings → AIO Toolkit.

Where are llms.txt and llms-full.txt served?

They are generated dynamically at https://your-site/llms.txt and https://your-site/llms-full.txt. Pretty permalinks are required (any structure other than “Plain” under Settings → Permalinks). If the feeds return 404 right after activation, visit Settings → Permalinks once to flush the rewrite rules.

Is my private content exposed?

No. Only published posts and pages are included. Drafts, private posts and password-protected posts are excluded from both feeds, and no JSON-LD is emitted for them either.

Does it conflict with my SEO plugin?

No. AIO Toolkit appends to the virtual robots.txt rather than replacing it, and it adds its own JSON-LD block. If your SEO plugin already outputs schema.org markup you can turn the JSON-LD tab off and keep only the llms.txt features.

Does llms-full.txt affect performance?

The output is cached in a transient, regenerated when your content changes and refreshed at most once a day. A configurable size cap (default 500 KB, maximum 10 MB) keeps the response small.

How do I change the list of AI crawlers?

Use the flaio_ai_crawlers filter to add or remove user agents:

add_filter( 'flaio_ai_crawlers', function ( $agents ) { $agents[] = 'MyBot'; return $agents; } );

Does the plugin call any external service?

No. The server never contacts a third-party API. If you turn on “Send an event to Google Analytics”, the visitor’s browser passes an ai_referral event to the Google Analytics / Google Tag Manager tag that is already installed on your site; nothing is sent if no tag is present.

How is this different from the “AI Assistant” channel in Google Analytics 4?

GA4 (since May 2026) groups visits from AI assistants it recognizes into an “AI Assistant” channel. It cannot see AI crawlers at all, counts Google AI Overviews and AI Mode as Organic Search, and does not publish which assistants it recognizes. This plugin logs the crawlers on your server, counts assistant visits independently, and can send its own event to GA4 so you can analyse them there.

Why are the crawler numbers lower than in my server logs?

Requests served by a page cache or CDN never reach WordPress, so they are not counted, and on very busy sites simultaneous requests can occasionally overwrite each other’s count. Treat the numbers as a minimum. User agents can also be faked.

Does the plugin advertise anything?

The AI activity screen ends with a link to a free AI visibility check offered by the plugin’s developer, Frontier Line. It is a plain link on the plugin’s own settings screen; there are no dashboard notices or pop-ups.

Can I block AI training but stay visible in AI search?

Yes. Under the robots.txt tab choose “Allow AI search and assistants, block model-training crawlers”. GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot and other training crawlers get Disallow: /, while OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot and similar stay allowed.

Is multisite supported?

Yes. Rewrite rules are registered per site on activation, and uninstalling cleans up every site in the network (on very large networks, the site it is run from).

Screenshots

Changelog

0.2.0

  • New: AI activity report – AI crawler log (7 days, trend, llms.txt reads, last seen) and visits from AI assistants with landing pages.
  • New: Google Analytics 4 integration – optional ai_referral event and a custom channel group regex.
  • New: robots.txt policy “allow AI search and assistants, block model-training crawlers”.
  • New: AI readiness checks and a dashboard widget.
  • Improved: site-wide robots.txt Disallow rules are repeated for each AI crawler group; crawlers that already have their own group are no longer touched.
  • Improved: crawler list updated (Claude-SearchBot, Google-CloudVertexBot, Meta-ExternalFetcher added; retired Anthropic tokens removed).
  • Improved: settings labels are linked to their fields for screen readers.

0.1.0

  • Initial release: llms.txt, llms-full.txt, AI crawler allow-list, JSON-LD injection, tabbed settings screen.