"Blocked due to other 4xx issue" in Search Console: 11 pages, all 200, last crawl 6 weeks ago
Search Console showed 11 pages of one of my sites under "Blocked due to other 4xx issue". I assumed something on the site was still broken. Nothing was. The 4xx happened once, in early October, and Google simply had not
Search Console showed 11 pages of one of my sites under "Blocked due to other 4xx issue". I assumed something on the site was still broken. Nothing was. The 4xx happened once, in early October, and Google simply had not come back.
Here is what I found, the numbers, and the one button that matters.
The report
The site is vuetelemetry.com, a Next.js site about Vue, Nuxt and front-end performance, in 6 languages. The Page indexing report on 19 November 2026:
| Reason | Pages |
|---|---|
| Discovered, currently not indexed | 266 |
| Blocked due to other 4xx issue | 11 |
| Crawled, currently not indexed | 9 |
| Page with redirect | 2 |
| Indexed | 44 |
The sitemap itself was fine: 330 URLs submitted, last read 17 November, status Success.
The 4xx group appeared around 22 September with 13 pages, and slowly shrank to 11. "Other 4xx" is what is left once Google has split out 401, 403 and 404 into their own reasons.
What URL Inspection said
For the page I cared most about, the Vue/Nuxt hosting comparison:
- Last crawl: 7 Oct 2026, 01:27, Googlebot smartphone
- Crawl allowed: Yes
- Page fetch: Failed: Blocked due to other 4xx issue
- Indexing allowed: N/A
- Sitemaps: "Temporary processing error"
So the only fetch Google had of that page was a failed one, six weeks old.
What the server returns today
I requested the 10 page URLs of the group with a Googlebot user agent:
UA='Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)'
for u in articles/best-hosting-vue-nuxt-app articles/what-is-a-single-page-application \
de/articles/was-ist-eine-rest-api es/projects/vue fr/articles/meilleur-hebergement-app-vue-nuxt; do
echo "$(curl -s -o /dev/null -w '%{http_code}' -A "$UA" https://vuetelemetry.com/$u) $u"
done
All 200. The robots.txt only disallows /go/. The middleware only runs on / (language redirect for first visits) and never touches article URLs.
I do not have request logs from late September, so I cannot say which code was served or why. What I can say is that the error was transient and the fix had already happened by itself, weeks ago.
Why it stays red
On a small site Google does not recrawl a URL quickly after a failed fetch. The last crawl dates in the report are 3, 5 and 7 October. Nothing since. The report keeps showing the old failure because there is no newer fetch to replace it.
The same low crawl rate explains the 266 "Discovered, currently not indexed": Google knows the URLs from the sitemap and internal links but has not spent the crawl on them. One example: the hosting picker tool is in the sitemap and linked from the homepage, and URL Inspection still answers "URL is unknown to Google", no referring sitemap, no referring page.
The button
In the Page indexing report, open the reason, then click Validate fix. Google queues every URL of the group for a recrawl and tracks it. Mine shows "Validation: Started, 19/11/2026".
Request indexing works too, but it is limited to about ten URLs a day per account. Validate fix covers the whole group in one click.
Checklist for "Blocked due to other 4xx issue"
- Read the last crawl date in URL Inspection. If it is weeks old, the report describes the past.
- Fetch every URL of the group yourself, with a Googlebot user agent, and check for 200.
- Check robots.txt and any middleware or edge rule that could answer 4xx to bots (rate limits, geo or bot filters).
- If all are 200: Validate fix, then Request indexing for the one or two pages that matter most.
- If not: fix first, validate after. A validation that fails restarts the wait.
I will update this post with the validation result.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.