Docs / AEO Ultimate for Claude

Jump to: WordPress sites · Shopify stores · Plans · Privacy and safety · Troubleshooting

WordPress sites

What Claude can do with it

The connector is part of the free TWT AEO Ultimate WordPress plugin (version 2.30 or later), with 36 tools. It gives Claude the same data you see in the plugin, so you can ask questions in plain language instead of clicking through screens:

• “Which AI engines cite us, and for which questions are competitors cited instead?” AI Visibility results, competitor citations and trends across every run.
• “Which important pages has no AI crawler visited this month?” AI crawler activity, uncrawled pages and AI referral traffic.
• “What’s stopping this page from being cited?” A full AEO report for any page, schema conflicts, the E-E-A-T scorecard and what AI crawlers actually see.
• “Give me the five quick wins for this week.” Ready-made analyses Claude can start from: AI Visibility, AI crawlers, a full health report, quick wins, competitor gaps and a deep dive on one page.

If you allow it, Claude can also fix what it finds: meta descriptions, Open Graph text, FAQ schema, image alt text, 404 redirects, duplicate schema, AI Ready settings, tracked questions, buyer personas, and the company and author profiles. It cannot edit page content, publish posts, or change titles, slugs, menus or media.

Step 1: Turn on the connector on your site

1. Update TWT AEO Ultimate to 2.30 or later.
2. In WordPress, go to TWT AEO → Settings → MCPs.
3. Under 1. Turn on the connector, click Turn on.
4. Under 2. Create a connection password, click Create connection password. It is shown only once, already filled into the setup under step 3, so keep the page open until you have copied what you need.

Only administrators can use the connector. The connection password is a standard WordPress Application Password: it works only for apps like Claude, never for logging in, and you can revoke it in your WordPress profile at any time. Application Passwords need your site to run on HTTPS, and some security plugins switch them off.

Step 2: Connect Claude

Claude on the web, desktop and mobile (recommended)

1. Create a free account at app.aeoultimate.app.
2. Add a client (your own business, or a client’s), then add your website under it with the platform WordPress.
3. Paste the site’s connection key (shown under step 3 on the MCPs tab) into the site’s Claude section and click Connect. The dashboard checks the key with your site before saving it, encrypted.
4. In Claude, open Settings → Connectors → Add custom connector and paste:
   https://mcp.aeoultimate.app/mcp
5. Sign in with your aeoultimate.app account and click Sign in and allow.

Connect once and every WordPress site in your account is available. Claude picks a site by its domain, for example “check AI citations for example.com”, and can compare sites side by side.

Claude Code

Run the command shown on the MCPs tab once in a terminal. It looks like this, with your site’s address and connection password filled in:

claude mcp add --transport http --scope user aeo-ultimate-example-com https://example.com/wp-json/aeo/v1/owner-mcp --header "Authorization: Basic …" --header "X-AEO-Authorization: Basic …"

The second header carries the same value for servers that strip the first (version 2.30.4 and later).

Claude Desktop and Cowork (direct)

In Claude Desktop, open Settings → Developer → Edit Config, paste the mcpServers block from the MCPs tab into claude_desktop_config.json (merge it with any you already have) and restart Claude. This route needs Node.js installed. Most people find the recommended route above simpler.

Step 3 (optional): Let Claude make changes

Changes are a separate switch on the MCPs tab, under What Claude can change, and they are off until you click Allow changes. With changes on:

• Every change is two steps. Claude first shows exactly what will change and asks you. It applies the change only after you say yes, and the approval expires after 15 minutes.
• One page at a time, never in bulk.
• Everything is logged and reversible. The last 50 changes are listed under Changes made by Claude with before and after values and who made them. Click Revert to put the exact previous value back (you are warned if the page was edited since), or ask Claude to undo it.

Running an AI Visibility check spends credits with your own AI providers and cannot be undone, so Claude always asks first.

Shopify stores

What Claude can do with it

The connector is part of the AEO Ultimate Shopify app on the Mid and Pro plans, with 43 tools. Claude reads the same data the app shows:

• “What should I fix first?” The app’s What to fix report, catalog issues (missing GTINs, thin descriptions, products not yet enriched), image alt-text gaps, and missing FAQs, share text and meta descriptions.
• “Which pages has Google not indexed, and which old URLs now 404?” Search Console queries and pages, the Not indexed report, and Lost links from Search Console or a list of URLs from your old platform, with suggested redirect targets.
• “Is our Merchant Center feed in sync?” Price, availability and disapproval mismatches, plus product ratings, the organization profile and blog posts.
• On Pro: AI Visibility results and the sites AI answers cite instead of you, AI crawler visits, the store trust report, schema and indexing audits, content uniqueness, and searching the documents in your RAG Engine for facts your product pages leave out.

If you allow it, Claude can also make the fixes: SEO titles and meta descriptions, meta tag templates, image alt text, product FAQs and share text, URL redirects, the organization profile, collections (Pro), blog post drafts, AI enrichment of a product, IndexNow submissions, and starting AI Visibility or Google index checks. Claude writes the copy itself, so it does not spend your AI key on FAQs, meta descriptions or blog drafts. It cannot see orders or customers, edit your theme, or publish a blog post; blog posts are saved as drafts for you to review.

Step 1: Turn on the connector in the app

1. In your Shopify admin, open AEO Ultimate (Mid or Pro plan) and go to Settings → Use with Claude.
2. Click Create connection key. The key starts with aeock_ and is shown only once, so copy it before you leave the page.
3. Click Turn on next to Connector.

The key works only for this store’s connector. You can replace or revoke it on the same page at any time, and revoking it stops Claude at once.

Step 2: Connect Claude

Claude on the web, desktop and mobile (recommended)

1. Create a free account at app.aeoultimate.app, or sign in to the one you already use for your WordPress sites.
2. Add your store under a client with the platform Shopify (its .myshopify.com address or its own domain).
3. Paste the aeock_ key into the store’s Claude section and click Connect. The dashboard checks the key with the app and refuses a key that belongs to a different store.
4. In Claude, open Settings → Connectors → Add custom connector (or find AEO Ultimate for Shopify in the connector directory), paste:
   https://mcp.aeoultimate.app/shopify/mcp
   and sign in with your aeoultimate.app account. This is a separate connector from the WordPress one, so Claude only ever sees store tools here.

Claude Code

Run this once in a terminal, with your key in place of YOUR-KEY:

claude mcp add --transport http --scope user aeo-ultimate-shopify https://store.aeoultimate.app/api/mcp --header "Authorization: Bearer YOUR-KEY"

Step 3 (optional): Let Claude make changes

On the same Settings page, click Allow changes. With changes on:

• Every change is two steps. Claude shows exactly what will change, item by item, and applies it only after you say yes. The approval expires after about 15 minutes.
• Small batches only. Most changes touch one product; redirects and meta tag templates go up to 25 at a time, each listed in the preview.
• Everything is logged and reversible. The last 50 changes are listed under Changes made by Claude with before and after values. Click Revert, or ask Claude to undo it. A collection or blog draft is only removed by undo while it is still empty or unpublished and unedited, so your later work is never lost.

Some actions reach outside your store and cannot be undone, so Claude always asks first: IndexNow submissions, AI Visibility runs and Google index checks, AI enrichment (one generation on your own AI key) and content uniqueness searches (on your own search key). All of them stay inside the daily limits set in the app.

Plans

The plans apply to the hosted connector at mcp.aeoultimate.app. Connecting Claude Code or Claude Desktop directly to a site or store, as above, is always free. The Shopify connector itself needs the AEO Ultimate app’s Mid or Pro plan. If a multi-site plan ends, Claude keeps working on your first connected WordPress site and on every Shopify store; the other WordPress sites pause until you renew.

Privacy and safety

• Claude only gets what its tools return: AEO data such as citations, crawler visits, indexing, catalog gaps and page scores. Never API keys, settings secrets, visitor IP addresses, the full text of AI answers, or on Shopify any order or customer data.
• The hosted connector passes requests and answers through without storing them. Connection keys are stored encrypted.
• Questions and answers written by other AI models, and product text from suppliers, are treated as data, never as instructions to Claude.

Read the full Claude connector privacy policy.

Troubleshooting

The server removes the Authorization header (WordPress)

The connector signs in with a header called Authorization. Some hosts, most often cPanel servers that run PHP as CGI, remove that header before WordPress sees it. Every key then looks like no key at all, so creating a new connection password does not help.

Easiest fix: update TWT AEO Ultimate to 2.30.4 or later. app.aeoultimate.app and the setup commands on the MCPs tab also send the password in a second header, X-AEO-Authorization, which these servers let through. If you set up Claude Code or Claude Desktop before 2.30.4, copy the command or config from the MCPs tab again. The steps below fix the server itself, which also helps other apps that use Application Passwords.

Check it: in WordPress, open Tools → Site Health. A warning about the Authorization header means this is the problem.

Fix the server, trying these in order:

1. Make sure your .htaccess file has this line inside the # BEGIN WordPress block, right after RewriteEngine On. Current WordPress versions add it themselves when you save Settings → Permalinks.
   RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
2. If the warning stays, the server ignores .htaccess for this. On cPanel, switch the site to PHP-FPM: in WHM open MultiPHP Manager and turn PHP-FPM on for the domain, or in cPanel ask your host to do it. PHP-FPM passes the header and is usually faster too.
3. On other hosts, ask support to “pass the HTTP Authorization header to PHP” (for example with CGIPassAuth On) so WordPress Application Passwords work.

Then paste the connection key into app.aeoultimate.app again.

Still stuck? Email david@tampawebtech.com.