Fully Recommended
- Modern WordPress installation
- PHP 8.3+
- MySQL 8.0+ or MariaDB 10.6+
- HTTPS enabled
- Strong hosting performance
- Working WP-Cron or real server cron
- Updated browser
- Clean plugin stack
System Requirements
Check your environment before installing LemonX.
LemonX is built for modern WordPress websites that use AI, SEO automation, multilingual translation, MCP agent workflows and connected growth tools.
Before installing LemonX AEO, Code, Verto, MCP, Pro, Theme or the full LemonX Suite, review these requirements to make sure your website, server, browser, API providers and WordPress configuration are ready.
For WordPress site owners, developers, agencies, hosting teams and technical SEO teams.
Quick Summary
Recommended environment for LemonX.
| Component | Recommended | Minimum / Notes |
|---|---|---|
| WordPress | Latest stable WordPress version Best: WordPress 6.5+ or newer |
WordPress 6.4+ |
| PHP | PHP 8.3+ Best: Not recommended: PHP 7.x or unsupported PHP versions |
PHP 8.2+ |
| Database | MySQL 8.0+ or MariaDB 10.6+ | Follow current WordPress-supported database requirements |
| HTTPS | Required for production websites | Strongly required for MCP, API keys, license activation and AI provider connections |
| Server Memory | 256 MB+ PHP memory limit Best: 512 MB+ for large workflows |
128 MB for basic usage |
| Upload Limit | 64 MB+ | For OCR, knowledge base and migration: 128 MB+ recommended |
| Max Execution Time | 120 seconds+ | For translation, OCR and migration: 300 seconds recommended where possible |
| Browser | Latest Chrome, Safari, Firefox, Edge | Not recommended: outdated browsers for admin workflows |
| AI Provider | Required for AI-powered features | Supports OpenAI-compatible providers where configured |
| Cron / Background Tasks | Required for queues, translation jobs, indexing, reports and long-running workflows | — |
| HTTPS + SSL | Required for secure API communication, license verification, MCP authentication and external integrations | — |
Compatibility
Know whether your environment is ready.
Usable With Caution
- Shared hosting
- PHP 8.2
- Limited memory
- Many active plugins
- Heavy page builders
- Large translation queues
- Complex multilingual setup
- Older custom theme
Not Recommended
- PHP 7.x
- No HTTPS
- Disabled cron
- Very low memory limit
- Outdated WordPress version
- Unsupported database version
- Abandoned theme
- Unmaintained plugins
- Production site without backup
WordPress Requirements
LemonX is designed for modern WordPress websites.
LemonX works best on updated WordPress installations with a stable theme, maintained plugins, HTTPS, working background tasks and a healthy server environment.
Recommended
- Latest stable WordPress version
- WordPress 6.5 or newer
- Block editor support enabled
- REST API available
- Permalinks enabled
- HTTPS enabled
- Admin access available
- Working plugin installation and update system
Minimum
- WordPress 6.4+
- Administrator access
- Plugin upload or direct installation access
- REST API not blocked
- Standard WordPress database structure
Not Recommended
- Outdated WordPress versions
- Heavily modified WordPress core
- Disabled REST API
- Broken permalink structure
- Unmaintained themes
- Unmaintained plugins
- Sites with unresolved malware or security issues
Notes
- Some LemonX features may still work on older WordPress environments, but performance, security and compatibility cannot be guaranteed. For production websites, always keep WordPress updated.
PHP Requirements
Use a supported PHP version for better security and performance.
Recommended
- PHP 8.3 or newer
Minimum
- PHP 8.2
Not Recommended
- PHP 8.1 or older
- PHP 7.x
- Unsupported PHP branches
- Hosting environments that cannot upgrade PHP
Required PHP Settings
- memory_limit: 256M recommended
- max_execution_time: 120 or higher recommended
- max_input_vars: 3000 or higher recommended
- upload_max_filesize: 64M or higher recommended
- post_max_size: 64M or higher recommended
- allow_url_fopen: enabled when required by provider integrations
- cURL: enabled
- JSON: enabled
- mbstring: enabled
- OpenSSL: enabled
- ZIP: recommended
- GD or Imagick: recommended for media-related workflows
Why PHP Version Matters
- LemonX uses AI provider connections, background tasks, API calls, translation queues, indexing workflows, content processing and optional OCR or knowledge base features. These workflows require a stable and modern PHP environment.
- Older PHP versions may create security risks, compatibility problems, slower performance or unexpected errors with modern WordPress plugins.
Database Requirements
Use a modern MySQL or MariaDB database.
Recommended
- MySQL 8.0+
- MariaDB 10.6+
Minimum
- Use a database version supported by your current WordPress installation.
Required Capabilities
- Standard WordPress tables
- Ability to create plugin tables where needed
- UTF-8 support
- utf8mb4 support recommended
- Stable database connection
- Sufficient storage for logs, records, reports, translation data and template records
Database Usage by LemonX
- Product settings
- License status
- Module configuration
- AEO reports
- Schema settings
- Prompt records
- Template records
- Translation records
- Translation memory
- Glossary rules
- MCP logs
- AI provider configuration
- Background task status
- Usage-related records
Notes
- For large multilingual websites, ecommerce sites, high-volume blogs or agency client sites, database performance matters. Slow database queries can affect dashboard workflows, translation queues, reporting and search-related analysis.
HTTPS & Security
HTTPS is required for production use.
LemonX connects WordPress with AI providers, cloud gateway services, license systems, search APIs, translation providers and MCP clients. Secure communication is essential.
Required
- HTTPS enabled
- Valid SSL certificate
- Secure WordPress admin login
- Strong admin password
- Updated WordPress core
- Updated active plugins
- Updated active theme
- Administrator access for setup
- Secure API key storage
- No public exposure of private keys
Strongly Recommended
- Two-factor authentication for administrators
- Limited administrator accounts
- Separate accounts for team members
- Staging environment for testing
- Regular backups
- Security plugin or hosting firewall
- Web application firewall
- Activity logging
- File editing disabled in WordPress admin
- Regular malware scanning
Not Recommended
- Running LemonX on HTTP production sites
- Sharing admin accounts
- Using outdated plugins
- Using nulled themes or plugins
- Disabling security updates
- Pasting API keys into public pages
- Giving MCP write access without review
Hosting Requirements
Choose hosting that can handle AI-powered WordPress workflows.
Recommended Hosting Type
- Managed WordPress hosting
- Cloud VPS
- High-quality shared hosting
- Agency hosting environment
- Dedicated server for high-volume workflows
Minimum Hosting Requirements
- WordPress-compatible hosting
- PHP 8.2+
- MySQL or MariaDB
- HTTPS
- cURL support
- Working WP-Cron or server cron
- Sufficient memory
- Ability to install plugins
- Outbound API connections allowed
Recommended Server Resources
- PHP memory limit: 256 MB+
- For large sites: 512 MB+
- CPU: Modern shared or dedicated CPU resources
- Storage: SSD recommended
- Disk space: Enough for media, logs, translations, templates and backups
- Object cache: Recommended for larger sites
- Page cache: Recommended for frontend performance
- Real cron: Recommended for large queues
Outbound Connection Requirements
- Your server should allow outbound HTTPS requests to: AI providers, translation providers, LemonX license service, LemonX cloud gateway, Google APIs, Bing APIs, Yandex APIs, IndexNow endpoints, MCP clients where applicable, webhook destinations where configured.
Not Recommended Hosting Environments
- Hosts that block outbound API calls
- Hosts with very low PHP memory
- Hosts with disabled cron
- Hosts that cannot upgrade PHP
- Hosts with strict timeout limits
- Hosts that block REST API
- Hosts that block loopback requests
- Hosts with unreliable SSL
- Hosts with overloaded shared resources
File Handling
Some LemonX workflows process files, documents and media.
Recommended Upload Settings
- upload_max_filesize: 64 MB+
- post_max_size: 64 MB+
- For OCR and knowledge base workflows: 128 MB+ recommended
- For large document uploads: 256 MB+ may be useful
Supported File Types May Include
- DOCX
- TXT
- Markdown
- CSV
- Images
- Screenshots
- Export files
- Structured content files
- Template files
Product Areas That May Use Uploads
- LemonX Code knowledge base
- OCR workflows
- Website migration workflows
- Template import
- Prompt library import
- Agency workflows
- Translation planning
- Product data import
- Documentation-based page generation
Notes
- Large files require more memory, longer processing time and stronger hosting. For production websites, test large file workflows on staging before using them heavily.
Background Tasks
Queues and scheduled jobs need reliable cron behavior.
LemonX may use background processing for translation queues, AI jobs, indexing, reports, crawls, content analysis, MCP logs and scheduled workflows.
Required
- WP-Cron enabled or real server cron configured
- Loopback requests working
- No firewall blocking internal WordPress requests
- Enough execution time for background tasks
- No aggressive server process killing
Recommended
- Real server cron every 5–15 minutes
- Separate queue processing for large sites
- Monitoring for failed jobs
- Log retention policy
- Staging test for large queues
Product Areas That Use Background Tasks
- Verto translation queue
- AEO content analysis
- Indexing submission
- Report generation
- Content decay checks
- Rank tracking
- AI visibility checks
- MCP logs
- Knowledge base processing
- OCR tasks
- Template imports
Common Problems
- Translation jobs stuck
- Reports not generating
- Indexing queue not processing
- Scheduled checks not running
- Background jobs timing out
- AI tasks failing without visible error
Recommended Fix
- If background jobs are unreliable, ask your host to configure a real server cron and confirm that loopback requests are not blocked.
Browser Requirements
Use a modern browser for the LemonX dashboard.
Recommended Browsers
- Latest Google Chrome
- Latest Safari
- Latest Firefox
- Latest Microsoft Edge
Admin Dashboard Recommendation
- Desktop browser recommended
- Modern laptop or desktop recommended
- Stable internet connection
- JavaScript enabled
- Cookies enabled for login and dashboard sessions
- Pop-up blockers reviewed for OAuth or provider login flows
Mobile Support
- Frontend pages remain responsive based on your theme and layout.
- WordPress admin workflows may work on tablets or phones, but advanced LemonX dashboard workflows are best managed on desktop.
Not Recommended
- Outdated browsers
- Unsupported mobile browsers
- Browsers blocking all scripts
- Private browsing modes that block cookies
- Corporate browsers that block API requests
- Browser extensions that interfere with WordPress admin
AI Provider Requirements
AI-powered features require an AI provider or LemonX cloud access.
Required for AI Features
- Valid AI provider access
- API key or account connection
- Sufficient provider credits or billing
- Available model
- Outbound HTTPS requests from server
- Correct endpoint configuration
- Working provider authentication
Supported Provider Types
- OpenAI-compatible providers
- Cloud AI providers
- Local providers where configured
- Translation AI providers
- Custom AI endpoints where supported
Common Provider Requirements
- API key
- Model name
- Base URL or endpoint
- Organization or project ID where required
- Rate limit awareness
- Billing status
- Token limit awareness
- Privacy review
- Fallback provider where needed
Product Areas That Need AI Providers
- LemonX AEO AI Writer
- Content Analyzer
- Query Lab workflows
- AI citation analysis
- LemonX Code page generation
- Knowledge base and RAG
- OCR-assisted content workflows
- LemonX Verto AI translation
- Glossary-assisted translation
- MCP-assisted AI workflows
- Prompt Library usage
- Content refresh workflows
Recommended Setup
- Use separate API keys for production and testing.
- Avoid sharing private API keys between unrelated sites.
- Set provider usage limits when available.
- Monitor usage and cost.
- Use fallback providers for critical workflows.
- Review provider privacy policies before sending sensitive content.
Search Integrations
AEO and indexing workflows may require search platform access.
Google Search Console
- Verified property
- Correct site URL
- Google account access
- API authorization where needed
- Permission to view search performance data
Google Indexing API
- Google Cloud project
- API enabled
- Service account where applicable
- Correct permissions
- Supported URL types
- Secure credential handling
Bing Webmaster
- Bing Webmaster account
- Verified site
- API key or authorized access
- Correct site URL
Yandex Webmaster
- Yandex Webmaster account
- Verified site
- API access where configured
- Correct site URL
IndexNow
- IndexNow key
- Key file or configured key location
- Supported search engines
- Correct URL submission settings
Notes
- Indexing submission does not guarantee ranking. Search engines decide whether and when to crawl, index and rank pages.
Multilingual Requirements
Large translation workflows need stable server resources.
Required for LemonX Verto
- WordPress site with stable permalink structure
- HTTPS
- Target languages configured
- Translation provider access
- Working background queue
- Sufficient memory
- Sufficient execution time
- Database storage
- SEO metadata access
- Ability to generate or manage language URLs
Recommended for Multilingual SEO
- Clear source language
- Language switcher plan
- Translated URL strategy
- hreflang validation
- Multilingual sitemap support
- Glossary prepared
- Translation memory enabled
- Review workflow defined
- Cache configured
- Staging environment for major translation launches
Recommended for Large Sites
- Server cron
- 512 MB+ memory
- Strong database performance
- Queue monitoring
- Translation batch planning
- Language launch checklist
- SEO validation after translation
- Search Console monitoring
Not Recommended
- Launching many languages without QA
- Translating important product pages without glossary
- Changing URL structure without redirects
- Publishing machine translation without review
- Ignoring hreflang validation
- Running large translation jobs on very weak hosting
MCP Requirements