WordPress Invalid Json Response Error Step By Step Fix? What to Check First

Quick Answer: WordPress Issue is usually caused by session, network, or access filtering issues. Restart the app/browser, clear cache, and retry on a different network. Start with the fastest checks before assuming a deeper system issue.

What’s causing this issue?

• Session problem
• Cache conflict
• Network filtering
• Temporary service-side issue

Quick answer: The WordPress invalid JSON response error usually happens when the block editor cannot communicate with your site’s REST API correctly.

Start by refreshing permalinks, testing in a clean browser session, disabling plugin conflicts, and checking whether security, cache, or mixed URL settings are blocking the request.

Quick Fix Checklist

• Reload the editor and try saving again.
• Open WordPress in an incognito/private browser window.
• Clear your browser cache and cookies for the site.
• Temporarily disable browser extensions, especially ad blockers, privacy tools, and script blockers.
• Go to Settings > Permalinks and click Save Changes without changing anything.
• Update WordPress, your theme, and plugins.
• Temporarily disable caching, security, and SEO plugins one by one.
• Check that WordPress Address (URL) and Site Address (URL) match exactly.
• Test from another browser profile or another browser.
• Check /wp-json/ in your browser. If it does not load, the REST API is likely blocked.

Causes

This error is not usually about the content itself. It usually means WordPress sent or expected JSON data, but something interrupted, changed, or blocked the response.

• Permalink rules are stale: WordPress REST routes may stop resolving correctly until permalinks are refreshed.
• Plugin conflict: Security, cache, SEO, redirect, firewall, or optimization plugins can alter REST API responses.
• Theme conflict: A theme function can inject output, warnings, or redirects into API requests.
• Browser extension interference: Ad blockers, privacy extensions, and script filters can block editor requests.
• Expired session or cookie issue: The editor may fail if your login session is stale.
• Mixed site URLs: HTTP/HTTPS mismatch or different www/non-www settings can break API calls.
• Security or CDN filtering: Firewalls, bot protection, or edge caching can block or rewrite JSON responses.
• Update conflict: A recent WordPress, plugin, or theme update may have changed REST behavior.
• Permission issue: A role, plugin setting, or API restriction may prevent save requests.

Cause	Fix
Stale permalinks	Open Permalinks and click Save Changes
Browser cache or extension	Use incognito mode, clear site data, disable extensions
Plugin conflict	Disable plugins one by one, starting with cache and security tools
REST API blocked	Test /wp-json/ and remove blocking rules or redirects
HTTP/HTTPS or URL mismatch	Make WordPress URL and Site URL identical
CDN or firewall interference	Purge cache and temporarily bypass security filtering

Step-by-Step Fix

1. Refresh the page and log in again.
   Sometimes the editor loses its session token. Log out of WordPress, close the tab, sign in again, and retry the update.
2. Test in a private window.
   Open your site admin in incognito/private mode. If the error disappears, the problem is likely cached site data, cookies, or an extension in your normal browser profile.
3. Clear browser data for the site.
   Delete cached files and cookies for your WordPress domain only, then reopen the editor. This is one of the fastest fixes for stale editor sessions.
4. Disable browser extensions.
   Turn off ad blockers, privacy tools, script blockers, password managers, and header-modifying extensions. Then reload the editor and test again.
5. Resave permalinks.
   In WordPress admin, go to Settings > Permalinks and click Save Changes. This refreshes rewrite rules and often restores broken REST API routes.
6. Check the REST API directly.
   Visit https://yourdomain.com/wp-json/. You should see JSON output. If you see a redirect, login page, 403, 404, or HTML instead of JSON, something is interfering with the API.
7. Confirm your site URLs match.
   Go to Settings > General and verify that WordPress Address (URL) and Site Address (URL) use the same version of the domain, including HTTPS and www/non-www.
8. Disable plugins in the right order.
   Temporarily deactivate plugins one at a time, starting with:
   • cache plugins
   • security/firewall plugins
   • redirect plugins
   • SEO plugins
   • optimization/minify plugins
   • custom REST/API plugins

   After each change, test the editor again.

9. Switch to a default theme temporarily.
   Activate a default WordPress theme and test saving a post. If the error stops, your theme or a theme function is affecting editor requests.
10. Purge all cache layers.
    This is the non-obvious fix many guides miss. Clear:
    • browser cache
    • WordPress cache plugin cache
    • server or host cache
    • CDN cache

    Old cached headers or redirects can break JSON responses even after plugin changes.

11. Check for update conflicts.
    If the problem started right after an update, compare recently updated plugins and theme changes. Roll back only the specific plugin or theme update if you have a safe staging workflow.
12. Inspect the browser console and network request.
    Open Developer Tools and retry the save. Look for failed requests to wp-json, 401/403/404 errors, CORS issues, or HTML returned where JSON should be. This quickly confirms whether the problem is browser-side or site-side.

Still Not Working

If the error continues after the basic fixes, use deeper troubleshooting focused on the editor request itself.

• Create a clean browser profile: If incognito works but your normal browser does not, your main profile may have corrupted site data or an extension policy issue.
• Check user-role restrictions: Some membership, workflow, or security plugins limit REST API access by role. Test with an administrator account.
• Temporarily bypass CDN or web application firewall rules: Security layers can block POST requests to REST endpoints or strip headers needed by the editor.
• Look for forced redirects: Login redirects, maintenance mode, country blocks, or bot protection pages can return HTML instead of JSON.
• Test with all plugins off, then re-enable one by one: This is the fastest way to isolate a conflict if the cause is not obvious.
• Use Site Health in WordPress: Check for REST API or loopback warnings that point to blocked requests.
• Reinstall the affected plugin or update package: If the issue started after a partial update, reinstalling the plugin or theme can restore missing files.
• Escalate with evidence: Contact your host, plugin developer, or theme support with the exact wp-json error, browser console message, and the list of recent updates.

If you manage a production site, test major changes in staging first. The most common real-world root causes are plugin conflicts, stale cache layers, blocked REST API requests, and browser extensions modifying admin traffic.

Frequently Asked Questions