How to Integrate AigeoRadar with WordPress: Complete Setup & Usage Guide

WordPress powers millions of business websites — but traditional SEO alone no longer controls how AI assistants recommend your brand. Tools like ChatGPT, Perplexity, and Gemini look for structured discovery signals: files such as llms.txt, machine-readable entity data, and clear homepage metadata.

AigeoRadar analyzes your site, builds an AI Discovery package from your crawl and GEO analysis, and the AigeoRadar Connector WordPress plugin publishes that package to your live site in one click — no FTP, no child-theme edits, no copying JSON by hand.

This guide covers everything you need: prerequisites, installation, connection, deployment, verification, updates, plan requirements, and how the plugin differs from WordPress content publishing inside AigeoRadar.

Two WordPress integrations — don’t mix them up

AigeoRadar offers two separate WordPress features. They solve different problems:

Feature	Purpose	Where to set it up
AigeoRadar Connector plugin	Deploy AI discovery assets (llms.txt, entity.json, ai-feed.xml, knowledge.json) and homepage head tags	Site → Publishing Integrations → WordPress Plugin
WordPress REST publishing	Publish generated blog posts, FAQ pages, and landing pages from Content Factory	Same page → Publishing destinations (username + application password)

If your goal is AI visibility and GEO optimization, start with the Connector plugin. Use REST publishing only when you want AigeoRadar to push drafted content into WordPress posts and pages.

What the plugin deploys to your site

After you run a GEO analysis in AigeoRadar and click Deploy now in WordPress, the following goes live:

Asset	URL (typical)	What it does
llms.txt	https://yoursite.com/llms.txt	Your LLM site guide — key pages, services, brand context, and safety rules for AI systems
entity.json	https://yoursite.com/entity.json	Structured business entity data AI crawlers and RAG pipelines can ingest
ai-feed.xml	https://yoursite.com/ai-feed.xml	Capability feed describing what your business offers and how AI should reference you
knowledge.json	https://yoursite.com/knowledge.json	Structured Q&A knowledge base built from your analysis
Homepage head tags	View source on your front page	AI discovery meta tags and JSON-LD injected via wp_head on the homepage only

The plugin stores assets securely and serves them at the root URLs above. If your server cannot write files to the web root, the plugin falls back to virtual routes — the same URLs still work without manual file uploads.

Prerequisites before you connect

1. An AigeoRadar account with a site added (your WordPress domain).
2. Domain verification completed in AigeoRadar (DNS, HTML file, or meta tag).
3. At least one completed GEO analysis — the AI Discovery package is generated from your crawl and analysis results.
4. Pro plan or higher — WordPress plugin sync (wordpress_plugin_sync) is included on Pro, Agency, and Enterprise plans. Free and Starter users see an upgrade prompt.
5. WordPress 6.0+ and PHP 8.1+ on your hosting.
6. Admin access to both AigeoRadar and your WordPress dashboard.

Tip: Fill in your Business Profile in AigeoRadar (Site → Integrations) before deploying. Richer profile data improves entity.json and knowledge.json quality.

Step-by-step: connect and deploy

Step 1 — Open Publishing Integrations in AigeoRadar

Go to Dashboard → Sites → [your domain] → Publishing Integrations.

In the AigeoRadar WordPress Plugin card you will see:

• API base URL: https://app.aigeoradar.com/api/v1
• Site UUID: unique ID for your site (copy this)
• Download plugin ZIP button
• Generate connect token button

Step 2 — Download and install the plugin

1. Click Download plugin ZIP.
2. In WordPress: Plugins → Add New → Upload Plugin.
3. Upload the ZIP and click Install Now, then Activate.

The plugin appears as AigeoRadar Connector. After activation, go to Settings → AigeoRadar (or use the plugin’s Settings link on the Plugins screen).

Step 3 — Generate a connect token

Back in AigeoRadar, click Generate connect token.

• The token is one-time use and expires in 15 minutes.
• Copy all three values: API URL, Site UUID, and the connect token.

Step 4 — Connect WordPress to AigeoRadar

In WordPress (Settings → AigeoRadar):

1. Paste the API base URL (https://app.aigeoradar.com/api/v1).
2. Paste your Site UUID.
3. Paste the connect token.
4. Click Connect.

On success, the plugin stores encrypted credentials and shows a Connected status. WordPress can now pull your latest discovery package from AigeoRadar’s Integration API.

Step 5 — Deploy to your live site

Click Deploy now in the WordPress plugin admin.

The plugin downloads the latest package, writes (or virtually serves) discovery files, and enables homepage head injection. Deployment typically completes in seconds.

Step 6 — Verify everything is live

Run these quick checks:

1. Open https://yoursite.com/llms.txt — you should see readable UTF-8 text describing your business and key pages.
2. Open https://yoursite.com/entity.json — valid JSON with your organization entity.
3. Open https://yoursite.com/ai-feed.xml and https://yoursite.com/knowledge.json.
4. View your homepage source (Ctrl+U) and search for ai-discovery or JSON-LD organization schema.
5. Optionally, run a new analysis in AigeoRadar — the real scan should detect deployed AI discovery assets.

Understanding status badges in WordPress

The plugin admin shows clear status indicators:

• Connected — WordPress is linked to your AigeoRadar site. Credentials are stored.
• Aigeo Active — Your subscription includes WordPress sync. You can deploy and redeploy updates.
• Aigeo Inactive — Your plan lapsed or sync is not included. Existing deployed files stay live, but new deploys are blocked until you renew or upgrade to Pro+.

AigeoRadar intentionally keeps WordPress connected even when a plan expires — your discovery files remain served so you don’t lose AI visibility overnight. Renew to push fresh analysis updates.

When and how to redeploy

Redeploy whenever your AI Discovery package changes:

• After a new crawl and analysis (updated scores, new pages, revised business profile)
• After editing your Business Profile in AigeoRadar
• After generating new discovery assets from the Action Center or Content Intelligence workflow

Workflow: complete analysis in AigeoRadar → open WordPress → Deploy now. No need to reconnect unless you disconnect the plugin or change sites.

Using AigeoRadar day to day with WordPress

Monitor your GEO score

Use the AigeoRadar dashboard to track AI Readiness, Authority, and overall GEO scores. The Action Center lists issues with suggested fixes — many improve after discovery assets are live.

Run an LLM Visibility A/B test (Pro+)

From your analysis page, run the LLM Visibility A/B Test to compare how an AI would answer buyer questions before vs after your discovery package context. This is proof that deployment changes how AI describes your business — not just a percentage score.

Publish content to WordPress (optional, separate feature)

If you use AigeoRadar’s Content Factory to generate blog posts, FAQ pages, or landing pages, connect a Publishing destination with your WordPress username and an Application Password (Users → Profile → Application Passwords in WP 6+). That path publishes posts and pages — it does not replace the Connector plugin for llms.txt and entity files.

Troubleshooting common issues

Problem	Likely cause	Fix
Connect token fails	Token expired (15 min) or already used	Generate a new token in AigeoRadar and retry immediately
Deploy button disabled / “Inactive”	Free or Starter plan, or expired subscription	Upgrade to Pro+ or renew your plan
llms.txt returns 404	Permalinks not flushed, caching plugin, or security plugin blocking	Save Permalinks in WP (Settings → Permalinks → Save). Clear cache. Whitelist discovery URLs.
Garbled characters in llms.txt	Encoding mismatch	Redeploy from plugin v0.1.4+ (UTF-8 normalized). Confirm browser shows UTF-8.
Head tags missing on homepage	Head injection disabled or a page builder replaces wp_head	Enable head injection in plugin settings. Confirm your front page uses a theme that calls wp_head().
Files outdated after analysis	Deploy not run after new analysis	Click Deploy now again in WordPress

Security and permissions

• Connect tokens are single-use and short-lived — they are not stored long-term.
• After pairing, the plugin uses a signed Integration API secret (HMAC) for package downloads.
• Only WordPress users with manage_options (typically Administrators) can connect or deploy.
• Discovery file content is sanitized before storage and served with correct content types.

Quick reference checklist

1. Add and verify your site in AigeoRadar
2. Run a full GEO analysis
3. Upgrade to Pro+ if needed
4. Download AigeoRadar Connector from Publishing Integrations
5. Install and activate in WordPress
6. Generate connect token → paste API URL, Site UUID, token → Connect
7. Deploy now
8. Verify /llms.txt, JSON/XML files, and homepage head tags
9. Redeploy after each major analysis update

Need help?

Email hello@aigeoradar.com or visit the AigeoRadar Help Center. For plugin-specific guidance, open Settings → AigeoRadar → Help inside WordPress after installation.