Zen GEO – Generative Engine Optimization for WordPress

What this does that an llms.txt generator does not

Publishing an llms.txt file is a few lines of code, and plenty of plugins stop there. Zen GEO treats that as one output of the job rather than the job.

◎It scores your content — and names the fix

Twelve weighted checks model how retrieval-augmented systems actually behave: they chunk a page, embed the chunks, retrieve a few, and quote whichever one answers the question on its own. Every failing check gives a specific instruction, not a colour.

▤It reads page builders

Content is extracted from Elementor's stored element tree, so pages built with Elementor, its Pro widgets or third-party widgets are scored on their real text — not on an empty post_content, which is where most content analysers give up.

◐It shows which assistant read which page

Not just that AI crawlers visited: a per-page, per-crawler breakdown with 90 days of history, stored in your own database, with no IP addresses recorded.

?It finds the FAQ you already built

Question-and-answer pairs are read out of Elementor accordions, toggles and Details blocks and published as FAQPage data, with nothing retyped. Only question-shaped headings count, so a list of section names is left alone.

⇄It defers instead of competing

Yoast SEO, Rank Math, All in One SEO, SEOPress and Slim SEO are detected, and Zen GEO stands down where they already emit structured data. Two competing Article graphs on one URL is worse than one.

⌘It works where you work

A tab inside the Elementor editor beside Widgets and Globals, a WordPress meta box, a Dashboard widget, a sortable post-list column, a site-wide audit with CSV export, and WP-CLI commands for bulk work.

Publish a machine-readable map of your site

Surface	What it is
`/llms.txt`	A Markdown index of your site following the llmstxt.org convention: your site name, a summary, and annotated links to the pages that matter.
`/llms-full.txt`	Optionally, the same pages with their full text inlined, for assistants that fetch one document instead of crawling.
`?zengeo=md`	Every page as clean Markdown — no theme, no navigation, no cookie banner. Advertised in each page's `<head>` so crawlers find it on their own.
JSON-LD	One consolidated graph — Organization or Person, WebSite, Article/WebPage, BreadcrumbList — cross-referenced so an engine reads one coherent statement. Plus sameAs, FAQPage, speakable, LocalBusiness and WooCommerce Product.
`/robots.txt`	Per-crawler allow or disallow for 19 AI crawlers, plus optional enforced 403 blocking at the PHP layer and custom validated directives.

Decide who may read your site

Crawlers are grouped by what they actually do — model training, answer-engine indexing, or a fetch triggered by a real person — because blocking the second kind removes you from AI answers entirely, and most people who say "block AI" do not mean that.

Blocking a training crawler is not the same as blocking an answer engine. Blocking training affects future model weights. Blocking answer-engine crawlers is what removes you from today's answers and citations. Zen GEO separates them so that mistake is hard to make by accident.

Honest limits

The category is full of overpromising. To be clear about what this does not do:

It does not track "your ChatGPT rankings". That needs a paid third-party service; a WordPress plugin cannot see it.
Crawler analytics are a trend, not an audit. Hits are counted when a request reaches PHP, so a full-page cache or CDN serving bots directly will under-report.
Enforced blocking is user-agent matching. It stops crawlers that identify themselves honestly; it does not stop an impersonator using a browser user-agent string. Anything on a public URL can be copied by someone determined to copy it.
It is not an SEO plugin. It does not manage titles, meta descriptions, canonicals, redirects or XML sitemaps. Keep the SEO plugin you have.

Zen GEO — Generative Engine Optimization