Requirements
Server, WordPress and PHP requirements for Aimogen Pro, the PHP extensions it needs, multisite behaviour, and the provider accounts required per feature.
Hard requirements#
The plugin checks these on the activation hook. If a check fails, activation is aborted with an explanatory message rather than leaving a half-installed site.
| Requirement | Minimum | Notes |
|---|---|---|
| WordPress | 5.0 | Tested up to 7.0 |
| PHP | 7.3 | 8.1 or newer is recommended |
| cURL PHP extension | required | Activation aborts if curl_init() is unavailable |
| Capability to activate | activate_plugins | Standard WordPress requirement |
Strongly recommended#
Not enforced, but a production install without these will be frustrating.
| Item | Recommended | Why |
|---|---|---|
PHP max_execution_time | 180s or more | A long article makes several sequential API calls; agents make many |
PHP memory_limit | 256M or more | Scraping, image sideloading and large batches are memory-hungry |
mbstring | enabled | Correct multibyte handling. The plugin ships a pure-PHP fallback, but it is slower |
dom and libxml | enabled | HTML parsing for scraping, readability extraction and Gutenberg block editing |
zip | enabled | Language pack installation and some import/export paths |
| Outbound HTTPS | unrestricted | Provider APIs, scraping targets and image sources are all remote |
| A real cron trigger | system cron | See Scheduling and the posting cron |
The plugin uses a default request timeout of 160 seconds for large calls
(AIMOGEN_DEFAULT_BIG_TIMEOUT). If PHP terminates the request before that, you get truncated content
rather than a clean error.
What you also need#
At least one AI provider API key. Aimogen Pro ships with no credentials and does not proxy your requests unless you deliberately choose AiomaticAPI. An OpenAI key is not required — any one supported provider is enough to generate text. See AI providers.
A licence. Automatic updates and the feature screens require an activated purchase code. See Activation and licensing.
Optional service accounts, depending on which features you enable:
| Feature | Needs |
|---|---|
| AI images | OpenAI, Stability.AI, Google, Ideogram, Replicate, GoAPI (Midjourney) or a Cloudflare Worker |
| Embeddings and RAG | An embedding provider, plus OpenAI Vector Stores, Pinecone, Qdrant or Chroma |
| Text-to-speech | OpenAI, ElevenLabs, Google Text-to-Speech or Azure Speech Services |
| Talking avatars | D-ID or Azure Speech Services |
| Internet access and SERP data | Google Custom Search, SerpAPI, ValueSERP, SpaceSERP, Serper.dev or Tavily — or none, using the built-in Bing and DuckDuckGo scrapers |
| Amazon product data | An Amazon Associates account. PA-API keys are optional; without them the plugin scrapes |
| Translation | Optional DeepL, Microsoft Translator or Google Translate keys |
Multisite#
Aimogen Pro runs on multisite. Behaviour that differs from single-site:
- Licensing is network-wide. The registration record is read from and written to the main site, so one activation covers the network.
- The updater only runs on the main site. Subsites do not perform their own update checks.
- Settings are per-site. Each site keeps its own
aiomatic_Main_Settings,aiomatic_Chatbot_Settings,aiomatic_Spinner_Settingsand so on. On a network install, defaults are seeded for a site the first time its settings option is missing. - Settings forms post to
../options.phpwhen opened from the network admin. - Database tables are per-site and use the site prefix. See Data model.
Plan API spend accordingly: every site draws on the same provider quota unless you give each site its own keys.
Hosting notes#
Shared hosting with aggressive process limits will cut off long generations mid-way. Prefer shorter target lengths, enable Reliability Mode, and use the asynchronous posting method described in Scheduling.
Managed WordPress hosts sometimes restrict outbound HTTP to an allowlist. Provider API domains must be reachable — the list is on each provider page.
Web application firewalls frequently block the plugin REST routes, in particular the MCP server
endpoints under /wp-json/aiomatic-mcp/v1/*. See
Plugin and server conflicts.
Page caching and object caching can serve stale chatbot responses. Exclude admin-ajax.php from
caching for the chatbot actions. See Performance.
Next: Installation.
Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.