AEOTrack

How can AEOTrack help you?

November 6, 2026

The WordPress plugin

What it does

The AEOTrack WordPress plugin (version 2.0) does two things:

  1. Reports AI-crawler visits. Every request to your site is checked on the server against the known AI crawler signatures — GPTBot, OAI-SearchBot and ChatGPT-User (OpenAI), ClaudeBot, anthropic-ai and Claude-Web (Anthropic), PerplexityBot and Perplexity-User, Google-Extended and GoogleOther, cohere-ai, CCBot and others — and a match is sent to AEOTrack with the path that was fetched. Ordinary visitors are never reported. The visits appear under Your site → AI crawler setup.
  2. Adds the [aeotrack_faq] shortcode, which shows the FAQs you approved, with matching FAQ schema, on the page where you place it. Visitors see the questions and answers; the FAQPage markup underneath is built from the same list, so the two always agree.

The detection has to run on the server because AI crawlers do not run JavaScript: a script tag in the page would never see them. That is why there is no snippet to paste — the plugin is the integration.

The plugin is included on every paid plan and the trial (it belongs to AI bot detection).

Install

  1. Open Integrations in AEOTrack, pick the website in the header, and scroll to WordPress.
  2. Click Download plugin (ZIP). The ZIP is built for this website — its tracked-website id is inside — so download it again for each WordPress site you track. Raw PHP file gives the same plugin as a single file for developers who deploy plugins themselves.
  3. In WordPress, go to Plugins → Add New → Upload Plugin, choose the ZIP, click Install Now, then Activate.
  4. There is nothing to configure in WordPress. Within a day or two of a real AI crawler visiting, it shows under Your site → AI crawler setup.

The plugin requires WordPress 5.0 or later and works with any theme. It hooks init for detection and adds nothing to page weight for visitors.

Show your FAQs

  1. In AEOTrack, generate FAQs in Improve → FAQ schema and approve the ones you want published (see the FAQ Schema Generator Guide). Draft FAQs are never shown.
  2. In WordPress, edit the page that should show them (usually your FAQ page), add a Shortcode block and type [aeotrack_faq]. To show one particular FAQ set, use [aeotrack_faq id="faq_…"] with that set's id from AEOTrack.
  3. Update the page. It now shows the questions and answers, with their FAQPage markup, in that spot. The plugin caches the FAQs for 12 hours, so approving new ones updates the page on the next refresh with no redeploy.

The plugin no longer uses wp_head and no longer adds FAQ schema to your homepage. Structured data should describe content visitors can see, so the FAQs now appear, visibly, on the page you choose.

Upgrading from version 1

Version 1 plugins stop adding homepage schema on their own within 12 hours, with nothing for you to do; crawler detection keeps working. To get the shortcode, download the ZIP again from the WordPress card and upload it over the old plugin (WordPress offers Replace current with uploaded).

Checking it works

  • Crawler visits: you cannot force an AI crawler to visit, but the first real visit appears under AI crawler setup with the bot's name, the page and the time. Sites that block AI crawlers in robots.txt (see Your site → Crawlability) will, correctly, see none from the bots they block.
  • FAQs: open the page with the shortcode; the questions should show. In the page source, look for <script type="application/ld+json"> containing "@type": "FAQPage", or paste the URL into Google's Rich Results Test. If nothing shows, check that at least one FAQ is approved. If you approved new FAQs and the page still shows the old ones, the 12-hour cache has not refreshed yet; clearing your site's transients (or any caching plugin's cache) forces it.

Not on WordPress?

AI-crawler visits can be read from your web server's logs instead: Your site → AI crawler setup → Server log ingestion explains the upload. For FAQs, a GitHub repository can receive them as aeotrack/faq-section.html (the visible section plus markup) in a pull request. On any other platform, copy the approved questions and answers onto the page by hand, with the JSON-LD from </> View schema; see the FAQ Schema Generator Guide.

Removing it

Deactivate and delete the plugin in WordPress as usual. Visit history already recorded in AEOTrack is kept. A page that still contains the [aeotrack_faq] shortcode will show the shortcode text once the plugin is gone, so remove the block too.