{"id":19021425,"date":"2026-09-16T10:00:53","date_gmt":"2026-09-16T10:00:53","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/root-url-not-excluded\/"},"modified":"2026-09-16T10:00:53","modified_gmt":"2026-09-16T10:00:53","slug":"root-url-not-excluded","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/root-url-not-excluded\/","title":{"rendered":"Root URL not excluded"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">We are currently on the free version of Super Page Cache, 5.3.2, running on WordPress 7.0.3.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The website is multi-lingual and uses the Polylang plugin. The plugin is configured as following:<\/p>\n\n\n\n<ul>\n<li><strong>Detect browser language<\/strong> setting is enabled<\/li>\n\n\n\n<li><strong>The language is set from the directory name in pretty permalinks<\/strong> setting is enabled<\/li>\n\n\n\n<li><strong>The front page URL contains the language code instead of the page name or page ID<\/strong> setting is enabled<\/li>\n\n\n\n<li><strong>Hide URL language information for default language<\/strong> setting is <em>disabled<\/em><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">So if the the website&#8217;s root URL (domain.com) is requested, Polylang detects the browser language and redirects to a matching language (e.g. domain.com\/fr) or the default language (e.g. domain.com\/en) if no match is found. This setup is working perfectly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We set up Super Page Cache with default settings when the website went live. So far, so great.<br \/><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, a few weeks in, we noticed that the root URL suddenly returned a 404. error page for anonymous visitors.<br \/>We then added &#8220;\/&#8221; in the Prevent the following URIs from being cached setting in the Super Page Cache plugin and purged the cache. Problem solved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, today the root URL again returned a 404. We disabled Super Page Cache and the problem was solved. We then re-enabled the plugin and it is working again as intended.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Current state:<\/p>\n\n\n\n<ul>\n<li>After some back and forth with ChatGPT, we decided to upgrade Super Page Cache from 5.3.2 to 5.3.5. See the AI exchange here: https:\/\/chatgpt.com\/share\/6aaa672d-6bc4-83eb-871a-e4f8d7038110<\/li>\n\n\n\n<li>And we have implemented an uptime monitor that specifically checks for 404 status on the website homepage.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">But of course we are very interested to see if we are overlooking anything, we stumbled onto a bug and \/ or if we can safely rely on Super Page cache in the future. Any insights or pointers are highly appreciated. Many thanks in advance!<\/p>\n","protected":false},"template":"","class_list":["post-19021425","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19021425","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19021425\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=19021425"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}