Citrail – AI SEO for GEO and AEO

Citrail audits your site for the signals AI (ChatGPT, Claude, Perplexity, Google) need to read and cite it: robots.txt, sitemap, llms.txt, JSON-LD schema, canonical meta tags, and whether your content is readable without relying on JavaScript. The result is a Health Score from 0 to 100 and a clear checklist grouped by category, with status indicators and a one-sentence explanation for each check.

When something can be improved, Citrail explains it and offers to apply it with one click: it explicitly allows access for known AI bots in your robots.txt, publishes a basic llms.txt file, and adds JSON-LD schema (Organization and Article) if no other SEO plugin is already generating it. A setup wizard guides you step by step through these improvements, and every change is reversible: you can undo it at any time from the checklist or from the wizard itself.

Citrail works exclusively with open, public standards — schema.org, the robots.txt protocol, and the llms.txt convention — exposed through WordPress’s native APIs. It does not manipulate search rankings, does not promise guaranteed results, and does not run any third-party code or external scripts on your site. It also automatically detects whether Yoast SEO, Rank Math, or All in One SEO are active so it doesn’t duplicate their work.

Build / compiling the JavaScript

The admin interface is a React application. Its uncompiled source lives in the
src/ directory and is bundled into build/ (the files WordPress actually
loads) with @wordpress/scripts,
the official WordPress build tooling, which wraps webpack and Babel with no
custom configuration.

Requirements: Node.js 20+ and npm.

To compile src/ into build/:

1. npm install — install the build dependencies listed in package.json.
2. npm run build — produce the minified production bundle in build/
   (index.js, index.asset.php, style-index.css, style-index-rtl.css).

For development with an unminified build and file watching, run npm start
instead of npm run build.

Both src/ and build/ are shipped inside the distributed plugin ZIP so the
compiled code can always be traced back to, and regenerated from, its source.