The screenshot image shows that the URL in question is indexed. Why try to index an indexed page?

Check your logs to see if you can pin point that attempted index and see if there is a problem on your end?

I presume this was intended to force an index run on an updated or changed URL?

@not2easy I used it to manually submit an index request after a content update and noticed it was unusable. However, the problem isn't just with manual index requests; tools like live URL testing and rich content testing are also not working. Could this be a penalty?

@tangor Yes, it's still being crawled, but as I mentioned above, I can't use any of the manual indexing, live URL testing, or rich content testing tools; I get errors in all of them. This issue only exists in the www version of my website; there are no problems with the subdomains.

I searched online and found threads about similar problems, but I couldn't find anyone who had found a solution.

Are you redirecting non-www requests to www? I mean if you go to https://example.com does it land on https://www.example.com ?

@not2easy Yes, the non-www version is redirecting to www, but the live URL test isn't working on the non-www version either.

Subdomains are working, such as global.example.com
and de.example.com.

The problem appeared between January 8-9, when the effects of the latest update became apparent.

- I never used the manual indexing tool enough to cause a problem; I used it at a normal level, about 2 or 3 times a week.

Recent site-level changes:

- I removed 40-50 pages from pagination using the URL removal tool.
- I did 301 redirects for 20-30 campaign pages like “discounts” to relevant categories.

I've recently noticed a drop in crawl rates, but I attribute this to the removals mentioned above. I haven't experienced any index loss on my important pages, and the site continues to crawl slowly via the sitemap. The site returns a 200 code, so I don't think there's any problem with the bot's crawl.

However, I cannot use the manual index tool, live URL test, or rich content test tool. Could these tools be crawling with different IPs than the Google bot? Since I use the Shopify platform, could there be a block on my server side for these tools?

Just as a point of elimination: Are you running any browser level script or ad blockers? If so, is the g update page ALLOWED in those, if they exist? Secondly, have you had a recent browser update which might have changed privacy/cookies/etc without your knowledge?

@tangor no i don't run it

Yeah, I have seen this happen when the issue is not real indexing but something broken in Google’s submission system for that specific property. Since crawling still works and subdomains are fine, I would check the exact www property setup, canonicals, preferred version, and whether Search Console sees a mismatch between the inspected URL and the selected property. If pages are still getting crawled and indexed normally, the request tool itself might just be bugging out.