{"id":4387,"date":"2026-10-14T06:33:01","date_gmt":"2026-10-14T06:33:01","guid":{"rendered":"https:\/\/www.wpchatsupport.com\/blog\/?p=4387"},"modified":"2026-10-14T06:43:50","modified_gmt":"2026-10-14T06:43:50","slug":"fix-err-too-many-redirects-wordpress","status":"publish","type":"post","link":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/","title":{"rendered":"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress"},"content":{"rendered":"<h2>Introduction<\/h2>\n<p>You type your own address into the browser and nothing loads. Instead you see a short, blunt message. In Chrome it reads ERR_TOO_MANY_REDIRECTS. Firefox says the page is not redirecting properly. Safari says too many redirects occurred. The wording changes but the cause is the same. Your site keeps sending the browser somewhere else, over and over, until the browser gives up.<\/p>\n<p>Browsers only follow a limited number of redirects before they stop. That limit exists to protect you. Without it, the browser would loop forever. So this error is not really a failure. It is a safety brake.<\/p>\n<p>The ERR_TOO_MANY_REDIRECTS error in WordPress almost always shows up straight after a change. You added an SSL certificate. You moved from http to https. You switched your domain to www, or away from it. You turned on Cloudflare. You installed a redirect plugin or a security plugin. Each of these touches the same small set of settings, and two of them only have to disagree slightly for a loop to form.<\/p>\n<p>The good news is that your site is intact. Your files are fine. Your database is fine. Two rules are simply arguing with each other. This guide shows you how to find which two. You will learn the signs, the real causes, a step by step fix for each cause, and the habits that stop the loop coming back. Start at Step 1 even if you think you know the answer. The first two steps take two minutes and rule out the most common false alarms.<\/p>\n<h2>Signs That Show the ERR_TOO_MANY_REDIRECTS Error in WordPress<\/h2>\n<p>Redirect loops have a distinct fingerprint. Checking it first saves you from fixing the wrong thing. Here is what people actually see.<\/p>\n<p><strong>The address bar flickers and then stops.<\/strong> You may briefly see the URL change between http and https, or between the www and non-www versions of your domain. Then the error page appears. That flicker is the loop happening in front of you.<\/p>\n<p><strong>The error text depends on the browser.<\/strong> Chrome and Edge say ERR_TOO_MANY_REDIRECTS. Firefox says the page is not redirecting properly. Safari says too many redirects occurred trying to open the page. All three mean one thing.<\/p>\n<p><strong>Some pages load and others do not.<\/strong> A loop that only hits the login page points to one cause. A loop on the whole site points to another. Make a note of which pages fail.<\/p>\n<p><strong>Only the dashboard loops.<\/strong> The public site works perfectly but wp-admin or wp-login.php will not open. This narrows the cause down sharply, because it points at the admin HTTPS setting.<\/p>\n<p><strong>A private or incognito window works.<\/strong> This is a very useful clue. If the site loads in incognito but not in your normal window, the loop is stored in your own cookies or cache rather than on the server.<\/p>\n<p><strong>The site works for logged out visitors but not for you.<\/strong> That also points to cookies, or to a cached redirect that only your session is receiving.<\/p>\n<p><strong>The loop started at a known moment.<\/strong> Think back one step. An SSL install, a domain change, a new plugin, a Cloudflare setup or a migration are all common triggers. The change you made last is usually the change that caused it.<\/p>\n<p>One more test is worth running. Open the site on your phone over mobile data. If it fails there too, the problem is on the server and not in your browser.<\/p>\n<h2>Reasons Why the ERR_TOO_MANY_REDIRECTS Error Happens in WordPress<\/h2>\n<p>A loop needs two parties. One sends the browser to address A. The other sends it back to address B. Below are the nine real pairings that cause this in WordPress. Find yours before you change anything.<\/p>\n<h3>The two WordPress address settings disagree<\/h3>\n<p>WordPress stores two addresses. One is the WordPress Address, which is where the core files live. The other is the Site Address, which is what visitors type. Both sit on the Settings and then General screen.<\/p>\n<p>WordPress redirects every request to match these values. So if one says https:\/\/example.com and the other says http:\/\/www.example.com, every visit is sent from one to the other and straight back again. Official WordPress guidance is that both should include the https:\/\/ part and should not end with a slash. A mismatch in the protocol, in the www part, or a stray trailing slash is enough to start the loop.<\/p>\n<h3>An SSL or HTTPS plugin forces https while something else pushes back<\/h3>\n<p>SSL plugins work by forcing every request onto https. That is their job. The trouble starts when your server, your host&#8217;s control panel or your CDN is quietly doing the same thing in the other direction.<\/p>\n<p>A common pattern looks like this. The plugin sends a visitor to https. The server has a rule that sends https requests back to http because the certificate is not installed where it expects. Each side is doing exactly what it was told. The visitor just bounces between them.<\/p>\n<h3>Cloudflare is set to Flexible SSL while your server forces HTTPS<\/h3>\n<p>This is the single most common cause on sites behind Cloudflare. Cloudflare has an encryption mode setting under SSL\/TLS. On Flexible, Cloudflare accepts a secure connection from the visitor but sends plain http to your server.<\/p>\n<p>Cloudflare&#8217;s own documentation explains what happens next. If your server automatically redirects all http requests to https, the request goes back to Cloudflare, which sends it to your server as http again. The loop never ends. Nothing is wrong with your WordPress install at all.<\/p>\n<h3>A reverse proxy is hiding the real protocol from WordPress<\/h3>\n<p>Some setups put a proxy or load balancer in front of WordPress. The proxy handles the certificate. It then talks to WordPress over plain http inside the network.<\/p>\n<p>WordPress looks at the request, sees http, and decides the visitor needs to be sent to https. The proxy receives that, strips the encryption again, and hands WordPress another http request. WordPress documentation warns about this directly. It states that forcing secure logins behind a reverse proxy without extra configuration will send requests into an infinite redirect loop. This is the cause behind most loops that affect only wp-admin.<\/p>\n<h3>Conflicting or duplicated rules in .htaccess<\/h3>\n<p>On Apache servers, redirect rules live in a file called .htaccess. Plugins write into it. Security tools write into it. So do hosting control panels. Over time the file collects rules from several sources.<\/p>\n<p>Two problems arise. Sometimes two rules point in opposite directions, such as one forcing www and another removing it. Sometimes the WordPress block gets duplicated, so the same rewrite runs twice. Either case produces a loop that survives deactivating every plugin, because the rule is on disk rather than in the database.<\/p>\n<h3>A redirect plugin contains a rule that loops<\/h3>\n<p>Redirect plugins let you point one URL at another. It is easy to create a loop by accident. A rule can point a page at itself. Two rules can point at each other. A chain can curl back to its own starting point.<\/p>\n<p>Wildcard rules are the usual culprit. A rule that redirects everything under \/blog\/ to \/blog\/ will match its own destination and fire again. The plugin does exactly what you asked, forever.<\/p>\n<h3>Old cookies and cached redirects in your own browser<\/h3>\n<p>Browsers cache permanent redirects. A 301 tells the browser the move is permanent, so it remembers it and stops asking the server. That is good for speed and bad for troubleshooting.<\/p>\n<p>If a bad 301 was served even once, your browser may keep following it after the server has been fixed. WordPress login cookies cause a similar effect. A cookie set for the wrong domain or the wrong protocol makes WordPress think you are not logged in, so it sends you to the login page, which sends you back. This is why incognito often works when your normal window does not.<\/p>\n<h3>A caching plugin or CDN is still serving the old redirect<\/h3>\n<p>Page caches store whole responses, including redirect responses. So a loop can be fixed at the source and still be served from cache for hours.<\/p>\n<p>This is the cause that makes people think a fix did not work. The settings are correct. The cache is simply replaying the broken answer. CDN edge caches do the same thing across many locations at once, so the site may work in one country and loop in another.<\/p>\n<h3>A hard-coded address in wp-config.php overrides your settings<\/h3>\n<p>WordPress lets you set both addresses in wp-config.php using two constants, WP_HOME and WP_SITEURL. When they are present, they win. The values stored in the database are ignored.<\/p>\n<p>That creates a confusing situation. You open Settings and then General, correct the address and save. Nothing changes, because the file is still forcing the old value. WordPress documentation notes that using this method also means you can no longer edit those fields on the General settings screen. A migration or a staging tool very often leaves one of these constants behind.<\/p>\n<h2>How to Fix the ERR_TOO_MANY_REDIRECTS Error in WordPress (Step by Step)<\/h2>\n<p>Work through these in order. Each step clears one cause from the list above, starting with the quickest and safest checks.<\/p>\n<h3>Step 1: Clear Your Cookies and Cache for the Site<\/h3>\n<p>This step clears old cookies and cached redirects, the seventh cause above. Your browser remembers permanent redirects and may keep following one the server no longer sends. A stale WordPress login cookie causes the same bounce between the login page and the dashboard.<\/p>\n<p><strong>Confirm this is your cause first.<\/strong> Open the site in a private or incognito window. Then try a different browser, or your phone over mobile data. If the site loads in any of those, the problem is stored locally and this step will fix it. If every browser and device loops, skip ahead to Step 3.<\/p>\n<p><strong>Make the change.<\/strong> Clear cookies for your domain only rather than wiping everything. In Chrome, click the icon at the left of the address bar, open the site settings, and delete the cookies and site data for that address. In Firefox, open the padlock menu and clear cookies and site data. Then do a hard reload, which is Ctrl and F5 on Windows or Command, Shift and R on a Mac.<\/p>\n<p><strong>Verify it worked.<\/strong> Load the homepage in your normal window. Then log in at wp-login.php. If both work, you are done. If the loop returns, your browser is being handed a fresh bad redirect, so continue to Step 2.<\/p>\n<h3>Step 2: Purge Your Caching Plugin and CDN Cache<\/h3>\n<p>This step clears a cached redirect on the server side, the eighth cause above. Page caches store the whole response, so a loop that has already been fixed can still be replayed to visitors for hours.<\/p>\n<p><strong>Confirm this is your cause first.<\/strong> Two signs point here. The first is that you have already corrected a setting and nothing improved. The second is that the site behaves differently from different places, so it works on your phone but loops on your laptop, or works for a colleague abroad. Check whether a caching plugin is active and whether your domain runs through a CDN.<\/p>\n<p><strong>Make the change.<\/strong> Find the purge control in your caching plugin and clear everything, not just one page. Most plugins put a Purge All or Clear Cache button in the admin bar. If your host runs its own server level cache, clear that from the hosting dashboard too. Then purge your CDN. In Cloudflare, open the Caching section and choose to purge everything.<\/p>\n<p><strong>If the dashboard itself is looping, you cannot click any of that.<\/strong> In that case rename the caching plugin&#8217;s folder inside wp-content\/plugins over FTP. Adding .off to the end is enough. WordPress will deactivate it safely and you can rename it back later.<\/p>\n<p><strong>Verify it worked.<\/strong> Load the homepage in a private window so you know nothing local is involved. Try it from your phone as well. If the loop is gone, the cache was holding the old answer. If not, move to Step 3.<\/p>\n<h3>Step 3: Match the Two WordPress Address Settings Exactly<\/h3>\n<p>This step fixes disagreeing address settings, the first cause above. WordPress redirects every request so that it matches these two values. If they differ in the protocol, in the www part or in a trailing slash, every visit bounces between them.<\/p>\n<p><strong>Confirm this is your cause first.<\/strong> Open Settings and then General. Read both the WordPress Address and the Site Address very carefully, character by character. They should be identical on a normal single site install. Both should start with https:\/\/ if you have a certificate. Neither should end with a slash. A common mistake is one with www and one without.<\/p>\n<p><strong>If you cannot reach the dashboard, use the database instead.<\/strong> Open phpMyAdmin from your hosting panel, choose your site&#8217;s database, and open the wp_options table. The prefix may differ from wp_ on your site. Look for the rows named siteurl and home. Both option_value fields should hold the same address. Back up the database before you edit anything here.<\/p>\n<p><strong>Make the change.<\/strong> Set both to the exact address you want, with https:\/\/ and no trailing slash. Save. If you changed the values in the database, there is nothing else to click.<\/p>\n<p><strong>Verify it worked.<\/strong> Open the homepage in a private window. Then try the opposite form of your address, so test the www version if you chose non-www. It should redirect once and land correctly. If the General settings fields look greyed out or will not save, go to Step 4.<\/p>\n<h3>Step 4: Remove a WP_HOME or WP_SITEURL Override in wp-config.php<\/h3>\n<p>This step fixes a hard-coded address, the ninth cause above. These two constants override whatever is stored in the database. So a correct setting on the General screen is simply ignored.<\/p>\n<p><strong>Confirm this is your cause first.<\/strong> Download wp-config.php from your WordPress root folder by FTP. Open it in a plain text editor and search for WP_HOME and WP_SITEURL. If either line is present, read its value. Another strong sign is on the General settings screen itself. When these constants are set, the two address fields appear fixed and cannot be edited, which matches what WordPress documentation says about this method.<\/p>\n<p><strong>Back up the file before you edit it.<\/strong> wp-config.php holds your database credentials. One broken line will take the whole site offline. Save a copy to your computer first, and edit only in a plain text editor, never in a word processor.<\/p>\n<p><strong>Make the change.<\/strong> You have two options. Either correct both lines so they hold the right address, or delete both lines and let the database values apply again. If you keep them, they must match each other exactly:<\/p>\n<pre>define( 'WP_HOME', 'https:\/\/example.com' );\r\ndefine( 'WP_SITEURL', 'https:\/\/example.com' );<\/pre>\n<p>While you are in the file, also look for a line defining RELOCATE. WordPress warns that leaving this constant in place is insecure, so remove it if a migration left it behind.<\/p>\n<p><strong>Verify it worked.<\/strong> Upload the file and load the homepage in a private window. Then open Settings and then General and confirm the fields are now editable and correct. If the loop continues, move to Step 5.<\/p>\n<h3>Step 5: Deactivate Your SSL and Security Plugins One at a Time<\/h3>\n<p>This step fixes a plugin forcing https against something pushing back, the second cause above. SSL plugins exist to force every request onto https. A loop forms when your server or control panel is sending https requests the other way.<\/p>\n<p><strong>Confirm this is your cause first.<\/strong> Ask when the loop started. If it began the moment you activated an SSL, HTTPS or security plugin, this is almost certainly it. List your active plugins and pick out anything that handles SSL, HTTPS, redirects, firewalls or login hardening.<\/p>\n<p><strong>Make the change.<\/strong> If you can still reach the dashboard, deactivate those plugins one at a time, testing the site in a private window after each one. Stop at the plugin that restores the site. If you cannot reach the dashboard, connect by FTP and rename the suspect plugin folder inside wp-content\/plugins, adding .off to the name. Do one folder at a time so you learn which plugin is responsible.<\/p>\n<p><strong>Then decide which side should force https.<\/strong> Pick one place only. Either let your host or server handle the redirect, or let the plugin do it, never both. Most managed hosts now force https at server level, which means an SSL plugin is no longer needed.<\/p>\n<p><strong>Verify it worked.<\/strong> With the plugin off, load both the http and https versions of your homepage. Each should settle on https after a single redirect. If the loop is gone, reactivate your other plugins one by one to confirm nothing else conflicts. If the loop remains, go to Step 6.<\/p>\n<h3>Step 6: Audit Your Redirect Plugin Rules for Loops<\/h3>\n<p>This step fixes a looping redirect rule, the sixth cause above. Redirect plugins do exactly what you tell them. A rule that points a URL at itself, or two rules that point at each other, will fire forever.<\/p>\n<p><strong>Confirm this is your cause first.<\/strong> Check whether only certain URLs loop while the rest of the site is fine. That pattern points strongly at a rule rather than a site wide setting. Open your redirect plugin and read its list of rules. Look for any source and destination that are the same. Then look for wildcard rules, because a rule sending everything under a folder to that same folder will match its own destination.<\/p>\n<p><strong>Make the change.<\/strong> Disable the suspect rule rather than deleting it, so you can restore it if you are wrong. Test the URL. If it loads, you have found the rule and can rewrite it properly. For chains, redirect each old URL straight to the final destination instead of hopping through steps. One hop is also better for speed and for search engines.<\/p>\n<p><strong>Watch for rules you did not write.<\/strong> Some security plugins and some SEO plugins add redirects of their own, often when you change a post slug. Check their redirect logs too.<\/p>\n<p><strong>Verify it worked.<\/strong> Load the affected URL in a private window. It should reach its destination after one redirect. Check a handful of other URLs as well, in case the same wildcard pattern was used more than once. If the whole site still loops, move to Step 7.<\/p>\n<h3>Step 7: Rebuild a Clean .htaccess File<\/h3>\n<p>This step fixes conflicting or duplicated rules on disk, the fifth cause above. Plugins, security tools and hosting panels all write into .htaccess. Over time it collects rules that contradict each other, and those rules keep working even with every plugin disabled.<\/p>\n<p><strong>Confirm this is your cause first.<\/strong> Connect by FTP and turn on hidden files, which in FileZilla is under the Server menu as Force showing hidden files. Download .htaccess from the same folder as index.php. Open it and look for three things. Look for more than one block marked # BEGIN WordPress. Look for two rules that disagree, such as one adding www and another removing it. Look for any rule forcing https if you also have an SSL plugin or a host level redirect doing the same job.<\/p>\n<p><strong>Back up the file first, because this is a live change.<\/strong> Save a copy to your computer. This file can hold security rules and custom redirects you still need. If your site earns money, make this change on a staging copy first. Our guide on <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-backup-wordpress-using-updraftplus\/\">how to back up WordPress using UpdraftPlus<\/a> covers a free way to protect yourself.<\/p>\n<p><strong>Make the change.<\/strong> Rename the live file to htaccess-old so it stops being read. Then create a new .htaccess containing only the standard WordPress block, exactly as WordPress generates it:<\/p>\n<pre># BEGIN WordPress\r\n&lt;IfModule mod_rewrite.c&gt;\r\nRewriteEngine On\r\nRewriteBase \/\r\nRewriteRule ^index\\.php$ - [L]\r\nRewriteCond %{REQUEST_FILENAME} !-f\r\nRewriteCond %{REQUEST_FILENAME} !-d\r\nRewriteRule . \/index.php [L]\r\n&lt;\/IfModule&gt;\r\n# END WordPress<\/pre>\n<p>Then open Settings and then Permalinks and press Save Changes without altering anything. That makes WordPress confirm its own rules. Our guide on <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-set-up-and-fix-permalinks-in-wordpress\/\">how to set up and fix permalinks in WordPress<\/a> explains that screen in more detail. If WordPress cannot write the file, see our guide on <a href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-file-and-folder-permissions\/\">WordPress file and folder permission errors<\/a>.<\/p>\n<p><strong>Verify it worked.<\/strong> Load the homepage and an inner post in a private window. If both load, add your custom rules back from the old file one at a time, testing after each. If you get a 404 on inner pages instead of a loop, see our guide on <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-fix-a-404-error-in-wordpress\/\">how to fix a 404 error in WordPress<\/a>. If the loop survives a clean file, go to Step 8.<\/p>\n<h3>Step 8: Set Cloudflare Encryption to Full or Higher<\/h3>\n<p>This step fixes the Flexible SSL loop, the third cause above. On Flexible, Cloudflare takes a secure request from the visitor and sends plain http to your server. If your server then forces http back to https, the two bounce the request between them until the browser quits.<\/p>\n<p><strong>Confirm this is your cause first.<\/strong> Check whether your domain runs through Cloudflare or a similar proxy. Then log in to Cloudflare, open the SSL\/TLS section and read the encryption mode. If it says Flexible, and your site or host also forces https, you have found it. A further clue is that the loop appeared within minutes of pointing your domain at Cloudflare.<\/p>\n<p><strong>Make the change.<\/strong> Cloudflare&#8217;s own documentation gives two options. Either remove the https redirects from your server, or raise the encryption mode to Full or higher. Raising the mode is the better choice for almost every site. Full or Strict requires a valid certificate installed on your own server, so confirm you have one first. Most hosts now provide a free Let&#8217;s Encrypt certificate you can turn on in one click.<\/p>\n<p><strong>If you want Cloudflare to handle the https redirect for you, use its own setting.<\/strong> Turn on Always Use HTTPS in the SSL\/TLS area and remove the matching rule from your server. That keeps the redirect in one place, which is the whole point.<\/p>\n<p><strong>Verify it worked.<\/strong> Wait a minute for the change to apply, then purge the Cloudflare cache. Load the http version of your homepage in a private window. It should redirect once to https and stay there. If only wp-admin still loops, move to Step 9.<\/p>\n<h3>Step 9: Tell WordPress About Your Reverse Proxy<\/h3>\n<p>This step fixes the proxy loop, the fourth cause above. A proxy or load balancer handles the certificate and then talks to WordPress over plain http. WordPress sees http, decides the visitor needs https, and the proxy hands it another http request. WordPress documentation states plainly that this produces an infinite redirect loop.<\/p>\n<p><strong>Confirm this is your cause first.<\/strong> This cause has a very clear signature. The public site works but wp-admin or wp-login.php loops. Open wp-config.php and look for a line defining FORCE_SSL_ADMIN as true. Then check whether your site sits behind a proxy, a load balancer or a platform that terminates the certificate for you. If both are true, this is your cause.<\/p>\n<p><strong>Back up wp-config.php before you edit it.<\/strong> It holds your database credentials, so a mistake takes the site down. Download a copy and edit it in a plain text editor.<\/p>\n<p><strong>Make the change.<\/strong> Teach WordPress to read the header your proxy sends. The official WordPress snippet checks for https inside the forwarded protocol header and sets the secure flag itself. Place it in wp-config.php above the line that says stop editing:<\/p>\n<pre>define( 'FORCE_SSL_ADMIN', true );\r\n\/\/ HTTP_X_FORWARDED_PROTO may hold a list such as http,https\r\nif ( strpos( $_SERVER['HTTP_X_FORWARDED_PROTO'], 'https' ) !== false ) {\r\n    $_SERVER['HTTPS'] = 'on';\r\n}<\/pre>\n<p>This only works if the proxy actually sends that header. On Nginx, the proxy block needs a line setting X-Forwarded-Proto to the current scheme. If you do not control the proxy, ask your host to confirm the header is being passed.<\/p>\n<p><strong>Verify it worked.<\/strong> Upload the file and open wp-login.php in a private window. You should reach the login form and be able to sign in. Then click around the dashboard to confirm it stays on https. If you now get a blank screen instead, a PHP error has been introduced, so restore your backup and check the snippet. Our guide on <a href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-white-screen-of-death\/\">the WordPress white screen of death<\/a> explains how to read the error.<\/p>\n<h2>Best Practices to Prevent the ERR_TOO_MANY_REDIRECTS Error in WordPress<\/h2>\n<p>Each habit below removes one of the causes you just read about. Together they keep your redirects predictable.<\/p>\n<p><strong>Force https in one place only.<\/strong> Pick your host, your server rules, your CDN or a plugin. Never two. This single rule prevents the plugin conflicts in Step 5 and the Cloudflare loop in Step 8, which between them cause most of these errors.<\/p>\n<p><strong>Choose www or non-www once and stay with it.<\/strong> Write the decision down with your site notes. Then make sure both WordPress address settings use it. Mixed choices are what start the loop in Step 3.<\/p>\n<p><strong>Check both address settings after every move.<\/strong> Add it to your migration checklist, along with a search for WP_HOME and WP_SITEURL in wp-config.php. Staging tools very often leave one of those behind.<\/p>\n<p><strong>Keep .htaccess clean and commented.<\/strong> Add a short note above any rule you add by hand, saying what it does and when you added it. Review the file twice a year and delete rules for plugins you no longer run.<\/p>\n<p><strong>Point redirects straight at the final URL.<\/strong> Avoid chains, and never use a wildcard whose destination sits inside its own source folder. Review your redirect list whenever you change a slug.<\/p>\n<p><strong>Install a real certificate on your own server.<\/strong> That lets you run Cloudflare on Full or Strict instead of Flexible. Free certificates are available from most hosts in a single click.<\/p>\n<p><strong>Test in a private window after any redirect change.<\/strong> Your normal browser caches permanent redirects and will lie to you. A private window gives you the truth.<\/p>\n<p><strong>Purge every cache layer after a redirect change.<\/strong> Clear the plugin cache, the host cache and the CDN cache. Otherwise a fixed site keeps serving the broken answer.<\/p>\n<p><strong>Make SSL and redirect changes on staging first.<\/strong> These settings can lock you out of your own dashboard. A staging copy lets you prove the change before it reaches visitors.<\/p>\n<p><strong>Keep a current backup before touching wp-config.php.<\/strong> One stray character in that file takes the whole site offline, and it is the file this error most often requires you to edit.<\/p>\n<h2>Conclusion<\/h2>\n<p>A redirect loop looks dramatic but it is one of the safer WordPress errors. Nothing is lost or broken. Two instructions simply disagree, and the browser refuses to keep bouncing between them.<\/p>\n<p>The signs tell you a lot before you change anything. A flickering address bar, a site that works in incognito, or a loop that only hits the dashboard each point to a different cause. Note which pages fail and when the loop started.<\/p>\n<p>The causes are a short list. Mismatched address settings, an SSL plugin fighting your server, Cloudflare on Flexible, a proxy hiding the real protocol, conflicting .htaccess rules, a looping redirect rule, stale cookies, a stale cache, and a hard-coded address in wp-config.php.<\/p>\n<p>The fix follows the same order every time. Clear your cookies. Purge every cache. Match the two address settings. Remove any override in wp-config.php. Switch off SSL and security plugins one by one. Audit your redirect rules. Rebuild .htaccess. Raise Cloudflare to Full. Then teach WordPress about your proxy.<\/p>\n<p>Prevention comes down to one idea. Force https in exactly one place, choose www or non-www once, and check both settings after every move. Keep .htaccess tidy, test in a private window, and purge your caches afterwards.<\/p>\n<p>If the loop turns out to be a file that WordPress cannot write, our guide on <a href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-file-and-folder-permissions\/\">how to fix WordPress file and folder permission errors<\/a> covers that side of the problem. For the authoritative detail, see the <a href=\"https:\/\/developer.wordpress.org\/advanced-administration\/security\/https\/\" target=\"_blank\" rel=\"noopener\">WordPress HTTPS documentation<\/a>, the <a href=\"https:\/\/developer.wordpress.org\/advanced-administration\/upgrade\/migrating\/\" target=\"_blank\" rel=\"noopener\">WordPress guide to changing the site URL<\/a>, and <a href=\"https:\/\/developers.cloudflare.com\/ssl\/troubleshooting\/too-many-redirects\/\" target=\"_blank\" rel=\"noopener\">Cloudflare&#8217;s own page on too many redirects<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction You type your own address into the browser and nothing loads. Instead you see [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4396,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[287],"tags":[556,553,555,554,343],"class_list":["post-4387","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress-error","tag-cloudflare","tag-err_too_many_redirects","tag-ssl","tag-wordpress-redirect-loop","tag-wordpress-troubleshooting"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to Fix ERR_TOO_MANY_REDIRECTS in WordPress Fast<\/title>\n<meta name=\"description\" content=\"Seeing ERR_TOO_MANY_REDIRECTS in WordPress? Learn the 9 causes of a redirect loop and clear each one safely, step by step, starting with the quickest.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress Fast\" \/>\n<meta property=\"og:description\" content=\"Seeing ERR_TOO_MANY_REDIRECTS in WordPress? Learn the 9 causes of a redirect loop and clear each one safely, step by step, starting with the quickest.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/\" \/>\n<meta property=\"og:site_name\" content=\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting &amp; Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-14T06:33:01+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-14T06:43:50+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/ERR_TOO_MANY_REDIRECTS.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"1440\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"James\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"James\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"21 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/\"},\"author\":{\"name\":\"James\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/person\\\/42bec463c3b7b14c88f4c787a7009730\"},\"headline\":\"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress\",\"datePublished\":\"2026-10-14T06:33:01+00:00\",\"dateModified\":\"2026-10-14T06:43:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/\"},\"wordCount\":4643,\"publisher\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/ERR_TOO_MANY_REDIRECTS.png\",\"keywords\":[\"Cloudflare\",\"ERR_TOO_MANY_REDIRECTS\",\"SSL\",\"WordPress redirect loop\",\"WordPress Troubleshooting\"],\"articleSection\":[\"WordPress Error\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/\",\"name\":\"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress Fast\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/ERR_TOO_MANY_REDIRECTS.png\",\"datePublished\":\"2026-10-14T06:33:01+00:00\",\"dateModified\":\"2026-10-14T06:43:50+00:00\",\"description\":\"Seeing ERR_TOO_MANY_REDIRECTS in WordPress? Learn the 9 causes of a redirect loop and clear each one safely, step by step, starting with the quickest.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/ERR_TOO_MANY_REDIRECTS.png\",\"contentUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/ERR_TOO_MANY_REDIRECTS.png\",\"width\":2560,\"height\":1440,\"caption\":\"ERR_TOO_MANY_REDIRECTS\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-err-too-many-redirects-wordpress\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/\",\"name\":\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#organization\",\"name\":\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/logo__1_-removebg-preview.png\",\"contentUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/logo__1_-removebg-preview.png\",\"width\":600,\"height\":226,\"caption\":\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/person\\\/42bec463c3b7b14c88f4c787a7009730\",\"name\":\"James\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g\",\"caption\":\"James\"},\"description\":\"James is an experienced WordPress and WooCommerce specialist with over 10 years of practical experience. At WPChatSupport, he creates clear guides that help website owners fix WordPress issues, improve speed, secure their sites, and manage WooCommerce stores with confidence. His expertise includes store setup, plugin configuration, theme customization, payment gateway integration, and website troubleshooting. Through simple and helpful content, James supports users in solving technical problems and following best practices for online business growth.\",\"sameAs\":[\"https:\\\/\\\/blog.wpchatsupport.com\"],\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/author\\\/24x7wpsupport\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress Fast","description":"Seeing ERR_TOO_MANY_REDIRECTS in WordPress? Learn the 9 causes of a redirect loop and clear each one safely, step by step, starting with the quickest.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/","og_locale":"en_US","og_type":"article","og_title":"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress Fast","og_description":"Seeing ERR_TOO_MANY_REDIRECTS in WordPress? Learn the 9 causes of a redirect loop and clear each one safely, step by step, starting with the quickest.","og_url":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/","og_site_name":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting &amp; Tutorials","article_published_time":"2026-10-14T06:33:01+00:00","article_modified_time":"2026-10-14T06:43:50+00:00","og_image":[{"width":2560,"height":1440,"url":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/ERR_TOO_MANY_REDIRECTS.png","type":"image\/png"}],"author":"James","twitter_card":"summary_large_image","twitter_misc":{"Written by":"James","Est. reading time":"21 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/#article","isPartOf":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/"},"author":{"name":"James","@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/person\/42bec463c3b7b14c88f4c787a7009730"},"headline":"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress","datePublished":"2026-10-14T06:33:01+00:00","dateModified":"2026-10-14T06:43:50+00:00","mainEntityOfPage":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/"},"wordCount":4643,"publisher":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/#primaryimage"},"thumbnailUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/ERR_TOO_MANY_REDIRECTS.png","keywords":["Cloudflare","ERR_TOO_MANY_REDIRECTS","SSL","WordPress redirect loop","WordPress Troubleshooting"],"articleSection":["WordPress Error"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/","url":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/","name":"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress Fast","isPartOf":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/#primaryimage"},"image":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/#primaryimage"},"thumbnailUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/ERR_TOO_MANY_REDIRECTS.png","datePublished":"2026-10-14T06:33:01+00:00","dateModified":"2026-10-14T06:43:50+00:00","description":"Seeing ERR_TOO_MANY_REDIRECTS in WordPress? Learn the 9 causes of a redirect loop and clear each one safely, step by step, starting with the quickest.","breadcrumb":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/#primaryimage","url":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/ERR_TOO_MANY_REDIRECTS.png","contentUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/ERR_TOO_MANY_REDIRECTS.png","width":2560,"height":1440,"caption":"ERR_TOO_MANY_REDIRECTS"},{"@type":"BreadcrumbList","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.wpchatsupport.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to Fix ERR_TOO_MANY_REDIRECTS in WordPress"}]},{"@type":"WebSite","@id":"https:\/\/www.wpchatsupport.com\/blog\/#website","url":"https:\/\/www.wpchatsupport.com\/blog\/","name":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials","description":"","publisher":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.wpchatsupport.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.wpchatsupport.com\/blog\/#organization","name":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials","url":"https:\/\/www.wpchatsupport.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2025\/07\/logo__1_-removebg-preview.png","contentUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2025\/07\/logo__1_-removebg-preview.png","width":600,"height":226,"caption":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials"},"image":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/person\/42bec463c3b7b14c88f4c787a7009730","name":"James","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g","caption":"James"},"description":"James is an experienced WordPress and WooCommerce specialist with over 10 years of practical experience. At WPChatSupport, he creates clear guides that help website owners fix WordPress issues, improve speed, secure their sites, and manage WooCommerce stores with confidence. His expertise includes store setup, plugin configuration, theme customization, payment gateway integration, and website troubleshooting. Through simple and helpful content, James supports users in solving technical problems and following best practices for online business growth.","sameAs":["https:\/\/blog.wpchatsupport.com"],"url":"https:\/\/www.wpchatsupport.com\/blog\/author\/24x7wpsupport\/"}]}},"_links":{"self":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts\/4387","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/comments?post=4387"}],"version-history":[{"count":2,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts\/4387\/revisions"}],"predecessor-version":[{"id":4395,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts\/4387\/revisions\/4395"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/media\/4396"}],"wp:attachment":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/media?parent=4387"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/categories?post=4387"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/tags?post=4387"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}