[ad_1]
Google’s Martin Splitt answered a query about how Googlebot responds to a pre-render meta tag that has the worth of 404 web page not discovered. It’s an excellent query as a result of that is the sort of meta tag, a non-standard meta aspect, isn’t usually encountered so it’s good to know what to do when one thing like this comes up.
The particular person asking the query wished to find out about how Google would possibly reply to a meta tag within the head part that has the title “prerender-status-code” and a worth of “404” which signifies that the requested web page is just not discovered.
The query was requested by an individual named Martin and Martin Splitt of Google is the one who answered it.
That is the query :
“Martin is asking: What does Googlebot do when it finds <meta title=”prerender-status-code” content material=”404″> ?”
Martin Splitt answered:
“Nicely Martin, that’s simple to say, Googlebot at the moment ignores that standing code.
I assume that is coming from a single web page software that’s client-side rendered and also you wish to keep away from soft-404s, in that case take into account including <meta title=”robots” content material=”noindex”> or redirect to a web page the place the server responds with the 404 standing code.
For extra info on that see our documentation at builders.google.com/search.”
What’s Prerender-Standing-Code?
The prerender-status-code meta aspect (typically known as meta tag) is just not an official meta tag and there’s no documentation on it on the Worldwide Net Consortium (W3C.org), the place the official HTML requirements are created.
That is extra of a proprietary or non-standard meta aspect. Non-standard meta components are are usually not a part of the official W3C HTML specs. Some non-standard meta components are browser-specific or are created for particular functions. Consequently, they will not be supported by completely different browsers or by search engines like google. and their conduct will not be constant throughout completely different browsers
The prerender-status-code meta aspect is an instance of a non-standard meta aspect that additionally occurs to not be supported by Google.
One other non-standard meta aspect that’s not supported by Google is the meta key phrases aspect. There is no such thing as a reference to it on the W3C.org and it was by no means part of the official HTML requirements. It was a meta aspect that was invented by search engines like google within the Nineties.
The X-UA-Appropriate meta aspect is an instance of a browser-specific non-standard meta aspect that’s an outdated meta aspect that was particular to the outdated Web Explorer internet browser.
That is an instance of the X-UA-Appropriate meta aspect:
<meta http-equiv="X-UA-Appropriate" content material="IE=edge">
The takeaway from Martin’s reply concerning the prerender-status-code meta aspect is that many non-standard meta components are usually not supported by Google.
One other takeaway is that not each meta tag is part of the official HTML requirements which will be discovered on the World Huge Net Consortium web site (W3C.org). These non-official meta components are known as non-standard meta components.
Extra info will be discovered at Google’s assist web page about supported meta tags, which was final up to date on December 1, 2023.
Meta tags and attributes that Google helps
Take heed to the Google Workplace hours video on the 3:46 minute mark:
Featured Picture by Shutterstock/Jaaak
[ad_2]
