LemonX Support

Compatibility

Need to know whether LemonX works with your WordPress setup? This page explains compatibility with WordPress versions, PHP, themes, page builders, SEO plugins, translation plugins, WooCommerce, caching tools, hosting environments, AI providers and MCP clients.

Check Compatibility Submit a Ticket

LemonX is designed to work with modern WordPress websites. For the best experience, keep WordPress, PHP, your theme and all LemonX products updated to the latest stable versions.

WordPress & PHP

Check the recommended WordPress, PHP, database and server requirements for LemonX products.

View Requirements

Themes & Builders

Learn how LemonX works with block themes, classic themes, Gutenberg, Elementor and other builders.

Check Theme Compatibility

SEO & Translation Plugins

Understand how LemonX works alongside Yoast, Rank Math, AIOSEO, WPML, Polylang, TranslatePress and other tools.

View Plugin Compatibility

Hosting & Security

Review compatibility with caching, security, firewall, CDN, REST API and server restrictions.

Troubleshoot Hosting Issues

LemonX compatibility overview

LemonX is built for modern WordPress websites and is designed to work with modular WordPress workflows. Because LemonX includes multiple products, compatibility may depend on which LemonX product you use and which features are enabled.

LemonX product areas

LemonX AEO

SEO, AEO, Schema, indexing, AI visibility, reports and content optimization.

LemonX Code

AI page generation, visual editing, templates, knowledge base, OCR, forms, modals and migration tools.

LemonX Verto

AI translation, multilingual SEO, URL translation, hreflang, translation memory and cache.

LemonX MCP

Secure AI agent connection, WordPress read/write tools, preview-before-apply workflow and MCP clients.

LemonX Pro

License management, cloud gateway, product entitlements, usage control and premium features.

LemonX Theme

Starter theme, canvas layout, template foundation and AI-generated page support.

Important note: You do not need to enable every LemonX product on every website. If a compatibility issue appears, you can often isolate it by disabling unused LemonX modules and testing only the product you need.

Recommended system requirements

For the best experience, we recommend using LemonX on a modern WordPress environment.

Recommended environment

WordPress: Latest stable version
PHP: Modern supported PHP version
Database: MySQL or MariaDB supported by WordPress
HTTPS: Enabled
REST API: Enabled
Permalinks: Enabled
Outbound HTTPS requests: Allowed
WP-Cron or real cron: Available
Memory limit: Sufficient for AI, translation and background tasks
File permissions: Standard WordPress write permissions for uploads and cache where needed

Why these requirements matter

LemonX products may need to:

Call AI provider APIs
Verify licenses
Generate and save content
Process translation queues
Submit indexing requests
Use WordPress REST API
Store settings and logs
Read media and page content
Run background jobs
Connect with MCP clients
Check product entitlements
Receive updates securely

If your server blocks these actions, some LemonX features may not work correctly.

WordPress compatibility

LemonX is designed for WordPress websites using modern WordPress standards.

Compatible WordPress setups

Single WordPress sitesBusiness websitesBlogs and content websitesWooCommerce storesAgency-managed client websitesMultilingual websitesB2B websitesLanding page sitesDeveloper and staging environments

WordPress features LemonX may rely on

REST APIAdmin AJAXCustom post typesMetadataTaxonomiesMedia libraryPermalinksCron jobsUser roles and capabilitiesPlugin update systemTheme template structureOptions APITransients and cachingApplication Passwords or secure authentication flows where needed

Recommended WordPress settings

Use clean permalinks.
Keep WordPress updated.
Do not disable REST API globally.
Do not block admin AJAX.
Use HTTPS.
Avoid editing plugin files directly.
Keep a backup before major updates.
Test major changes on staging when possible.

PHP and server compatibility

LemonX products may perform AI requests, indexing requests, translation queue processing, content generation and file-based operations. Your server should allow modern WordPress plugin behavior.

Recommended server capabilities

Modern PHP version
cURL enabled
JSON support enabled
mbstring enabled
OpenSSL enabled
ZIP support where needed
Fileinfo support where needed
Sufficient memory limit
Sufficient max execution time
Outbound HTTPS requests allowed
Write permissions for WordPress uploads
Background task support
WP-Cron or real cron available

Common server-related issues

License verification fails.
AI provider connection fails.
Translation queue does not process.
Indexing request does not send.
MCP connection cannot authenticate.
Plugin update does not appear.
Large OCR or knowledge base tasks fail.
REST API endpoints return blocked responses.
Security firewall blocks LemonX requests.

Recommended action: If you are not sure whether your server supports these features, contact your hosting provider and ask whether outbound HTTPS requests, WordPress REST API, WP-Cron and standard plugin update requests are allowed.

Theme compatibility

LemonX is designed to work with modern WordPress themes, including classic themes, block themes and lightweight starter themes.

Compatible theme types

Classic WordPress themesBlock themesCustom themesChild themesLightweight performance themesAgency-built themesWooCommerce-compatible themesLemonX Theme / LemonTThemes using standard WordPress template hierarchy

Best compatibility conditions

The theme follows WordPress coding standards.
The theme supports normal content rendering.
The theme does not block REST API.
The theme does not heavily override admin screens.
The theme does not remove required WordPress hooks.
The theme supports standard post, page and media behavior.
The theme does not strip generated markup unexpectedly.

LemonX Theme compatibility

LemonX Theme is designed as a clean foundation for LemonX Code and AI-generated pages. It is suitable when you want a lightweight layout base, canvas template and predictable page rendering.

Possible theme-related issues

Generated pages do not look as expected.
Theme CSS overrides LemonX-generated sections.
Canvas layouts do not display full width.
Header or footer conflicts with builder templates.
Archive templates behave differently from expected.
Theme disables parts of the block editor.
Theme adds excessive wrappers around content.

Recommended troubleshooting

Switch to a default WordPress theme temporarily.
Disable custom theme functions temporarily.
Check whether the issue appears only with one theme.
Test the page with LemonX Theme or a default theme.
Clear theme cache and optimization cache.
Review whether your theme overrides content filters.

Page builder compatibility

LemonX Code is designed to help create and manage WordPress pages, sections and templates. Compatibility with page builders depends on how the builder stores content and renders layouts.

Common builders: Gutenberg, Elementor, Divi, Bricks, Oxygen, Beaver Builder, WPBakery, Block themes, Custom builders.

Best supported workflow: LemonX generally works best when content is stored using standard WordPress pages, posts, blocks, shortcodes or clean HTML structures. Builder-specific layouts may require additional testing.

Gutenberg compatibility

Gutenberg and standard block-based workflows are generally the most predictable environment for AI-generated content, structured content, reusable sections and SEO-friendly pages.

Elementor compatibility

LemonX may work alongside Elementor depending on the feature used. Some AI-generated sections may need to be inserted as HTML, shortcode, block content or converted manually depending on the workflow.

Divi, Bricks, Oxygen and other builders

Advanced builders often store layout data in custom formats. LemonX may still help with content, structure, SEO, copywriting, Schema, translation and migration, but direct visual editing compatibility may depend on the builder.

Possible builder-related issues

Generated content does not appear inside builder layout.
Builder styling overrides LemonX output.
LemonX content appears outside expected containers.
Shortcodes are not rendered correctly.
Builder-specific templates do not accept standard content.
MCP edits a page but builder layout needs manual refresh.
Migration from builder content requires cleanup.

Recommended workflow

Test on staging first.
Use standard WordPress content when possible.
Keep original builder templates backed up.
Use LemonX for structure, copy, SEO and content generation.
Use your builder for final visual adjustments if needed.
Avoid mixing too many layout systems on the same page.

SEO plugin compatibility

LemonX AEO includes SEO and AEO features, but many websites already use SEO plugins. LemonX can be used alongside existing SEO tools depending on your setup and which features are enabled.

Common SEO plugins

Yoast SEORank MathAIOSEOSEOPressThe SEO FrameworkSquirrly SEOSlim SEO

Compatibility approach

LemonX can support SEO workflows such as content analysis, AI search optimization, Schema generation, internal linking, indexing, AI visibility and reporting. If another SEO plugin already controls metadata or Schema, you should avoid duplicate output.

Areas to check

Meta titleMeta descriptionCanonical URLOpen Graph tagsTwitter Card tagsSchema markupBreadcrumb SchemaXML sitemaprobots settingsIndexing statusRedirects404 monitoringInternal links

Best practices

Choose one primary plugin to output meta tags.
Avoid duplicate Schema from multiple plugins.
Disable overlapping features where necessary.
Check page source after enabling Schema.
Use testing tools to verify structured data.
Keep canonical URL output consistent.
Make sure only one sitemap is submitted if duplicates cause confusion.

Possible issues

Duplicate meta tags.
Duplicate Schema markup.
Conflicting canonical URLs.
Multiple XML sitemaps submitted.
Open Graph preview mismatch.
SEO score differs between tools.
Redirect rules conflict.
Robots settings conflict.

Recommended troubleshooting

Temporarily disable overlapping features.
Check generated HTML source.
Inspect Schema output.
Review sitemap settings.
Clear cache.
Test one page at a time.
Use one tool as the source of truth for each output type.

Translation plugin compatibility

LemonX Verto provides AI translation and multilingual SEO features. If your website already uses a multilingual plugin, compatibility depends on how language versions, URLs and translations are stored.

Common multilingual plugins

WPMLPolylangTranslatePressWeglotGTranslateMultilingualPressLoco TranslateWooCommerce Multilingual

What LemonX Verto may handle

Page translationPost translationProduct translationTaxonomy translationURL and slug translationSEO title translationMeta description translationSchema translationOpen Graph translationhreflangLanguage switcherTranslation queueTranslation memoryGlossaryTranslation cache

Important compatibility rule: Avoid letting multiple plugins control the same language routing, URL structure or hreflang output unless the integration is specifically configured for that workflow.

Possible issues

Duplicate hreflang tags.
Wrong language version appears.
Translated slugs conflict.
Language switcher duplicates.
SEO metadata not translated.
Translation cache mismatch.
Different plugins store translated content differently.
WooCommerce products do not sync correctly.
Search engines discover duplicate language URLs.

Recommended workflow

Decide which system controls language routing.
Decide which system controls hreflang.
Decide which system controls translated SEO fields.
Test one language first.
Test one content type first.
Check translated URLs.
Check source output.
Clear cache after translation.
Submit only the correct multilingual sitemap.

WooCommerce compatibility

LemonX can support WooCommerce websites with product content, product SEO, multilingual product pages, Schema, category content, product descriptions, FAQs and AI-generated ecommerce content.

Possible WooCommerce use cases

Generate product descriptions.
Generate product FAQ sections.
Translate products.
Translate categories.
Translate product slugs.
Optimize product Schema.
Create ecommerce landing pages.
Generate collection page copy.
Improve internal links.
Submit product pages for indexing.
Create multilingual SEO metadata.
Build content for product comparison pages.

Compatibility areas to check

Product post typeProduct categoriesProduct attributesProduct variationsProduct imagesProduct reviewsProduct SchemaCart and checkout pagesPayment gateway pagesWooCommerce multilingual setupCaching exclusionsDynamic fragments

Best practices

Do not heavily cache cart and checkout pages.
Test translation workflows on sample products first.
Back up product data before bulk changes.
Review generated product descriptions before publishing.
Check product Schema output.
Avoid duplicate SEO metadata from multiple tools.
Test variation products separately.
Check translated product URLs before indexing.

Possible WooCommerce issues

Product variations not translated as expected.
SEO metadata missing for products.
Duplicate Product Schema.
Checkout pages cached incorrectly.
Translated product URLs conflict.
Product category pages need manual review.
Images need translated ALT text.
Product feeds may need separate handling.

Caching plugin compatibility

LemonX is designed to work with caching tools, but AI generation, translation queues, license checks, dynamic admin screens and MCP connections may require proper cache exclusions.

Common caching tools

WP RocketLiteSpeed CacheW3 Total CacheWP Super CacheAutoptimizeFlyingPressBreezeSG OptimizerCloudflare APOServer-level cacheObject cache

Areas that may need exclusion

LemonX admin pages
LemonX REST API endpoints
License verification requests
MCP authentication endpoints
Translation queue actions
AI provider callback or request endpoints
Preview-before-apply pages
Account connection flows
Dynamic dashboard widgets

Possible caching issues

License status does not refresh.
Translation queue appears stuck.
MCP tool response is outdated.
Admin dashboard shows old data.
Generated pages show old content.
Language switcher displays wrong language.
REST API responses are cached incorrectly.
Updated Schema does not appear immediately.

Recommended troubleshooting

Clear all caches.
Clear CDN cache.
Disable minification temporarily.
Exclude LemonX admin and API routes from cache.
Disable object cache temporarily for testing.
Check whether server cache is active.
Test in an incognito browser.
Turn off page cache for logged-in users.

Security plugin compatibility

Security plugins and firewalls can protect your site, but they may also block license checks, REST API requests, AI provider calls, indexing requests or MCP connections if configured too aggressively.

Common security tools

WordfenceiThemes SecuritySolid SecuritySucuriAll-In-One SecurityCloudflare WAFMalCarePatchstackHosting firewallServer-level WAFCustom .htaccess rules

LemonX actions that may be blocked

License verification
Product updates
REST API requests
MCP authentication
AI provider requests
Indexing submissions
Translation queue processing
Webhook-like requests
Cloud gateway requests
Admin AJAX requests

Possible security-related issues

License activation fails.
MCP cannot connect.
REST API returns 401, 403 or 404.
AI provider connection fails.
Indexing submission fails.
Dashboard loads partially.
Admin actions are blocked.
Requests are flagged as suspicious.
Firewall blocks outbound HTTPS.

Recommended troubleshooting

Check firewall logs.
Whitelist LemonX routes if needed.
Allow outbound HTTPS requests.
Make sure REST API is not globally disabled.
Temporarily disable aggressive rules for testing.
Check whether application passwords are blocked.
Ask hosting support if a server firewall is blocking requests.
Do not disable security permanently without understanding the cause.

CDN and Cloudflare compatibility

LemonX can work with CDN services, but cache and firewall rules should be configured carefully.

Common CDN services

CloudflareBunny CDNFastlyAkamaiSucuri CDNHosting CDNLiteSpeed QUIC.cloud

Recommended CDN configuration

Do not cache WordPress admin pages.
Do not cache dynamic REST API responses used by LemonX.
Do not block outbound license or API requests.
Allow authenticated users to bypass full-page cache.
Clear cache after major content generation or translation.
Check firewall rules if MCP connection fails.
Review bot protection settings if AI crawlers or indexing tools are affected.

Possible CDN issues

Old translated content appears.
Updated content is not visible.
LemonX dashboard shows outdated status.
MCP connection is blocked.
AI crawler settings do not appear immediately.
Indexing verification fails.
Language-specific URLs return cached wrong language.

AI provider compatibility

LemonX products may connect to AI providers for content generation, translation, analysis, OCR, knowledge base workflows, MCP-related workflows and automation.

Common AI providers: OpenAI, Anthropic Claude, Google Gemini, DeepSeek, Ollama, OpenAI-compatible providers, Custom AI gateways, Self-hosted or local models where supported.

Compatibility requirements

Valid API key
Correct API base URL
Supported model name
Outbound HTTPS requests allowed
Sufficient provider quota
Correct provider permissions
Stable network connection
Compatible request and response format
Reasonable timeout settings

Possible AI provider issues

Invalid API key.
Model not found.
API base URL incorrect.
Provider quota exceeded.
Rate limit reached.
Request timeout.
Server cannot reach provider.
Response format unsupported.
Local model unavailable.
Provider blocks your region or server IP.

Recommended troubleshooting

Test the API key directly if possible.
Check provider quota and billing.
Confirm model name.
Confirm API base URL.
Try another provider.
Try a smaller request.
Increase timeout if supported.
Ask your host whether outbound HTTPS is allowed.
Check LemonX provider logs if available.

MCP client compatibility

LemonX MCP connects WordPress with MCP-compatible AI clients. Compatibility depends on the MCP client, authentication setup and your WordPress server environment.

Common MCP clients: Claude Desktop, Codex, Cursor, Other MCP-compatible clients.

Requirements for MCP workflows

WordPress site available over HTTPS
Valid authentication
MCP endpoint reachable
Correct site URL
Correct credentials or token
REST API not blocked
Firewall allows required requests
User has proper WordPress permissions
LemonX MCP module enabled
Preview-before-apply workflow configured where needed

Possible MCP issues

Client cannot connect.
Authentication fails.
Site identity mismatch.
Tools do not appear.
Read tools work but write tools fail.
Preview works but apply fails.
Firewall blocks MCP requests.
Wrong site URL is configured.
User does not have permission.
REST API is disabled.

Recommended troubleshooting

Confirm the WordPress site URL.
Confirm HTTPS is working.
Check authentication credentials.
Check user role and permissions.
Confirm LemonX MCP is active.
Check security plugin logs.
Test REST API availability.
Regenerate credentials if needed.
Restart the MCP client.
Review MCP logs inside LemonX.

Browser compatibility

LemonX admin screens are designed for modern browsers.

Recommended browsers

ChromeSafariFirefoxEdge

Browser features that should be enabled

JavaScript
Cookies
Local storage
Modern CSS support
Secure HTTPS connection
Popups where required for account connection
No aggressive script blocking on LemonX admin screens

Possible browser issues

Dashboard does not load.
Buttons do not respond.
License connection popup fails.
Account login does not stay active.
Visual editor behaves unexpectedly.
File upload does not start.
MCP setup instructions do not display correctly.

Recommended troubleshooting

Update your browser.
Try another browser.
Disable browser extensions temporarily.
Use an incognito/private window.
Clear browser cache.
Allow cookies.
Disable aggressive privacy blockers for LemonX admin pages.

WordPress multisite compatibility

LemonX may be used in multisite environments depending on your product, license and configuration. Multisite behavior should be tested carefully before production use.

Things to check

Network activation vs site activation
Per-site license status
Per-site settings
Shared users and roles
Different language sites
Different domains or subdomains
Plugin permissions
Media library behavior
REST API behavior
Cron and background tasks
Client site ownership
Agency license limits

Recommended workflow

Test on a staging multisite network first.
Activate LemonX only where needed.
Confirm license behavior per site.
Check whether each subsite needs separate settings.
Avoid bulk changes until one subsite works correctly.
Review permissions for site admins and network admins.

When to contact support: Contact support if you need to confirm whether your plan supports multisite, subsite licensing, agency workflows or network-level configuration.

Hosting compatibility

Most modern WordPress hosting environments should support LemonX, but some hosts may restrict outbound requests, cron jobs, REST API routes, file operations or long-running background tasks.

Compatible hosting types

Shared hostingManaged WordPress hostingVPSCloud hostingDedicated serversAgency hostingEnterprise hostingLocal development environmentsStaging environments

Hosting features to check

Outbound HTTPS requestsREST API accessWP-Cron or real cronMemory limitExecution timeFile permissionsSSL certificateDatabase performanceServer firewallObject cacheCDN rulesSecurity policyBackup availability

Possible hosting-related issues

AI requests timeout.
Translation queue stops.
OCR processing fails.
License verification blocked.
Plugin update unavailable.
MCP cannot connect.
Large pages fail to save.
Background jobs do not run.
REST API returns server errors.

Recommended action: If your hosting provider has strict security rules, ask them to confirm that WordPress plugins can make outbound HTTPS requests and use REST API endpoints normally.

Known compatibility conflict patterns

Compatibility issues usually come from overlapping features, blocked requests or aggressive optimization.

Duplicate SEO output

Two plugins output meta tags, Schema, canonical URLs or Open Graph tags at the same time.

Blocked REST API

A security plugin, firewall or custom code blocks REST API routes required by LemonX.

Cached dynamic responses

Caching tools cache admin, API or language-specific responses that should remain dynamic.

Builder-specific storage

A page builder stores content in a custom format that does not accept standard WordPress content directly.

Translation routing conflict

Multiple plugins attempt to control language URLs, hreflang or translated content storage.

Server request blocking

Hosting firewall blocks outbound calls to license, AI, translation or indexing services.

Permission mismatch

The WordPress user does not have the capability required for the LemonX action.

Wrong environment URL

A staging URL, temporary URL, www/non-www mismatch or HTTP/HTTPS change causes license or MCP confusion.

Compatibility testing checklist

Before using LemonX on a production site, use this checklist.

Basic setup

WordPress is updated.
PHP is modern and supported.
HTTPS is enabled.
Permalinks are enabled.
REST API works.
Admin AJAX works.
WP-Cron works.
Outbound HTTPS requests are allowed.
LemonX products are updated.

Product testing

AEO dashboard loads.
Code generation works.
Verto translation queue runs.
MCP connects successfully.
Pro license status verifies.
Theme templates display correctly.
AI provider connection works.
Indexing integration works where configured.

Plugin testing

SEO plugin output checked.
Translation plugin output checked.
Cache cleared after changes.
Security firewall logs reviewed.
WooCommerce product pages tested.
Page builder pages tested.
CDN cache tested.
No duplicate Schema appears.

Final production checks

Back up the website.
Test on staging if possible.
Enable one module at a time.
Clear all caches.
Check frontend pages.
Check source code output.
Check admin performance.
Confirm no fatal errors.
Monitor logs after launch.

How to report a compatibility issue

If you believe LemonX conflicts with your theme, plugin, hosting provider or AI provider, send us enough information to reproduce and diagnose the issue.

What to include

Website URL
WordPress version
PHP version
LemonX product and version
Theme name and version
List of active plugins
Hosting provider
Caching plugin or CDN
Security plugin or firewall
AI provider, if relevant
SEO plugin, if relevant
Translation plugin, if relevant
Page builder, if relevant
Exact error message
Screenshots or screen recording
Steps to reproduce the issue
Whether the issue happens on staging
Whether disabling another plugin fixes the issue
Whether switching theme fixes the issue

Submit a Compatibility Ticket

Compatibility FAQ

Does LemonX work with any WordPress theme?

LemonX is designed to work with modern WordPress themes. Themes that follow WordPress standards generally work best. Heavily customized themes may require testing.

Does LemonX work with Elementor?

LemonX can work alongside Elementor in many workflows, especially for content, SEO, AEO and generation support. Direct layout editing may depend on how the page is built.

Does LemonX work with Gutenberg?

Yes. Gutenberg and standard WordPress block workflows are among the most predictable environments for LemonX-generated content.

Can I use LemonX AEO with Yoast or Rank Math?

Yes, but avoid duplicate output. Decide which tool controls meta tags, Schema, sitemaps and Open Graph data.

Can I use LemonX Verto with WPML or Polylang?

It depends on your configuration. Avoid letting multiple tools control language routing, hreflang and translated URLs at the same time unless configured intentionally.

Does LemonX work with WooCommerce?

LemonX can support WooCommerce content, product SEO, product translation, product pages, Schema and ecommerce landing pages. Test product variations and checkout-related pages carefully.

Will caching plugins break LemonX?

Caching plugins usually work, but LemonX admin pages, API routes, translation queues, license checks and MCP endpoints may need cache exclusions.

Why does my security plugin block LemonX?

Security plugins may block REST API requests, outbound HTTPS calls, MCP authentication or license verification if rules are too strict. Check firewall logs and whitelist safe LemonX actions where needed.

Does LemonX work on multisite?

Some LemonX workflows may work on multisite, but licensing and per-site settings should be confirmed based on your plan and tested on staging.

Does LemonX support local development?

You can test many features locally, but cloud features, license verification, AI provider calls, indexing and MCP connections may require a reachable HTTPS environment.

My AI provider does not connect. Is that a compatibility issue?

It may be a provider configuration issue, API key issue, quota issue, server firewall issue or incorrect API base URL. Check provider settings first.

What is the best way to find a conflict?

Disable non-essential plugins, switch to a default theme, clear cache, test one LemonX module at a time, and re-enable tools one by one until the issue returns.

Related Support Pages

Not sure if LemonX is compatible with your setup?

Send us your WordPress version, PHP version, theme, active plugins, hosting provider and the LemonX product you want to use. We will help you review the compatibility risk and recommend the safest setup path.

Submit a Compatibility Ticket View System Requirements

For faster support, include your theme name, active plugins, hosting provider, PHP version, WordPress version, LemonX product version and screenshots of any errors.