WordPress.org

Plugin Directory

AI Search Optimization – llms.txt, Schema & AEO Audit – Citevera

AI Search Optimization – llms.txt, Schema & AEO Audit – Citevera

Wopisanje

Your content is not getting cited by AI answer engines. Classic SEO plugins (Yoast, RankMath, AIOSEO) optimize for Google’s blue links. Citevera optimizes for the new layer that sits above them – the one that writes the answer.

Citevera is the WordPress plugin for AI search optimization. It makes your site citable by ChatGPT, Perplexity, Gemini, and Google AI Overviews, with one-click fixes that don’t require editing theme code or touching header templates.

Who this is for

  • Site owners who have noticed their brand never appears in AI-generated answers.
  • Marketing teams that want to stay ahead of the AI-search shift.
  • Agencies supporting clients through the AEO / GEO transition.

Why Citevera

  • Written for AI answer engines, not retrofitted from classic SEO.
  • Plays nicely with Yoast, RankMath, and AIOSEO – never duplicates schema they already emit.
  • Free tier makes zero external HTTP calls. Your data stays on your WordPress server.
  • Paid tier connects to the same audit pipeline behind scan.citevera.com, so your WP plugin and your SaaS account share one license.
  • Citevera also supports non-WordPress sites through a SKILL.md export for Claude Code. Full documentation at https://citevera.com/docs/claude-code-integration.

Free features

  • One-click site audit with the rule-based checklist used by scan.citevera.com.
  • llms.txt generator, served dynamically at yoursite.com/llms.txt with a 1-hour cache.
  • AI-crawler robots.txt control: per-agent Allow / Disallow for GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Google-Extended, CCBot, Applebot-Extended, YouBot, cohere-ai, and Meta-ExternalAgent – plus legacy tokens (anthropic-ai, Claude-Web) honored for older robots.txt files.
  • Schema.org JSON-LD for Organization, WebSite, Article, BreadcrumbList.
  • FAQPage schema, auto-detected from FAQ blocks on posts and pages.
  • Monthly scheduled audit with email alerts when your AI-search readiness score drops.
  • Yoast, RankMath, and AIOSEO compatibility detection.

Premium features (active Citevera license required)

The premium tier connects the plugin to the Citevera cloud service at api.citevera.com. These features call our AI inference pipeline and require an active subscription. See the External services section below for the exact data sent and the Terms / Privacy links.

  • AI-powered cloud audit (calls api.citevera.com). Recommendations marked auto-applicable can be applied from your Citevera dashboard at app.citevera.com; this plugin then applies them on your site (llms.txt, schema JSON-LD, robots rules) within a few minutes.
  • Gutenberg block toolbar: select any paragraph, click „Optimize for AI“, see a diff, accept or decline (calls our AI rewrite service).
  • Sidebar AI-answerability score inside the Gutenberg editor (instant, computed locally).
  • Competitor tracking and monthly client portfolio reports at app.citevera.com.

External services

Citevera Free does not connect to any external service. (The free tier performs self-requests to your own site’s /llms.txt, /robots.txt and sitemap URLs to verify they are being served – loopback checks of the same kind WordPress core’s Site Health uses. No third party is involved.)

When you paste a license key to unlock premium features, Citevera connects to api.citevera.com (operated by Citevera) to:

  • Verify the key and return your tier entitlements (one request on activation; background refresh every 12 hours after).
  • Run cloud audits when you explicitly click „Run full audit“.
  • Rewrite selected content when you explicitly click „Optimize for AI“ in the Gutenberg editor.

The data sent to api.citevera.com during a cloud audit is a summary of your site: post counts, active plugins, active theme, detected schema types, and a sample of up to 10 page contents. The admin previews this exact payload before the first cloud audit runs.

Rewrite requests send only the text you selected plus minimal surrounding context (post title, post type, adjacent paragraphs) for a single AI call.

Terms of service: https://citevera.com/legal/terms
Privacy policy: https://citevera.com/legal/privacy

Development

This plugin ships its full source code inside the deployed zip to comply with WordPress.org Guidelines 1 and 4 (public access to source code and build tools).

PHP source: src/

JavaScript / TypeScript source for the admin React app and the Gutenberg editor integration: assets/admin/src/ and assets/editor/src/

Build configuration: package.json, tsconfig.json, composer.json

To rebuild the compiled JS bundles in assets/admin/build/ and assets/editor/build/:

  1. npm install
  2. npm run build

The build uses @wordpress/scripts (webpack under the hood). PHP autoloading is generated by Composer with: composer install –no-dev –optimize-autoloader

Instalacija

  1. Upload the plugin to your site (Plugins – Add New – Upload Plugin).
  2. Activate Citevera through the Plugins menu.
  3. Navigate to the new Citevera menu in your admin sidebar.
  4. Click „Run audit“ on the Dashboard to see your current AI search readiness score.
  5. Optional: paste a license key on the License screen to unlock premium features.

HSP

What is llms.txt?

llms.txt is a 2024 proposed standard that lets large language models quickly understand a site’s content hierarchy. It works like robots.txt but for AI. Citevera generates one for you, served dynamically at yoursite.com/llms.txt.

Does Citevera conflict with Yoast, RankMath, or AIOSEO?

No. Citevera detects these plugins and defers to them for Organization, Article, and WebSite schema. Citevera only adds what they do not already emit (FAQPage from detected blocks, HowTo, AI-specific fields). You can override this per schema type if you want Citevera’s version to take precedence.

Does Citevera make external HTTP calls in the free version?

No external service is ever contacted in the free version. The plugin makes exactly one kind of network request on its own: requests to your own site’s /llms.txt, /robots.txt and sitemap URLs, to verify they are actually being served the way a crawler would see them (some configurations, such as plain permalinks, silently serve the homepage at these URLs instead). Those requests never leave your site. License verification contacts our server only when you explicitly enter a paid key.

Does this work with the Classic Editor?

Admin area features (audit, schema, llms.txt, robots, license) work with both Classic and Gutenberg editors. Inline block-toolbar rewriting and the sidebar score panel require Gutenberg.

Does this work with WooCommerce?

Yes. Free tier emits Organization / WebSite / Article schema as usual. The Growth tier adds bulk Product schema across your catalogue with per-variation offers, aggregated ratings, brand, and stock state.

Does this work with Elementor / Divi / Bricks / Beaver Builder / Oxygen?

Yes. Citevera detects FAQ patterns across all major page builders. Schema is emitted via wp_head and works regardless of page builder.

Does Citevera track or send my content to any third party in the free tier?

No. Free tier is fully local. Paid features explicitly send summary data (post counts, detected schema types, sample page content) to api.citevera.com for the audit and to our AI inference service for rewriting. The scope is documented on the License screen before the first call.

Where are the paid AI features hosted?

On api.citevera.com, which runs our own AI inference service. No data is sent to OpenAI, Google, or any other public AI provider.

Can I cancel my paid subscription from inside WordPress?

Yes – the License screen links to app.citevera.com where you can pause, downgrade, or cancel at any time.

Does the plugin include its own AI models?

No. The free version is rule-based. Paid features call out to api.citevera.com.

Pohódnoćenja

Za tutón tykač pohódnoćenja njejsu.

Sobuskutkowarjo a wuwiwarjo

„AI Search Optimization – llms.txt, Schema & AEO Audit – Citevera“ je softwara wotewrjeneho žórła. Slědowacy ludźo su k tutomu tykačej přinošowali.

Sobuskutkowarjo

Protokol změnow

1.0.7

  • Fix: the dashboard no longer fails with „Cookie check failed“ after a wp-admin tab has been open for a long time. The plugin now refreshes its WordPress security nonce automatically and retries; if your session has genuinely ended, it says so plainly and offers a one-click reload instead of a retry that could never succeed.
  • Improved error messages when the dashboard cannot load: a permissions problem, a security plugin or host firewall blocking /wp-json/ (with the exact path to allowlist), and a license issue now each get their own explanation, always including the failing URL.
  • The AI visibility score now shows the five AI decision funnel stages (detection, understanding, trust, coverage, conversion) it is computed from, with an explainer. Previously a low visibility score next to healthy readiness bars looked like a bug; they are different measurements, and now the dashboard says so.
  • Fix: axis bars no longer read „First audit“ when audits already exist; a trend arrow appears once there are two audits of the same kind to compare.
  • The sitemap status now reports how many URLs the sitemap declares. A sitemap that is served but declares 0 URLs shows an amber warning instead of a green check – serving an empty sitemap is not a pass.

1.0.6

  • Fix: deactivating a license now releases its activation seat on the licensing server. Previous versions only cleared the key locally, so the seat stayed occupied until it was pruned manually.
  • Fix: the dashboard and audit now VERIFY that /llms.txt, /robots.txt and your sitemap are actually being served (via self-requests to your own site, the way a crawler sees them) instead of reading internal settings. On sites with plain permalinks these URLs silently serve the homepage; the plugin previously reported „Published“ and scored crawlability 100 anyway. Checks tell you exactly what is wrong and how to fix it (usually Settings – Permalinks – Save), report „Not verified“ honestly when a host blocks self-requests, and unverifiable checks are excluded from scoring rather than counted as passing.
  • Redesigned dashboard that matches the WordPress admin look: native grays, clearer score presentation, and honest empty states („Not measured“ instead of a zero score before your first audit).
  • Fix: two dashboard icons rendered as literal placeholder text ([lock] on the cloud-audit link, [-] in the empty activity feed). Both are proper icons now.
  • Fix: the scoring-methodology notice no longer gets relocated into the dashboard header by wp-admin, which also pushed the tier badge out of place.
  • Free tier: the dashboard now flags score decay (a drop since the previous audit, or an audit older than 30 days) and shows the monthly competitor-insight card available on paid plans.
  • Added a one-time review request that appears only after three successful audits and a score improvement. Dismiss it once and it never returns.
  • Copy: rewrite features are now labelled „AI rewrites“ throughout.

1.0.5

  • Fix: license keys issued after the move to Freemius (keys starting with sk_) can now be activated. Previous versions rejected them before contacting the licensing server: the key field uppercased input as you typed and the format check only accepted the legacy CV-XXXX-XXXX-XXXX shape. Legacy CV keys continue to work unchanged.
  • The license screen’s format hint and placeholder now describe both key families.
  • Listing name is now keyword-led (AI Search Optimization – llms.txt, Schema & AEO Audit) so the directory entry says what the plugin does before who made it. Slug, plugin file and wp-admin name are unchanged.

1.0.4

  • Tested and confirmed compatible with WordPress 7.0.
  • Fix: the Gutenberg editor sidebar (Citevera score panel) is now properly wired. The PHP-side registrar was never invoked from the plugin bootstrap, so the editor JS bundle never enqueued.
  • Fix: the „Optimize for AI“ block-toolbar button now appears. The format was registering as a bare span, which collided with core/underline’s bare-span registration and was rejected by rich-text. The format now uses a scoped class (citevera-optimize) so it coexists with core formats.
  • Fix: PluginSidebar imports migrated from @wordpress/edit-post to @wordpress/editor to clear console deprecation warnings on WP 6.6+.
  • Fix: the monthly auto-audit + regression alert emails are now properly scheduled. The cron registrar was never invoked from the plugin bootstrap, so the monthly audit never ran in any prior release.
  • Fix: cron schedule registration now defers to the init hook, eliminating a „_load_textdomain_just_in_time“ notice that fired the first time the cron was registered (added in WP 6.7).

1.0.3

  • Build-tool transparency: deployed zip now ships the JavaScript/TypeScript sources for the admin React app and the Gutenberg editor integration (assets/admin/src, assets/editor/src) alongside the compiled bundles, plus package.json and tsconfig.json. Satisfies WordPress.org Guidelines 1 and 4 (public access to source code and build tools). New „Development“ section in readme.txt documents the rebuild steps.

1.0.2

  • WP.org review compliance: FAQPage schema emission, monthly auto-audit cron, and regression alerts are now free features (previously license-gated). Premium tier continues to gate cloud audits, AI rewrites, and the Gutenberg sidebar score – all of which require the Citevera cloud service.
  • Security: harden /llms.txt output. wp_strip_all_tags() applied to dynamic site fields + X-Content-Type-Options: nosniff response header.
  • Compliance: text domain renamed from ‚citevera‘ to ‚citevera-ai-search-optimization‘ to match plugin slug.
  • Build: stop including .wordpress-org/ in the deploy zip (wp.org pulls it from SVN /assets/).
  • Schema toggle UI: HowTo, SoftwareApplication, and Product entries removed (front-end emission not yet wired; surfacing them as toggles let users enable settings that did not affect output).

1.0.1

  • Fix: upgrade links in the Dashboard and Schema admin screens now point at https://citevera.com/pricing instead of a 404’d URL on app.citevera.com.

1.0.0

  • Initial release.