Nurevo AEO – AI Search Optimization (AEO/GEO), llms.txt & Schema

When people ask ChatGPT, Perplexity, Google AI Overviews, Gemini or Claude for a business like yours, the answer is built from what those AIs can read about you. Nurevo AEO makes sure they can read your facts correctly: who you are, what you sell, where you are and how to reach you.

This is AEO (Answer Engine Optimization), also called GEO (Generative Engine Optimization). Nurevo AEO checks your site, tells you what is missing, and publishes the missing pieces in the formats AI crawlers read: schema.org structured data, llms.txt and AI crawler rules. All of it is rendered on your own server, so crawlers that never run JavaScript still see it.

Built for three kinds of sites

• Local businesses – shops, salons, clinics, restaurants, hotels and offices: address, phone, opening hours, services and FAQ.
• Online shops – an OnlineStore with your product catalogue, prices and stock where known, and your return policy. Works with WooCommerce without duplicating its product markup.
• B2B, SaaS and professional services – an Organization with the services or software you offer, plus your pricing, case study and FAQ pages in llms.txt.

Keep your SEO plugin. Nurevo AEO adds the facts Yoast SEO, Rank Math, All in One SEO or Slim SEO leave out, inside the structured data they already publish. One graph, one business, no duplicates.

In your language. The plugin and its dashboard are available in 59 locales.

Ready for AI agents. On WordPress 6.9 and later it offers read-only abilities through the WordPress Abilities API, so AI assistants connected with the official MCP Adapter can read your AEO status and business facts.

Free, and genuinely complete

Everything below runs on the free plan. No license key, no trial period, no feature timer.

• AEO score — a 0 to 100 score with traffic-light alerts and a concrete checklist of what to fix.
• One-click fixes — basic schema.org structured data, llms.txt and AI crawler access are fixed from the admin screen.
• Server-rendered schema.org JSON-LD — emitted into the page HTML, so crawlers that never run JavaScript still read it.
• llms.txt — served at /llms.txt. Generated inside the plugin from your WordPress content, so it works with no site key and no network access.
• AI crawler rules — robots.txt entries that allow the crawlers AI search uses to read and cite your pages: OAI-SearchBot and ChatGPT-User (ChatGPT), Claude-SearchBot and Claude-User (Claude), PerplexityBot and Perplexity-User (Perplexity). Your existing robots.txt rules, such as /wp-admin/, keep applying to them.
• Your choice on AI training — crawlers that collect content to train AI models (GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot) are left to your robots.txt by default. You can allow or block them in one click. Blocking them does not affect AI search or your AEO score.
• Business data extraction — reads your existing SEO plugin settings, WordPress options and clearly labelled public content to fill in blank fields only. Values you have typed are never overwritten. The WordPress administrator email is never used as your business email.

Works alongside Yoast SEO, Rank Math, All in One SEO and Slim SEO

Keep your SEO plugin. The two jobs are different: your SEO plugin handles search ranking, Nurevo AEO handles whether an AI can read your facts.

Nurevo AEO does not publish a second set of structured data next to your SEO plugin’s. It adds the missing facts to the one your SEO plugin already publishes.

With Yoast SEO, Rank Math, All in One SEO or Slim SEO, Nurevo AEO hooks the filter each of them uses to build its JSON-LD graph (wpseo_schema_graph, rank_math/schema/validated_data, aioseo_schema_output, slim_seo_schema_graph) and adds only what is missing:

• Your business node gets the address, telephone, opening hours, description and email it lacks, and a more specific type such as HairSalon or Dentist. Values your SEO plugin already sets are never overwritten.
• FAQ questions you entered in Nurevo are added to the page’s existing FAQPage, skipping any question it already answers, or as an FAQPage of their own where the page has none (Slim SEO publishes no FAQPage) – only on the page where you placed the Nurevo FAQ block or the [nurevo_faq] shortcode.
• Services you entered are added, linked to your business node.
• WebSite, WebPage, Article and breadcrumbs stay exactly as your SEO plugin publishes them.

The page ends up with one graph, from your SEO plugin, describing one business.

That matters because the free tiers of these plugins usually publish an Organization with a name, a URL and a logo, but not the address, telephone or opening hours an AI needs to describe a local business. In Yoast SEO and AIOSEO those belong to paid local-SEO add-ons; Rank Math’s free version can publish one location if you fill in its Local SEO settings; Slim SEO publishes an Organization with your site name and URL (and logo, if set). Nurevo AEO fills whatever is still missing, without overwriting what is already there.

Slim SEO prints its graph at the end of the page rather than in <head>, so with Slim SEO Nurevo AEO waits until then. If Slim SEO’s schema is turned off (Settings > Slim SEO > Features), Nurevo AEO publishes its own graph, as with any other setup.

With any other setup – SEOPress, The SEO Framework, a theme’s own schema, or no SEO plugin – Nurevo AEO prints its own graph at the end of <head>. It leaves out what your other plugins already publish and puts the business facts under their business @id, so the two describe one business rather than two.

Plans

• Free — 0 JPY. Everything listed above, in full.
• Standard — 3,000 JPY/month (USD 20 outside Japan). “Always current”. AEO criteria keep changing. Licensed sites receive the current central ruleset from the Nurevo service and get a notice in wp-admin when the criteria change. Free sites keep running on the ruleset bundled with the plugin.
• Pro — from 14,800 JPY/month (USD 99 outside Japan). AI visibility measurement: how often your business appears in AI answers, with competitor comparison and history. This is a beta feature and the numbers should be read as indicative. AI answers change from day to day, so no plugin can guarantee that an AI will mention you.

No paid PHP is bundled in this plugin and nothing in the download is locked. The only difference a license makes is which ruleset the Nurevo service returns and whether the measurement screen is enabled. Paid plans require an account at https://nurevo.jp/ and are billed there, not through WordPress.

External services

This plugin relies on the Nurevo service, operated by Bestie. LLC. It is not required for the free output described above.

Nothing is sent from your public pages by default. Installing and enabling the plugin adds no third-party script to your site and transmits no visitor data. The structured data, llms.txt and AI crawler rules are all produced by the plugin itself, on your own server.

The browser tag is opt-in and off by default. Settings has an optional “Load the Nurevo browser tag on public pages” checkbox, unchecked unless you tick it. While it is off, no script is enqueued and nothing about your visitors reaches the service. If you turn it on, a script is loaded from the configured service URL (by default https://nurevo.jp/tag.js) on every public page view, carrying your public site key. It reports public form structure — field names, types, labels, selectors and option counts — and privacy-safe submission outcomes. It is designed not to transmit values a visitor typed: no names, email addresses, phone numbers, message bodies or payment details. Unticking the box stops it immediately. You do not need it for AEO.

Nothing is sent until you agree. Activating the plugin makes no request at all. The first time you open the AEO screen it explains what the diagnosis sends and asks you to tick a consent box and press “Run diagnosis”. Until you do, or until you pair the site with a pairing code (which is itself an explicit request to connect), the plugin does not contact the Nurevo service. Your consent is stored as a WordPress option and removed when the plugin is uninstalled.

Requests the plugin makes, and when. All of them go to the Nurevo service URL in Settings (by default https://nurevo.jp). None of them carries visitor data.

After you agree (Run diagnosis), without a key:

• AEO diagnosis — when you press “Run diagnosis”, and afterwards when you open the AEO screen, press “Check again” or apply a one-click fix. Sends your home URL and your WordPress language. The service then fetches your public front page, /robots.txt and /llms.txt. Endpoint: /api/aeo/score.

When you connect the site (pairing code or licence key) — connecting counts as consent:

• Pairing — sends the pairing code you entered and your home URL. Endpoint: /api/pair.
• Licence — sends the licence key you entered and your home URL. Endpoint: /api/license/bind.
• Site key management — sends your home URL and the owner email from Settings. Endpoints: /api/site-key, /api/site-key/regenerate, /api/site-key/disable.

Once the site is connected (site key or site ID present), in wp-admin and from WP-Cron twice a day:

• Diagnosis history — sends the site key, site ID and language. Endpoint: /api/sites/{id}/aeo-score.
• Business profile — reads and updates the profile the service holds. Sends the business details from Settings: name, description, address, telephone, opening hours, business type, website URL and business email. Endpoint: /api/sites/{id}/profile (GET and PUT).
• Catalogue — sends what the site offers so the service can publish the same facts: WooCommerce product names, URLs, SKUs, prices, currency, stock status and categories; the services, FAQ questions and answers entered in Settings; and the titles and URLs of your 30 most recently updated published posts and pages. Endpoint: /api/sites/{id}/catalog (PUT).
• Ruleset — sends the site key and receives the current output criteria and plan. When the service suggests changes (for example turning on llms.txt), they are shown in wp-admin and applied only when an administrator clicks Apply. Endpoint: /api/tag/config.
• Site insights — sends the site key and host. Endpoint: /api/site-insights.
• AI visibility measurement (Pro, beta) — sends the site key and site ID. Endpoint: /api/sites/{id}/sov.
• Change record (learning events) — a compact record of changes to this plugin’s own settings, sent with the sync above in small batches, each with an id so a resend is stored once; while the service cannot be reached they wait in a WordPress option (at most 200, oldest dropped first). Each event says which output was switched on or off (structured data, llms.txt, AI crawler rules, the browser tag), which business fields were filled in or cleared (the field names, never what was entered), the site type, which SEO plugin is active (Yoast SEO, Rank Math, AIOSEO, Slim SEO or none), the plugin version, the number of FAQ entries, services and products, and which one-click fix was applied. Nothing is recorded before the site is connected. Nurevo uses these records, together with the diagnosis scores and AI search measurements (including one baseline measurement taken when the site is added in the dashboard, before the plugin is connected), in aggregate across sites to learn which changes help businesses appear in AI answers; no score is changed automatically by it. Endpoint: /api/sites/{id}/events (POST).
• Free AI check (Free and Standard) — reads this month’s result with the site key and site ID; “Check now” sends the site ID with the profile token. Endpoint: /api/sites/{id}/sov/free-check (GET and POST). Once a month the Nurevo service itself puts three questions a customer might ask, built from your business type and area (never your business name), to Perplexity (https://www.perplexity.ai/, terms: https://www.perplexity.ai/hub/legal/terms-of-service, privacy: https://www.perplexity.ai/hub/legal/privacy-policy) and stores whether the answers named your business or cited your site. The plugin itself never contacts Perplexity.

The plugin also requests your own front page once a day (a loopback request to your own server, not to Nurevo) to see which structured data your other plugins already publish.

The site key is a public identifier. It appears in markup served to browsers, so never put a server secret in it. The license key is separate and is never printed into public pages.

The plugin suggests matching text for your site’s privacy policy under Settings > Privacy (Policy Guide).

By using these features you agree to the service’s terms. Please read them before entering a key:

• Privacy Policy: https://nurevo.jp/privacy
• Terms of Service: https://nurevo.jp/terms