Identify the affected product
- LemonX AEO
- LemonX Code
- LemonX Verto
- LemonX MCP
- LemonX Pro
- LemonX Theme
- Account or Billing
- Full LemonX Suite
Use this troubleshooting guide to diagnose common issues across LemonX AEO, Code, Verto, MCP, Pro and Theme. Start with the quick checks, then follow the product-specific steps for installation, license activation, AI provider setup, indexing, translation, MCP connection, compatibility and performance problems.
Many LemonX issues are caused by environment settings, outdated versions, cache, license status, API provider configuration or plugin conflicts. Before opening a ticket, complete these basic checks.
Go to: WordPress Dashboard > Plugins. Make sure the related LemonX plugin is installed and activated.
If the product is missing, install it first.
Installation HelpMake sure you are using the latest available version of the LemonX product.
If you are using Pro features, make sure your license is active and connected to the correct site.
If license verification, cloud gateway, updates, AI requests, indexing or MCP services are not working, check the LemonX status page.
Caching can sometimes make changes appear broken or outdated.
Then test again in a private browser window.
Before running a large workflow, test one small action.
Examples:
If the small workflow works, the issue may be related to batch size, timeout, quota or server limits.
Think about what changed before the issue appeared.
Examples:
On a staging site, temporarily disable non-essential plugins and switch to a default theme to test whether the issue is caused by a conflict.
Do not disable plugins on a production site unless you understand the impact. Use staging whenever possible.
Compatibility HelpInstead of testing a full workflow, test one small action.
Use the product-specific sections below.
If the issue continues, submit a ticket with full details.
Submit a TicketCheck:
Check:
Check:
Check:
Check:
Check:
Check:
Check:
Test major changes on a staging site before production.
Before large updates, migrations, batch translations or MCP write actions, create a backup.
Do not disable many plugins, change themes and update PHP all at once. Make one change, test, then continue.
Write down what you changed and what happened. This helps you reverse changes and helps support diagnose faster.
Do not paste private API keys, passwords, database credentials or full license keys into public tickets or screenshots.
Use one draft page, one URL, one translation or one MCP tool before running large workflows.
Be careful with MCP write tools. Enable only the tools you need and use Preview to Apply whenever possible.
If the issue continues, send us clear details so we can help faster.
AEO, Code, Verto, MCP, Pro, Theme or Suite.
Include plugin or theme version.
Include your WordPress version.
Include your PHP version.
Tell us which theme is active.
List SEO, translation, page builder, cache, security and WooCommerce plugins.
Copy the full message if available.
Remove private data before uploading.
Write the exact steps that trigger the issue.
Tell us what you expected to happen.
Tell us what happened instead.
Mention updates, plugin installs, theme changes, hosting changes or API key changes.
Fix plugin and theme installation issues.
OpenFix activation, renewal and entitlement issues.
OpenCheck WordPress, PHP, theme, plugin and hosting compatibility.
OpenSee active known issues and workarounds.
OpenCheck LemonX services.
OpenRead product-specific docs.
OpenContact LemonX Support.
OpenStart with the quick checks: confirm product activation, update versions, check license status, clear cache, check system status and test one small workflow.
For small checks, it may be okay. For major changes, plugin conflict tests, theme switching, MCP write tools, migration or large translation batches, use a staging site.
Test on staging by disabling non-essential plugins, then re-enable them one by one. If the issue appears only when another plugin is active, it may be a conflict.
Do not repeatedly refresh the page. Check your email for WordPress recovery mode, disable the affected plugin via SFTP if needed, review PHP error logs and submit a ticket.
Common reasons include invalid API key, provider quota, rate limit, timeout, long prompt, slow model response or server memory limits.
Common reasons include cron issues, provider quota, queue batch size, server timeout, cache conflict or translation provider error.
Common reasons include wrong endpoint, authentication issue, SSL problem, REST API block, security plugin rules or site identity mismatch.
Clear cache first. Then check CDN cache, page cache, browser cache, theme template output and whether the content was saved as draft.
No. Never send private API keys, passwords, hosting credentials or database credentials in plain text.
Product name, version, WordPress version, PHP version, active theme, related plugins, exact error message, screenshots, steps to reproduce and recent changes.
Send us the product name, version, WordPress environment, exact error message and steps to reproduce. We will help you find the next step.
Please remove private data from screenshots and never include passwords, private API keys, hosting credentials or payment information in your ticket.