Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WordPress Not Working on Chrome? How to Fix It

WordPress Not Working on Chrome? How to Fix It

Short answer

When WordPress works in other browsers but not in Chrome, the cause is almost always on Chrome's side: old cached files or cookies, a browser extension, a stale DNS or HTTPS record, or Chrome blocking mixed or insecure content. Open the site in an Incognito window first; if it works there, clear Chrome's cache and cookies for the site and turn off extensions.

Key takeaways

  • If the site works in Firefox, Safari or Edge, the problem is usually Chrome's cache, cookies, extensions or settings.
  • An Incognito window with extensions off is the fastest test.
  • Login loops in Chrome usually come from old cookies or a mismatch between http and https site addresses.
  • Chrome is stricter about SSL, mixed content and redirects than some browsers.
  • If the site fails in Chrome on every device, the cause is on the server, not in your browser.

Is the problem Chrome or your WordPress site?

Test the same page in another browser and in a Chrome Incognito window; if both work, the problem is your normal Chrome profile, not WordPress.

This one test saves a lot of time. Use this table to read the result:

Test resultWhat it means
Works in Firefox or Safari, fails in ChromeChrome cache, cookies, extensions or settings
Works in Chrome Incognito, fails in normal ChromeExtensions or stored cookies and cache
Fails in Chrome on every device and networkServer, SSL or redirect problem on the site
Fails only on your networkDNS, firewall or IP block
Fails only in Chrome on your phoneMobile cache, data saver or an old app version

Ask someone on a different network to open the site in Chrome. If it works for them, the issue is on your computer or connection.

How do you clear Chrome's cache and cookies for one site?

Clear the cached files and cookies for your site only, so Chrome loads fresh copies of the pages and forgets old login sessions.

The quickest way is from the site itself:

  1. Open your site in Chrome
  2. Click the site settings icon to the left of the address bar
  3. Choose Site settings
  4. Click Delete data, then reload the page

You can also press Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac for a hard refresh. Google's help page explains how to clear cache and cookies in Chrome for every device.

After clearing, log in to wp-admin again. Old login cookies are a common cause of dashboards that keep sending you back to the login screen.

Could a Chrome extension be breaking WordPress?

Yes, ad blockers, privacy tools, grammar checkers, password managers and translation extensions often break the block editor, media uploads or page layouts.

Incognito mode turns extensions off by default. If the site or dashboard works there, an extension is the likely cause.

Open chrome://extensions, switch all extensions off, then turn them back on one at a time and reload your site after each. The one that breaks the page again is the culprit.

You can usually keep the extension and add your site to its allow list instead. For editor-specific problems, our guide to a WordPress editor not working covers more causes.

Why does Chrome keep redirecting or showing “Too many redirects”?

A redirect loop in Chrome usually comes from old cookies, a cached redirect, or conflicting http and https settings between WordPress, the server and a CDN.

Chrome caches permanent 301 redirects. If your site once redirected somewhere else, Chrome may keep following the old redirect even after you fixed it on the server.

Clear the site's data in Chrome first. If the loop continues in Incognito and other browsers, the loop is on the server. Our guide to fixing too many redirects walks through WordPress, .htaccess and CDN settings.

If you use Cloudflare, a wrong SSL mode is a very common cause. See our guide on the Cloudflare redirect loop.

Is Chrome blocking the site for SSL or security reasons?

Chrome shows a full-page warning or refuses to load parts of the page when the SSL certificate is invalid, the page mixes HTTP files into HTTPS, or Safe Browsing has flagged the site.

Each warning means something different:

  • “Your connection is not private”: the certificate is expired, missing or for the wrong domain
  • “Not secure” in the address bar: the page loads over HTTP
  • Missing images or broken layout on an HTTPS page: Chrome blocked mixed content
  • Red “Dangerous site” screen: Google Safe Browsing detected malware or phishing

For certificate warnings, follow our guide to fixing “Your connection is not private”. For a red warning screen, check the site in the Google Safe Browsing site status tool and clean the site before requesting a review.

How do you reset Chrome's DNS and HTTPS memory?

If you recently moved hosts or changed DNS, flush Chrome's internal DNS cache and, when needed, delete the site's HSTS entry so Chrome stops using old records.

Chrome keeps its own DNS cache. Open chrome://net-internals/#dns and click Clear host cache. Then open chrome://net-internals/#sockets and click Flush socket pools.

If the site used HTTPS with HSTS and you have temporarily disabled SSL, Chrome will refuse to load it over HTTP. Open chrome://net-internals/#hsts, type your domain under Delete domain security policies and click Delete.

Your operating system and router also cache DNS. Restarting the router or flushing the system DNS cache helps when Chrome alone does not.

Why does the WordPress dashboard not work in Chrome?

Dashboard problems in Chrome usually come from extensions, blocked third-party cookies on a different admin domain, or cached admin scripts after an update.

Check that your WordPress Address and Site Address use the same domain and protocol. A dashboard on http:// with a site on https://, or www and non-www mixed, can cause login and cookie problems in Chrome.

If wp-admin fails in every browser, it is not a Chrome issue. Our guide on fixing wp-admin not loading covers server-side causes.

For login pages that refresh and send you back, see our guide to the login page refreshing and redirecting.

What if Chrome itself is out of date or misconfigured?

Update Chrome, try a new Chrome profile, and as a last step reset Chrome's settings, which keeps bookmarks and passwords but turns off extensions and clears temporary data.

Open the menu, choose Help, then About Google Chrome to install updates. An outdated browser can fail on modern scripts and security settings.

A new profile is a clean test without touching your current setup, and it only takes a minute to create. If the site works in a fresh profile, something in your old profile's settings or extensions is to blame.

If you manage a company computer, admin policies may block certain sites or scripts. Check chrome://policy or ask your IT team.

How do you stop Chrome-only problems in future?

Keep your site on HTTPS with matching site addresses, avoid long cache times on admin pages, and test the site in Chrome Incognito after big changes.

A few site-side habits prevent most browser-specific trouble:

  • Use one canonical address, either www or non-www, always on https
  • Purge caches after updates so Chrome does not hold mixed old and new files
  • Fix mixed content warnings as soon as they appear
  • Keep plugins updated so admin scripts stay compatible with current Chrome

When a page breaks in Chrome, the DevTools Console shows the exact error. Press F12, open the Console tab and reload the page.

Red lines that mention a file under /wp-content/plugins/ or /wp-content/themes/ point to the plugin or theme behind the problem. Lines about mixed content or blocked requests point to SSL and security settings instead.

Copy the error text before you contact your host or a plugin developer. A precise error message usually gets a faster and more accurate answer than a description of what the page looks like.

If you manage sites for clients, keep a clean Chrome profile with no extensions just for testing. It removes a whole class of false alarms when someone reports that the site looks broken.

Frequently asked questions

Why does my WordPress site work in Firefox but not Chrome?

Chrome is probably using old cached files, old cookies, a cached redirect or an extension that blocks scripts. Open the site in an Incognito window to confirm, then clear the site's data in Chrome and disable extensions one by one.

Why can't I log in to WordPress in Chrome?

A login loop in Chrome usually comes from old cookies or mismatched site addresses, such as www and non-www, or HTTP and HTTPS. Clear the site's cookies and make sure both addresses in Settings > General match exactly.

How do I clear Chrome's DNS cache?

Type chrome://net-internals/#dns in the address bar and click Clear host cache. Then go to the sockets page in the same section and flush socket pools. Restart Chrome if the old address still loads.

Does Chrome block WordPress sites without SSL?

Chrome still loads HTTP sites but marks them Not secure and warns when people type into forms. It also blocks insecure scripts on HTTPS pages, which can break layouts and features until mixed content is fixed.

Why does my WordPress editor not load in Chrome?

A browser extension, cached editor scripts or a blocked REST API are the usual causes. Test in Incognito first. If the editor works there, an extension is interfering, so add your site to its allow list or turn it off.

Sources

  1. Clear cache and cookies Google Account Help
  2. Safe Browsing site status Google Transparency Report
  3. Console overview Chrome for Developers
  4. Mixed content MDN Web Docs

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.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.