"Blocked due to other 4xx issue" in Search Console: what it means
By Michael Broadbridge. Last checked 16 November 2026 on Google Search Console.
Short answer
It means Googlebot requested a URL and got a 4xx error code that is not 401, 403 or 404, such as 400 or 422. Open the reason in the Page indexing report and inspect the example URLs. If they are not real pages, such as a search endpoint, leave them. If real pages are listed, fix the server response.
Symptoms
You may see this message:
Blocked due to other 4xx issue
- The Page indexing report lists Blocked due to other 4xx issue under Why pages aren't indexed.
- The example URLs are addresses you do not recognise as pages, such as /search/suggest on a Shopify store.
- The example URLs include products, posts or pages you expect to be in Google.
- The count went up after a firewall, bot protection service or security plugin was added or changed.
Causes, most likely first
An address that is not a page
Themes, plugins and apps call addresses that return data or page fragments for scripts, not pages for people. Google can find these addresses in the site's code. Requested without the details they expect, they return an error code, which Google reports here.
A firewall or bot protection refusing Googlebot
Security services, hosting firewalls and rate limits can answer Googlebot with a 4xx code instead of the page. Google treats a 429 (too many requests) as a sign that the server is overloaded.
Malformed links
A link with stray characters or a broken query string can make the server reply with 400 (bad request). Google follows the link and reports the error.
A server or app setting on real pages
A plugin, app or server rule can return a 4xx code for pages that work in a browser, for example when a page needs a parameter Google does not send.
How to fix it
Find which URLs are affected
Google's description of this reason is that the server returned a 4xx error not covered by any other reason in the report. 401, 403 and 404 each have their own reason, so anything listed here received a different 4xx code.
- Open the Page indexing report in Search Console.
- In the Why pages aren't indexed table, check that the Source column says Website, then click Blocked due to other 4xx issue.
- Read through the example URLs and sort them into real pages and addresses that are not pages.
- Change the filter above the chart from All known pages to All submitted pages. Any URL still listed is in your sitemap.
- Click the inspect icon next to a URL, or paste it into the URL Inspection tool. The Discovery section shows how Google found it, including any referring page and sitemap.
- Click Test live URL. The tool fetches the URL in real time, so you can see whether Google still gets an error now.
One Shopify store we looked at had a single URL under this reason: /search/suggest. It was not in the sitemap and needed no fix.
If the URLs are not pages, leave them
On Shopify, /search/suggest is the address the theme uses for predictive search, the suggestions that appear as someone types in the search box. Shopify's Predictive Search API documentation says it expects a search query (q) and that errors in the request parameters return a 422 status code. Themes such as Dawn include the address in their JavaScript, which is how Google finds it. Requested on its own, with no query, it returns 422.
- Google does not index URLs that return a 4xx code and does not use their content, so there is nothing to lose.
- Google says 4xx codes other than 429 have no effect on crawl rate, and it crawls such URLs less often over time.
- Do not click Validate fix. The address is meant to return an error when requested without its parameters, so validation would fail.
If the list keeps growing with addresses of this kind and you want them out of the report, block them in robots.txt. Google then lists them as blocked by robots.txt instead, which is also harmless for addresses that are not pages.
- On Shopify, open your themes.Menu:
Online Store > Themes - Click the three dot button on the live theme and choose Edit code.
- Click Add a new template, select robots and click Create template.
- Add a rule for the address only, following Shopify's Customize robots.txt.liquid guide on shopify.dev, and save.
Shopify describes editing robots.txt.liquid as an unsupported customisation that its support team cannot help with, and warns that incorrect use can result in loss of all traffic. Block only the exact address, never /search or the whole site.
If real pages are listed, fix the response
- A firewall, bot protection or security plugin is blocking Google. Check its logs for blocked requests from Googlebot and allow verified Google crawlers. Google publishes how to check that a request really comes from Googlebot, so you do not have to trust the user agent alone.
- A rate limit returns 429 to Google. Raise the limit for verified Google crawlers. If the server genuinely cannot cope, follow Google's guidance on reducing crawl rate. Google says not to use 401 or 403 codes to limit crawling.
- A page has moved. Add a permanent (301) redirect from the old address to the new one, which is what Google recommends for moved pages.
- A page was removed on purpose with no replacement. Leave it. Google removes URLs that return 4xx codes from its index over time.
- Links or the sitemap point at addresses that return errors. Correct the links and remove those addresses from the sitemap, so it only lists pages you want in Google.
Tell Google you have fixed it
- Fix every real page listed under the reason first, and run Test live URL on a few to confirm Google now gets the page.
- Open the details page for the reason and click Validate fix.
- Do not click Validate fix again until validation has passed or failed. Google says it typically takes up to about two weeks, and sometimes much longer.
- If it shows Failed, check which URLs still have the issue, fix them and start a new validation.
If that didn’t work
The live test works but the report still lists the URL
The report reflects Google's last crawl, not the live site. It updates after Google crawls the URL again, which validation asks it to do.
The page works in your browser but not for Google
Security services can treat crawler traffic differently from visitors. Test live URL uses Google's own crawler, so trust its result over your browser.
The errors come and go
Rate limits and overloaded servers often fail only at busy times. Check the server or firewall logs for the times Google crawled the affected URLs.
When to get help
Stop and get help if real pages are listed and you cannot find what is returning the error, if the cause is a firewall or hosting setting you do not manage, or if you are considering robots.txt changes and are not sure what else a rule would block.
What a developer would check
- The exact status code each listed URL returns to Googlebot, from server or firewall logs.
- Firewall, bot protection and rate limit rules that apply to Google's crawlers.
- Where the theme, plugins or apps reference the listed addresses in their code.
- The robots.txt file, before and after any change, tested against key pages.
Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.
Related questions
- Does Blocked due to other 4xx issue hurt my rankings?
- Not when the URLs are not pages. Google ignores the content of 4xx URLs and the rest of the site is unaffected. It matters only when pages you want in Google are listed, because those pages cannot be indexed until they return the page again.
- Should I block /search/suggest in my Shopify robots.txt?
- It is optional. The URL does no harm in the report. If you do block it, add a rule for that exact address only, and bear in mind Shopify's warning that robots.txt.liquid edits are unsupported.
- Is a 410 treated differently from a 404 by Google?
- Google says all 4xx codes except 429 are treated the same way. The URL is dropped from the index over time and crawled less often, whichever of the two codes it returns.
Written by Michael Broadbridge, Founder of Webgro. First published 19 November 2026. Last checked 16 November 2026 on Google Search Console.