Contact UsWDN News & more...

Google: Sometimes Bot Protection Services Serve Noindex Directive

Google Robot Blocked

Did that most incessantly those bot security services will encourage Google and various serps noindex directives? Google’s John Mueller said this on X, saying, “Steadily there’s bot-security (or a login, interstitial, etc) triggering that has a noindex on it.”

He also added that it’d be better for them to encourage 503 server popularity codes. “Better could be to make exhaust of 503 for server-side blocks cherish bot-security,” he wrote.

In the pause, the actual person he spoke back to used to be having a undeniable order inflicting the noindex, it used to be now now not bot security. He said it used to be “some shenanigans with NextJS doing consumer side rendering as a replace of server rendering.” “The HTML had a noindex trace, which used to be removed after rendering on the browser. The HTML proven on GSC is the one AFTER JavaScript rendering, which is why I couldn’t salvage it and plan it used to be a GSC trojan horse,” he added.

This used to be the error he used to be seeing:

Gsc Noindex Shot

Listed below are those posts:

Dialogue board discussion at X.