by citecue 1 (0 reviews)

CiteCue AI Auto-Fix

Name: CiteCue AI Auto-Fix
Author: citecue

AEO for WordPress: answers AI crawlers with a CiteCue-optimized version of the page they asked for, and fills your SEO plugin's metadata gaps.

CiteCue AI Auto-Fix ranks #53,141 among WordPress.org plugins with 1+ active installations, is #7,243 of 14,124 in the E-commerce category, a 1/5 rating from 0 reviews, and was last updated Sep 16, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7 (Current: 7.1.4)

v1.2.1 Current Version v1.2.1

Updated 1 month ago Last Update on 16 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#7,243 of 14,124 in E-commerce

View on WordPress.org

Rank

#53,141

— No change

Active Installs

-66.7%

KW Avg Position

131

2 worse

Downloads

282

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 40%

0+ 10+

40,204

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 6 more installs to reach 10+

Rank Changes

Current #53,141

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.2.1
Last Updated: Sep 16, 2026
Requires WP: 5.8+
Tested Up To: 7
PHP Version: 7.4 or higher
Author: citecue

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

AI AI Crawlers ai seo gptbot woocommerce

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

MonsterInsights – Google Analytics Dashboard for WordPress (Website Stats Made Easy)

Google for WooCommerce

800K+ installs

#74

WooPayments: Integrated WooCommerce Payments

800K+ installs

#76

WooCommerce PayPal Payments

800K+ installs

#82

WooCommerce Stripe Payment Gateway

700K+ installs

#85

WooCommerce Tax (formerly WooCommerce Shipping & Tax)

500K+ installs

#115

View all Ecommerce plugins

Frequently Asked Questions

Common questions about CiteCue AI Auto-Fix

No. Clicking "Connect to CiteCue" issues a key for this site and stores it for you. The manual route stays available for installs that cannot redirect through CiteCue.

Settings → CiteCue → "Verify installation" requests your own llms.txt as an AI crawler and confirms the plugin answered. It runs automatically right after you connect. The usual cause of a failure is a full-page cache or CDN answering before WordPress loads. To check a page by hand, request one you have optimized on CiteCue's Auto-Fix page and look for the "x-citecue: served" header: curl -si -A GPTBot https://your-site.com/a-page-you-optimized/ | grep -i x-citecue Use curl or a logged-out browser — logged-in users always get the normal site.

Almost always because CiteCue has no optimized version of that URL yet. Connecting sets up delivery; it does not generate pages. Add and generate them on CiteCue's Auto-Fix page, then re-test — waiting a minute first, because a miss is remembered for 60 seconds and an immediate retry will not call CiteCue at all. Settings → CiteCue → "Recent AI crawler activity" tells you which it is. A "passthrough" row for the URL means the plugin ran and CiteCue reported no optimized page. An "error" row means the call to CiteCue failed. No row at all can mean either that the plugin declined before calling CiteCue (a recent miss, a backed-off connection, serving switched off) or that a full-page cache or CDN answered before WordPress ran.

No, and the distinction is the one search engines draw: cloaking is showing a crawler different content than a person in order to manipulate ranking. The optimized page goes only to AI assistants that identify themselves in their User-Agent, never to a person, and it carries the same facts as the page it stands for. Google appears on both sides of that line and the difference matters: GoogleOther, which Google uses for its AI products, is in the crawler registry and is served the optimized page; Googlebot, which crawls for Search, is not in the registry and gets your ordinary page. What a person and Googlebot both receive is your page, plus CiteCue's metadata in the head, plus a page enhancement on the pages where you approved one. All three are identical for both — nothing is shown to a crawler and withheld from a reader, which is the test that actually matters.

Not for your visitors. On a page CiteCue has something for, the plugin reads a cached block and adds it to the response; nothing on that path calls out to the network. On a page it has nothing cached for, it injects nothing and queues the fetch for WP-Cron, so the first visitor to a cold URL pays one un-enriched view rather than one slow one. Requests from recognised AI crawlers are handled differently on purpose: that path may make a live lookup, because only a bot is waiting for it. It is bounded by a three-second timeout and a per-minute lookup budget, and a circuit breaker stops the plugin trying at all while CiteCue is unreachable, so a slow or failing CiteCue costs those requests a passthrough rather than an open-ended wait.

No. Only requests whose User-Agent matches the AI-crawler registry are served the optimized page, and those responses are never cached for regular traffic. Two things are added for everyone, deliberately. Enriched metadata is head-only tags describing the page a visitor is already looking at. A page enhancement, where you have approved one, is a short facts-and-FAQ section at the end of that page. Both are additions to your page; neither rewrites it, and neither is shown to crawlers and withheld from people.

No. CiteCue reads what your theme, WordPress and your SEO plugin actually printed into <head>, and adds only the tags none of them emitted — checking the output rather than looking for a particular plugin, so it is equally correct with an SEO plugin nobody has heard of. A site where Yoast already handles the title, description, canonical, OpenGraph and schema gets nothing added, which is the right answer. A site where it handles the basics but emits no OpenGraph gets the OpenGraph tags. CiteCue's tags carry a data-citecue attribute, so View Source tells you exactly which ones it added. To hand a slot back to CiteCue, remove your SEO plugin's copy of that tag and re-add CiteCue's through the citecue_seo_head_tags filter. To switch the whole thing off, untick "Enrich page metadata" under Settings → CiteCue.

Nothing visible: a circuit breaker stops API calls for a minute and every crawler request falls through to your normal page (or a cached optimized copy).

By default it is created as a draft. You can raise the cap to "Pending review" or "Published" in the settings.

Yes. Store pages (cart, checkout, account, all WooCommerce endpoints) are never intercepted, and product/shop pages are served optimized like any other page. With WooCommerce active, pushed content may also create draft products or enrich existing ones (matched by SKU, only with an explicit force flag).