Integrations: WordPress, Astro and Next.js, so the fixes go live in one click
The integrations are how a fix card stops being advice. On WordPress the Citeon Connect plugin renders the JSON-LD, serves llms.txt and the robots rules server side and applies them in one click; on Astro and Next.js three open source packages do the same and render the articles Citeon writes; Google connects read only for Search Console and GA4. Each one is described here exactly, including what it never touches.
- WordPress: plugin 1.1.0, JSON-LD in the head, /llms.txt, robots directives, all server side; nothing written into your theme or posts; deactivate to revert.
- Astro and Next.js: three MIT packages, 0.2.3, never throw: 8 s timeout, one retry, 60 s cache, stale beats broken.
- Google: Search Console and GA4 with read only scopes, one sign in, credentials stored encrypted.
What the integrations are for
AI crawlers do not run JavaScript. A schema block added by a tag manager, an llms.txt served by a client side route, a robots rule that exists only in a settings screen: none of these reach them. The integrations exist to put the files where the crawlers read them, on your own domain, rendered by the server, and to let the dashboard apply a fix and check it on the live site without a developer in between.
WordPress: the Citeon Connect plugin
| What it does | How |
|---|---|
| JSON-LD schema in the head | Organization or LocalBusiness markup, rendered server side on every page |
| /llms.txt | Served from your domain, grounded in your real pages: home, blog, every published piece |
| robots.txt directives | Rules that allow the AI crawlers, filtered into the file WordPress serves |
| Apply in one click | Citeon writes the files over the WordPress REST API with the Application Password you provide; LiteSpeed, W3 Total Cache, WP Rocket and WP Super Cache are purged so the change shows at once |
| Status page | A branded page in the admin that shows what is live |
| Revert | Deactivate the plugin and everything it added is gone; it never writes into your theme, posts or content |
Version 1.1.0. Requires WordPress 5.6 and PHP 7.4 or later. GPLv2 or later. Not on the WordPress.org directory as of 7 October 2026; installs from the zip through Plugins, Add New, Upload.
Astro and Next.js: the Connect packages
| Package | What it is |
|---|---|
| citeon-connect | The core client: fetches the pieces Citeon publishes, the AI readiness files and reports AI reads. Never throws: 8 s timeout, one retry, in flight deduplication, a 60 s in-memory cache (bypassed when Next owns caching), strict builds on request, sitemapEntries for your sitemap |
| citeon-astro | The Astro integration: renders the pieces on your site, serves llms.txt, the JSON-LD and the robots rules from your domain |
| citeon-next | The Next.js helpers: the fetchers, an article component, llms.txt and the files |
All three MIT, version 0.2.3 on npm on 7 October 2026. Keyed by your site key against Citeon's public content API: posts, files and reads.
When a piece is approved, Citeon flips it to published, links it on your site, and pings your revalidate route and, for a static build, your deploy hook, so the page exists within the build, not a day later.
Apply, then verify on the live site
A fix is only done when the live site shows it. After a file is applied the Verify panel fetches your site and checks the schema, the llms.txt and the robots rules the card changed, with a link to Google's Rich Results Test. The next daily scan then shows whether the engines' answers moved. Credentials for WordPress are stored encrypted (AES-256-GCM) and are used only to apply what you approved.
Rendered by the server, on your domain, checked on the live site. Or it is not applied.
Citeon AI, the integration rule
Google: Search Console and GA4, read only
| Product | Scope | What it gives |
|---|---|---|
| Search Console | webmasters.readonly | Queries, pages, clicks and impressions, the search side of visits from AI |
| GA4 | analytics.readonly | Sessions and conversions as Google counts them, for the cross check |
One Connect with Google sign in through Google's own consent screen; the properties on that account are matched to your website. Citeon AI cannot change anything in either product.
Shopify, Webflow, Wix, Squarespace, Nuxt
Citeon detects which platform a site runs on, from the audit or a live fetch of the homepage, so a fix card never describes the wrong stack. On these platforms the generated files are produced for download and the card says where each one goes; one click apply is not built for them, and this page says so rather than listing them as integrations. Where the fixes come from: the fix cards; what the connectors publish: the content autopilot; the plans: pricing.
Questions people ask
What does the Citeon Connect WordPress plugin do?
Three things the WordPress REST API cannot do on its own, all rendered server side so AI crawlers, which do not run JavaScript, can read them: JSON-LD schema in the head (Organization or LocalBusiness), a /llms.txt file, and robots.txt directives that allow the AI crawlers. Citeon applies the files over the REST API with the Application Password you provide; nothing is written into your theme, posts or content, and deactivating the plugin reverts everything. Version 1.1.0, WordPress 5.6 and PHP 7.4 or later, GPLv2.
Is the plugin on the WordPress.org directory?
Not as of 7 October 2026. It ships as a zip from this site and installs through Plugins, Add New, Upload.
What do the Astro and Next.js packages do?
citeon-connect is the core client; citeon-astro and citeon-next add the framework pieces. They render on your site the articles Citeon writes, serve llms.txt, the JSON-LD and the robots rules from your own domain, add the pieces to your sitemap, and report AI reads back. Version 0.2.3, MIT licence, on npm.
What happens if Citeon is down while my site builds?
Nothing breaks. The core client never throws: 8 second timeout, one retry, a 60 second in-memory cache, and a stale answer rather than a broken page. Pass strict: true if you prefer a build to fail instead.
How does a fix get verified?
After a file is applied, the Verify panel in the dashboard fetches your live site and checks the schema, the llms.txt and the robots rules it changed, with a link to Google's Rich Results Test. On WordPress the common caches (LiteSpeed, W3 Total Cache, WP Rocket, WP Super Cache) are purged on apply, so the live check sees the change at once.
What does the Google connection read?
Search Console with the webmasters.readonly scope and GA4 with analytics.readonly, granted through Google's own consent screen in one sign in. Read only: Citeon AI cannot change anything in either product. Credentials are stored encrypted.
Sources
- Citeon Connect for WordPress, version 1.1.0 (plugin header and readme). WordPress 5.6+, PHP 7.4+, GPLv2 or later
- citeon-connect, citeon-astro, citeon-next on npm. 0.2.3, MIT, read 7 October 2026
- Citeon AI, Connect with Google (lib/google-oauth.ts). webmasters.readonly and analytics.readonly
- Google, Optimizing your website for generative AI features on Google Search. crawlable content; no special files required by Google