Ayzeo WordPress Plugin 1.2: Site Audit, IndexNow and AI Crawler Control Inside WordPress

1. What's New in 1.2

Until now the plugin was a thin client for the Ayzeo platform: it sent a page to the API and showed the result. Version 1.2 keeps that and adds a second layer that runs entirely on your own server. Nothing in this layer needs an account, and no AI service is involved:

• Site Audit. A fully algorithmic scan of your most important pages against the Ayzeo rulebook, on demand or once a week, with a technical readiness score, per-page scores, evidence for every check and a recommendation for every finding.
• One-click fixes. Structured data generated from your own content, meta description and Open Graph fallbacks, and an alt text helper. Every fix is previewed before it is applied and can be reverted.
• IndexNow. Automatic submission of new, updated, unpublished and deleted URLs to Bing and the other IndexNow engines, with key handling, a background queue, a readable log and a post list column.
• AI crawler control. One setting writes an explicit robots.txt policy for the 18 AI crawlers Ayzeo tracks, grouped by what they are for.
• llms.txt. The editor now serves your file exactly as you wrote it. Ampersands and angle brackets were escaped in earlier versions.

Connect the plugin to an Ayzeo project and it adds deep scans with AI-specific checks, AI visibility queries and content generation. On a Pro plan it adds the GEO dashboard you see above. The admin interface was rebuilt from scratch on the Ayzeo design system, the plugin is organised in modules, and it ships with a complete German translation.

2. Site Audit on Your Own Server

The audit is the platform's scanner rulebook, ported to PHP and checked against the same test fixtures. A page that passes one of the portable checks in WordPress passes the same check on ayzeo.com. The plugin picks your most important pages, fetches each one the way a crawler sees it, and runs the page-level checks:

• Titles and meta descriptions, including their lengths and duplicates
• Heading hierarchy and canonical tags
• Structured data validity, product schema completeness and sameAs consistency
• Open Graph tags and whether the og:type matches the page
• Author attribution and content freshness
• Image alt coverage, mixed content and render-blocking resources

Site-level checks cover robots.txt and search engine access, AI crawler access and whether the key AI bots have their own rules, sitemap presence and validity, HTTPS, security headers and redirect chains. Every check is a plain algorithm running in PHP. No page content leaves your server, no AI model is called, and the audit runs in the background, on demand or once a week if you switch the weekly audit on.

Below the score, pages are listed worst first with their top issues, and every page has a full report: each check with its evidence, the recommendation and, where the plugin can do it for you, the fix.

3. One-Click Fixes

An audit that only lists problems is a to-do list. Where a check fails and the plugin knows the answer, it offers the fix:

• JSON-LD structured data generated from your own WordPress content: the post, its author, dates and images.
• Meta description and Open Graph fallbacks that only output when no SEO plugin is providing them.
• An alt text helper for images that have none.

Every fix is previewed before it is applied and can be reverted. Suggested titles and descriptions write into your SEO plugin's own fields, so Yoast, Rank Math, All in One SEO and SEOPress keep control of what they already manage and nothing is output twice.

4. IndexNow for Bing and ChatGPT

ChatGPT search runs on Bing's index, which makes fast Bing indexing the most underused lever in GEO. IndexNow is the protocol for that: instead of waiting for a crawl, you tell the engines about a URL the moment it changes, and Bing, Yandex, Seznam, Naver and Yep share the submission. Google does not participate.

Switch IndexNow on and the plugin handles the rest:

• Every publish, update, unpublish, trash and delete of a post or page becomes a submission. Slug changes send the new URL and remove the old one.
• Drafts, private, password protected and noindex pages, and URLs your robots.txt blocks, are never submitted.
• Submissions go through a background queue with retries and land in a log that reads in plain language: what was sent, when, and what the engine answered.
• The plugin generates your key and serves the key file itself, and a Verify button confirms the engines can read it.
• A column in the post list shows the status per post, and one button submits all published URLs, which is the right first step on an existing site.

The screenshot shows a detail we spent real time on. Two IndexNow integrations on one site means two keys, and the engine silently drops every submission that carries the losing key. The plugin detects Yoast Premium, Rank Math, All in One SEO, SEOPress and Microsoft's own IndexNow plugin, names the ones that are active and stays off, with an explicit override if you know what you are doing.

5. AI Crawler Control and llms.txt

Most robots.txt files say nothing about AI crawlers, which leaves the decision to each bot's defaults. The AI crawlers tab writes an explicit policy for the 18 crawlers Ayzeo tracks, grouped by what they are for:

• Search: crawlers that build the index behind AI answers, such as OAI-SearchBot and PerplexityBot. Blocking them removes you from those answers.
• Assistants: fetchers that open a page when a user asks about it, such as ChatGPT-User and Perplexity-User, with a link back to you.
• Training: crawlers that collect text for model training, such as GPTBot and ClaudeBot. Allowing them is how models learn about your brand.

Each bot gets its own group with Allow or Disallow, your existing rules stay untouched, and the plugin's own checks confirm the result. If your site has a physical robots.txt file, the plugin does not edit it behind your back: it shows the exact block to paste.

The llms.txt editor from version 1.1 is on the same screen, with a live preview, and now serves the file exactly as you wrote it.

6. With an Ayzeo Project

Paste an API token from your project settings and the plugin adds the parts that need the platform:

• Deep scans add the AI-specific checks and generate suggested meta tags, JSON-LD and llms.txt content you can apply in one click. Scans now run in the background, so large pages no longer time out, and results are shown inside WordPress.
• AI visibility queries run through the current Ayzeo engine instead of the legacy pipeline. Ask a question and see how the engine answers it and which sources it considered.
• Content pages optimised for AI answers are generated with real research and published straight into WordPress as a draft.

Each token is scoped to one project and validated against your domain. Daily limits for scans and queries depend on your plan and are shown on the Settings page.

7. The GEO Dashboard Inside WordPress

On a Pro plan, the Overview page becomes the Ayzeo dashboard for your project: visibility share, mention rate, citation rate and average mention position, each with the change against the previous seven days once there is enough data, plus sentiment, a trend chart over 7, 30 or 90 days, your competitors ranked next to your own brand with their logos, and your top tracked prompts by visibility. A widget on the WordPress dashboard shows the headline numbers on every login.

The plugin does not try to replace the platform. The key-figure tiles link into the full analysis on ayzeo.com, so the moment you want to know why a number moved, you are one click away.

8. Upgrading from 1.1

• Requirements: WordPress 6.5 or newer and PHP 7.4 or newer. Version 1.2 is tested up to WordPress 7.1.
• What carries over: your API token, the project connection and your llms.txt content. The old menu entries redirect to the new pages.
• Smaller tables: analysis results are no longer stored with a screenshot.
• Languages: English and German.
• Where to get it: the WordPress plugin directory, or the ZIP on our WordPress page.

After the update, open Ayzeo, Site Audit and run your first audit. Then open Indexing and Crawlers to switch on IndexNow and review the AI crawler policy. Both take a minute.

9. Frequently Asked Questions

Q: Do I need an Ayzeo account to use version 1.2?

A: Not for the Site Audit, the one-click fixes, IndexNow, the AI crawler robots.txt policy or llms.txt. Those work on a plain WordPress install. An Ayzeo project adds deep scans with AI checks, AI visibility queries and content generation, and a Pro plan adds the GEO dashboard inside WordPress.

Q: Does the plugin submit pages to Bing via IndexNow?

A: Yes. Switch IndexNow on and the plugin submits every new and updated URL, and tells the engines when a URL is unpublished or deleted. It generates the key, serves the key file, batches submissions in the background and logs the result of each one. IndexNow reaches Bing, Yandex, Seznam, Naver and Yep, and ChatGPT search reads Bing. Google does not participate.

Q: Is the Site Audit the same as the website analysis on ayzeo.com?

A: It uses the same rulebook, so the algorithmic checks give the same result in both places. The audit runs on your server without any AI service. A deep scan through your Ayzeo project adds the AI-specific checks and generates suggested meta tags, JSON-LD and llms.txt content.

Q: Will it conflict with Yoast, Rank Math, All in One SEO or SEOPress?

A: No. The plugin detects them and steps back. If one of them already submits to IndexNow, Ayzeo shows a notice and stays off so you never end up with two keys. Meta description and Open Graph fallbacks only output when no SEO plugin provides them, and applying a suggested title or description writes into your SEO plugin's own fields.

Q: Which AI crawlers does the robots.txt policy cover?

A: The 18 crawlers Ayzeo tracks, grouped into search, assistants and training, including GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, anthropic-ai, PerplexityBot, Perplexity-User and DuckAssistBot. Each one gets its own Allow or Disallow group and your existing rules stay untouched.

Q: Will the audit slow down my site?

A: No. It runs in the background, on demand or once a week if you switch the weekly audit on, and fetches your pages the same way any visitor would. Nothing is added to your front end except the llms.txt endpoint, the IndexNow key file, the AI crawler policy in robots.txt and any structured data or meta tags you explicitly asked the plugin to output.

Q: What are the requirements and what does it cost?

A: WordPress 6.5 or newer, PHP 7.4 or newer, tested up to WordPress 7.1. The plugin is free, and the local features stay free on any number of sites. The connected features need an Ayzeo project on a free trial or a paid plan, and the GEO dashboard inside WordPress needs a Pro plan.

Get Version 1.2

Update from the Plugins screen if you already run the plugin, or install it fresh from the WordPress plugin directory. If you want AI visibility tracking on top of the local tools, the Pro trial covers everything in this post, including the GEO dashboard inside WordPress.

Key Takeaways

• Works without an account: Site Audit, fixes, IndexNow, AI crawler policy and llms.txt run on your own server, with no AI service involved.
• Same rulebook as the platform: the audit is the Ayzeo scanner ported to PHP and checked against the same fixtures.
• IndexNow is the ChatGPT lever: ChatGPT search reads Bing, and the plugin gets every new and updated page into Bing within minutes, without fighting other plugins over the key.
• Explicit AI crawler policy: 18 crawlers, grouped by purpose, one toggle each, existing rules untouched.
• Pro brings the dashboard into WordPress: the five GEO KPIs, the trend, your competitors and prompt status, one click from the full analysis.