Google confirmed final week that it’s engaged on a repair with SXG, signed exchanges, and never working accurately in search. Particularly, Google serves them in Google Search as regular HTML pages, not as signed exchanges. Google’s John Mueller mentioned this isn’t inflicting any points with site visitors from Google Search to SXG however somewhat, Google is just not pre-fetching, caching, and serving these pages quicker than a traditional HTML web page.
This primary was reported through Richard Hearne after which Omer Rachamim confirmed the difficulty on his finish too:
Any information on this one? I am experiencing the identical factor. Nothing comes up on varied exams – it appears Google is not pre-fetching SXG outcomes.
— Omer Rachamim (@Omerach) December 21, 2022
John Mueller of Google then confirmed the difficulty saying “this can be a identified bug and we’re engaged on rolling out a repair (possible after the vacations although); within the meantime you don’t want to fret – your webpages will nonetheless present up on Search usually as in the event that they have been non-SXG.”
I discovered extra — this can be a identified bug and we’re engaged on rolling out a repair (possible after the vacations although); within the meantime you don’t want to fret – your webpages will nonetheless present up on Search usually as in the event that they have been non-SXG.
— John Mueller is usually not right here 🐀 (@JohnMu) December 22, 2022
Some reported site visitors drops however possibly that’s not the case, possibly it’s simply how the reporting works? Omer mentioned he didn’t discover any site visitors points:
From my drilldown I can verify the hyperlinks are exhibiting and getting clicks. We recognized the bug after we investigated the hyperlinks and noticed they result in common html and never sxg, like John mentioned
— Omer Rachamim (@Omerach) December 23, 2022
Earlier this 12 months, Google Search introduced signed exchanges assist to desktop – it went dwell in July. Signed exchanges (SXG) permit Google Search to prefetch your content material whereas preserving the consumer’s privateness. In observe, which means that each AMP and non-AMP outcomes proven on Google Search might prefetch a couple of key assets (corresponding to HTML, JavaScript, CSS, photographs, or fonts) in a privacy-preserving method, if the related web site helps SXG.
A small correction – the web page that is being served is the common HTML, not the SXG copy of the HTML.
— Omer Rachamim (@Omerach) December 26, 2022
Discussion board dialogue at Twitter.
