Troubleshooting
Weglot Visual Editor Not Working: Causes and How to Fix It

Short answer
The Weglot visual editor usually fails when your site sends headers that block it from loading inside the dashboard, the site is password protected or in maintenance mode, a browser extension interferes, or the project URL is wrong. Test in a private window first, then check your security headers.
Key takeaways
- The visual editor runs in the Weglot dashboard and loads your live site.
- Test in a private window to rule out extensions and cookie blocking.
- X-Frame-Options and CSP frame-ancestors headers can block the editor.
- Password protection and maintenance mode stop the editor loading pages.
- Use the dashboard translation list as a fallback while you fix it.
Why is the Weglot visual editor not working?
The Weglot visual editor usually fails because your site blocks being shown inside another page, the site is private or in maintenance mode, a browser extension interferes, or the project URL does not match your site.
The visual editor lives in your Weglot dashboard, not in WordPress. It loads a live view of your page so you can click text and edit its translation in context. Weglot introduced the current version in its new visual editor update.
Because the editor loads your real site, anything that stops your site being displayed inside the dashboard can break it. Typical symptoms:
- A blank or grey preview area
- An endless loading spinner
- A refused to connect message
- The page loads but text cannot be selected
- Edits save but do not appear on the live site
The sections below cover each cause. Start with the quick browser checks, then move to site settings.
Have you ruled out browser problems?
Try the editor in a private window with extensions disabled, or in a different browser, because ad blockers, privacy tools and strict cookie settings often break it.
Browser problems are the quickest to test. A private window starts without most extensions and with a clean cache.
If the editor works in a private window, one of these is likely the cause:
- An ad blocker or privacy extension
- A script blocker
- Strict third-party cookie or tracking protection
- An old cached version of the dashboard
Disable extensions one by one in your normal browser to find the culprit. Then add an exception for the Weglot dashboard.
Also make sure your browser is up to date. The editor relies on modern browser features.
If you work on a company network, a firewall or proxy can also block parts of the dashboard. Try the editor on another network, such as a phone hotspot, to rule this out.
Is your site blocking being loaded in a frame?
Security headers such as X-Frame-Options or a Content-Security-Policy frame-ancestors rule can stop the editor from displaying your page, so relax them for the Weglot dashboard.
Many security plugins, hosts and CDNs add headers that prevent your site from loading inside another site. That protects against clickjacking, but it can also block tools like visual editors.
Two headers matter:
| Header | What blocks the editor |
|---|---|
| X-Frame-Options | DENY or SAMEORIGIN |
| Content-Security-Policy frame-ancestors | Any rule that does not list the Weglot dashboard |
To check, open your site, press F12, go to the Network tab, reload, click the first request and read the response headers.
If you see these headers, find where they are set. Common places are a security plugin, your .htaccess file, your host's panel or a CDN rule.
Allow the Weglot dashboard as a frame ancestor rather than removing protection entirely. Weglot support can confirm the exact domain to allow.
Our guide on how to edit the .htaccess file shows how to find and change header rules safely.
Is your site private, password protected or in maintenance mode?
The editor cannot load pages hidden behind a password, login wall, coming-soon page or IP restriction, because it sees what a logged-out visitor sees.
Check whether:
- A maintenance or coming-soon plugin is active
- The site is on a staging URL with HTTP authentication
- Your host restricts access by IP address
- A membership plugin hides the page from logged-out users
Temporarily open the page to the public, or use a staging site without a password, while you edit translations. Re-enable protection afterwards.
Remember that some caching and security plugins show a different page to visitors they think are bots. If the editor loads a challenge page or a captcha, add an exception for the Weglot dashboard in that plugin or in your CDN firewall rules.
Pages that only logged-in members can see may need translating with Weglot's other tools, such as the translation list in the dashboard.
Does the project URL match your site?
The visual editor opens the URL stored in your Weglot project, so a changed domain, missing www or old http address can make it load the wrong site or nothing.
Open your project settings in the Weglot dashboard and compare the website URL with your live address. Check:
- http versus https
- www versus non-www
- An old staging or temporary domain
- A trailing path if WordPress is in a subfolder
If you moved the site or switched to HTTPS, update the project URL. Our guide on installing an SSL certificate on WordPress covers the HTTPS side of a move.
Is the Weglot plugin connected and active?
The Weglot plugin must be active and linked to the same project with the correct API key, or the editor shows untranslated or empty pages.
In WordPress, go to the Weglot settings page and confirm the API key matches the one in your Weglot project. A mismatch happens when you create a second project or copy a site from staging.
Also check that your translation languages are set and, if Weglot's private language mode is on, that you understand who can see those languages. Private languages are hidden from regular visitors, which can be confusing when you test.
Our guide on how to use the Weglot plugin explains the connection steps if you need to start again.
After changing the key, save the settings, clear your caches and reload the editor. The first load after a change can take a little longer while Weglot fetches the page again.
Why can you not select some text in the editor?
Text you cannot click is often loaded by JavaScript after the page, set inside images, or excluded from translation in your Weglot rules.
Check these cases:
- Dynamic content. Text loaded later by scripts may need Weglot's dynamic content settings.
- Images. Words inside images cannot be edited as text. Use media translation to swap the image.
- Exclusions. Look at your exclusion rules for URLs or CSS selectors that skip this content.
- Iframes. Embedded content from other sites, such as videos or maps, is not part of your page.
If the text exists in your page source but is not editable, find it in the translation list in your dashboard instead. You can search for the original text there.
Why do saved edits not appear on your site?
Saved translations often do not appear because a page cache or CDN is still serving the old translated page, so clear every cache layer.
Clear your caching plugin, your host's cache and your CDN, then load the translated URL in a private window. Our guide on how to clear cache in WordPress lists each layer.
If the change still does not show, confirm you edited the right language and the right string. The same phrase can appear in several places, each with its own translation.
What should you do if the editor still fails?
Collect the browser console errors and your response headers, then contact Weglot support, since the editor runs on their platform and they can see logs you cannot.
Open the browser developer tools, go to the Console tab, and reload the editor. Errors mentioning frames, refused connections or blocked content are useful to support.
On the WordPress side, turn on debug logging to catch PHP errors. The debugging guide explains how.
While you wait, you can keep working in the dashboard's translation list. It does not depend on loading your site, so it works even when the visual editor does not.
Frequently asked questions
Why is the Weglot visual editor blank?
A blank editor usually means your site refused to load inside the dashboard. Security headers such as X-Frame-Options or a strict Content-Security-Policy are the common cause. A browser extension can also block it, so test in a private window.
Can I use the Weglot visual editor on a staging site?
Yes, if the staging site is publicly reachable and linked to the right project. Password protection or IP restrictions on staging stop the editor loading pages, so lift them while editing.
Is the Weglot visual editor inside WordPress?
No. The visual editor is part of the Weglot dashboard on Weglot's website. The WordPress plugin connects your site to your project, and you edit translations from your Weglot account.
Why are my visual editor changes not live?
Caching is the usual reason. Clear your caching plugin, host cache and CDN, then check the translated page in a private window. Also confirm you edited the correct language.
How can I translate without the visual editor?
Use the translation list in your Weglot dashboard. You can search for any original text, edit its translation and save. It does not need to load your site, so it works when the visual editor fails.
Sources
- Weglot plugin WordPress.org Plugins
- Feature update: new visual editor Weglot
- X-Frame-Options MDN Web Docs
- CSP: frame-ancestors MDN Web Docs
- Debugging in WordPress WordPress Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


