Under Investigation
Issues that the LemonX team is actively reviewing but has not yet fully confirmed or fixed.
View InvestigationsCheck current known issues, affected LemonX products, available workarounds, fix status and version notes. If you are experiencing a problem that is not listed here, you can submit a support ticket with your site details and reproduction steps.
Known issues are product or environment problems that have been reported, confirmed or are under investigation. Not every issue affects every website. Many problems depend on your WordPress version, theme, plugins, hosting environment, cache settings, AI provider or license plan.
Issues that the LemonX team is actively reviewing but has not yet fully confirmed or fixed.
View InvestigationsIssues with a temporary solution you can apply before a permanent fix is released.
View WorkaroundsThis page helps you understand whether a problem you are experiencing is already known, what products are affected, what you can do now, and when a fix may be available.
The current handling stage of the issue.
The LemonX product or module involved.
How the issue may affect your website or workflow.
Workaround: A temporary action you can take before the issue is fully resolved.
Fix Status: Whether a fix is being investigated, planned, tested or released.
Use this overview to quickly check the latest known problems and their current status.
Some users may still see an expired or inactive license message after completing renewal.
Refresh license status from WordPress Dashboard → LemonX → License. If the status does not update, log out and reconnect your LemonX account.
Monitoring
Translation jobs may remain pending or process slowly.
Enable real cron on your server or ask your host to confirm that WP-Cron is running correctly.
Fix Planned
Claude, Codex or other MCP clients may not connect to WordPress.
Check your security plugin firewall logs and allow LemonX MCP REST API routes.
Monitoring
Structured data testing tools may show duplicate Schema types.
Use one plugin as the primary Schema output source and disable overlapping Schema output where possible.
Documentation Updated
Generated layouts may not render exactly as expected inside builder-specific templates.
Use standard WordPress blocks or insert generated content as clean HTML where supported.
Ongoing Compatibility Improvements
Usage numbers may lag behind actual usage in the account dashboard.
Wait and refresh the account dashboard. This does not usually affect product access.
Under Investigation
We have received reports and are reviewing logs, environment details or reproduction steps. The issue may not yet be confirmed.
The issue has been reproduced or verified by the LemonX team.
A temporary solution is available while a permanent fix is being prepared or tested.
A fix has been planned for a future product update.
A fix has been created and is being tested internally or in beta.
A fix has been released in a product update.
The issue has been addressed or reduced, and we are monitoring reports.
The issue is resolved, no longer reproducible, or determined to be caused by an external configuration.
LemonX AEO includes SEO, AEO, Schema, indexing, AI visibility, reports and content optimization tools. Some known issues may be caused by overlapping SEO plugins, indexing provider limits, cache behavior or search engine API configuration.
If another SEO plugin outputs Schema for the same page, structured data testing tools may show duplicate Article, FAQ, Product, Breadcrumb or Organization Schema.
If you use Yoast SEO, Rank Math, AIOSEO, SEOPress or another SEO plugin, review which plugin controls Schema output before enabling all LemonX AEO Schema features.
Google, Bing, Yandex or IndexNow submission may fail if the API key, verification file, service account or site ownership is not configured correctly.
If the issue continues, submit a ticket with the provider name, URL, error message and screenshot of the integration settings.
Rank tracking, AI citation checks or visibility reports may not update instantly after content changes.
Search and AI visibility systems are not real-time. Allow time for crawlers, indexing systems and AI engines to process updated content.
LemonX Code includes AI page generation, visual editing, workflow writing, template library, design system, OCR, knowledge base, forms, modals, media AI, migration and security tools.
Some page builders store layouts in custom formats. AI-generated sections may appear as standard HTML, blocks or content rather than native builder widgets.
For best results, use LemonX Code with clean WordPress content, Gutenberg workflows or LemonX Theme when building AI-generated pages.
Large PDFs, high-resolution images or scanned documents may fail, time out or process slowly depending on hosting resources.
If the same file fails repeatedly, submit the file type, file size and error message to support.
Newly uploaded documents may not appear in AI responses immediately if indexing, parsing or background processing has not completed.
Do not rely on newly uploaded documents until the knowledge base confirms that processing is complete.
LemonX Verto handles AI translation, multilingual SEO, URL translation, hreflang, language switchers, translation queues, translation memory, glossary and cache.
Translation jobs may remain pending if WP-Cron is disabled, blocked or not triggered by low-traffic websites.
For production multilingual websites, real cron is recommended over traffic-based WP-Cron.
Translated URLs may conflict with existing pages, posts, categories, product slugs or manually created language URLs.
Before bulk translation, test URL translation on one content type and one language.
If another multilingual plugin also outputs hreflang tags, search engines may see duplicate or conflicting language signals.
Avoid letting multiple translation plugins control language routing and hreflang at the same time unless the integration is intentionally configured.
LemonX MCP connects WordPress with MCP-compatible AI clients such as Claude, Codex, Cursor and other clients. Most MCP issues are caused by authentication, REST API blocking, site URL mismatch, permissions or security plugin rules.
The MCP client may not detect tools, may fail authentication or may not connect to the WordPress site.
Start by testing whether the WordPress REST API is reachable and whether the configured site URL matches the live website.
The MCP client may be able to read site information but fail when attempting to update, create or apply changes.
Write actions require stricter permissions than read actions. Confirm both WordPress permissions and LemonX MCP tool permissions.
The MCP client may warn that the connected site does not match the expected site identity.
Do not apply changes through MCP until you confirm the AI client is connected to the correct website.
LemonX Pro manages licenses, cloud gateway access, entitlements, usage, quotas, product access and premium features.
After renewing, some sites may continue showing the previous license status until the site refreshes license data.
If the issue continues after refreshing, submit a ticket with your account email, website URL and license status screenshot.
Newly upgraded features may not appear immediately in the WordPress dashboard.
Most entitlement updates should appear after license refresh. Contact support if access remains incorrect.
Usage numbers may not update immediately after heavy AI, translation or indexing activity.
Usage display delays usually do not mean the feature is unavailable.
LemonX Theme provides a lightweight foundation for AI-generated pages, canvas layouts, templates and clean WordPress rendering.
AI-generated full-width sections may appear inside a narrow content container depending on page template or theme layout settings.
If the page is intended to be a landing page, use a canvas or full-width template.
Landing pages, campaign pages or AI-generated pages may show site header/footer when a blank canvas layout is expected.
Use a dedicated canvas template for pages that should not show standard site chrome.
These issues relate to the LemonX account dashboard, downloads, license dashboard, billing visibility or product access display.
A user may not immediately see downloads after purchase or account creation.
Most missing download issues are caused by email mismatch or incomplete payment status.
The dashboard may load partially or appear blank for some browser, cookie or extension configurations.
If the issue continues, submit browser name, operating system, screenshot and account email.
Some issues are caused by hosting restrictions, server configuration, firewall rules, cache settings or external provider limits.
License verification, AI provider calls, translation requests, indexing submissions and cloud gateway requests may fail.
LemonX products require outbound HTTPS connections for many cloud, AI and indexing workflows.
MCP connections, dashboard actions, license verification, data refresh and some admin features may fail.
Blocking REST API globally can break many modern WordPress plugin features.
Users may see older content, outdated translations, old Schema or old page sections after updates.
After major content generation or translation updates, clear all layers of cache.
Use this area to communicate issues that have been fixed in recent versions.
Resolved Issue Template: Issue name · Affected Product · Fixed In version · Description · Recommended Action: Update the affected LemonX product to the latest version.
Description: The license refresh action now updates more dashboard areas after account reconnection.
Recommended Action: Update LemonX Pro to the latest version.
Description: The queue status display now clears completed job notices more reliably.
Recommended Action: Update LemonX Verto to the latest version.
If you are not sure whether your issue is listed, try these safe steps first.
Install the latest versions of LemonX products before troubleshooting.
Go to WordPress Dashboard → LemonX → License and refresh your license.
Clear WordPress cache, object cache, CDN cache and browser cache.
Temporarily disable non-essential plugins on staging to identify conflicts.
Temporarily switch to a default WordPress theme or LemonX Theme to rule out theme conflicts.
Make sure WordPress REST API is not globally disabled.
Ask your host whether outbound HTTPS requests are allowed.
Security tools may block API, MCP, license or provider requests.
Admin dashboard problems may be browser or extension related.
Before changing production settings, reproduce the issue on staging when possible.
If your problem is not listed here, submit a support ticket with enough detail for the LemonX team to investigate.
Why details matter: Many LemonX issues depend on environment configuration. The more details you provide, the faster support can identify whether the issue is caused by LemonX, WordPress, another plugin, hosting, cache, firewall, API provider or account configuration.
No. Many known issues affect only specific environments, plugins, hosting providers, settings or product combinations.
A known issue is a problem that has been reported or confirmed. A compatibility issue usually happens when LemonX overlaps or conflicts with another plugin, theme, hosting rule or environment setting.
Follow the workaround first. Then update LemonX products when a fix is released.
Submit a support ticket with your WordPress version, LemonX version, theme, active plugins, hosting provider, screenshots and reproduction steps.
Not always. It means reports are being reviewed. The issue may later be confirmed, closed or identified as an environment-specific problem.
No. A workaround is temporary. You should still update when a permanent fix is released.
Check this page, the product changelog or release notes for the affected LemonX product.
For some issues, beta fixes may be available to selected users or support cases. Contact support if you need early access to a fix.
Because many issues are caused by interactions between LemonX, WordPress, themes, plugins, cache, security tools, hosting and external providers.
For major issues, test on staging first whenever possible.
Send us the details and our support team will help investigate. Include your product version, environment details, screenshots and exact steps to reproduce the issue.
For faster support, include your WordPress version, PHP version, LemonX product version, theme, active plugins, hosting provider, cache/security tools and reproduction steps.