AISA + WordPress 7 AI
WordPress 7 brings AI into core, with native connectors. AISA detects and uses them as a provider: zero keys to paste into the plugin.
How it works
If your WordPress 7 has an AI connector configured (Settings → AI), in AISA you simply pick “WordPress connector” as the provider: keys stay in core, shared with other plugins, and every AISA feature — One-Click, Bulk, editor panel, GEO, FAQ — runs on that engine.
Zero keys in the plugin
WordPress manages the credentials: you paste nothing into AISA. One single place for the whole site's keys.
Detection and diagnostics
AISA sees whether the AI framework is there, which provider is configured and what's missing — never a dead end.
Every feature, same engine
One-Click, background Bulk, editor panel, GEO/llms.txt, Q&Ai FAQ: every AISA feature can run on the WP connector.
The first mix is already here
Separate image provider: e.g. Vision on the WP connector and texts with your own key — or the other way round.
| Aspect | WordPress 7 connector | Direct keys in AISA (BYOK) |
|---|---|---|
| Where the keys live | In WordPress core | In AISA (Settings → API) |
| Setup in AISA | None: detect and use | Paste the provider key |
| Model choice | Managed by WordPress | Yours, per provider (separate Vision model too) |
| Available providers | The ones configured in WP | 7: Claude · GPT · Gemini · DeepSeek · Grok · Mistral · Sonar |
| Vision (image alt-text) | If the connector has a vision model | ✓ with Claude / GPT / Gemini |
| Keys shared with other plugins | ✓ the whole site reuses them | AISA only |
| Requirements | WordPress 7.0+ | Any supported WordPress |
| Best for | Those who already set up AI in WP | Those who want fine control of providers and models |
WP 7 connector or direct keys in AISA?
It's not a contest: the two paths coexist. Here's when each one makes sense.
On the roadmap: AI routing
The next step is per-task orchestration: DeepSeek for SEO texts, GPT for Vision, Sonar for GEO checks — mixing WordPress 7 connectors and your own keys, each where it performs best. WordPress 7 can keep multiple connectors configured at once, and AISA already sees them individually: the routing table is on the roadmap.
Why it matters
One single place for keys
WordPress manages them: no keys scattered across ten different plugins.
Start in a minute
Already set up AI in WP 7? AISA works right away, nothing to touch.
No double subscriptions
The same key serves every plugin on the site: you pay real usage only.
Coherent multilingual
The language always follows the page's real text — through the connector too.
AI routing ahead
Each task to the right provider, mixing WP connectors and your own keys.
Smart fallback
Connector not configured? AISA flags it and you switch to direct keys without losing anything.
In short
WordPress 7.0+
Zero keys in the plugin
One-Click & Bulk included
Vision via the connector
AI routing on the roadmap
Transparency note
The AI connector is a new, still-evolving part of WordPress 7: AISA supports it as a provider and follows its updates. "AI routing" (per-task assignment) is on the roadmap, not in the plugin yet. On WordPress before 7.0 you use direct keys: only where the credentials live changes.
Learn more: aiseoassistant.io
AI SEO & GEO Assistant is a project by Ingenium Project.
Try it free on 25% of your content
No credit card. WordPress 7 connector or your own API keys: you choose where the keys live.