Google confirmed final week that it’s engaged on a repair with SXG, signed exchanges, and never working appropriately in search. Particularly, Google serves them in Google Search as regular HTML pages, not as signed exchanges. Google’s John Mueller stated this isn’t inflicting any points with visitors from Google Search to SXG however moderately, Google will not be pre-fetching, caching, and serving these pages quicker than a standard HTML web page.
This primary was reported by way of Richard Hearne after which Omer Rachamim confirmed the problem on his finish too:
Any information on this one? I am experiencing the identical factor. Nothing comes up on numerous checks – it appears Google is not pre-fetching SXG outcomes.
— Omer Rachamim (@Omerach) December 21, 2022
John Mueller of Google then confirmed the problem saying “this can be a recognized bug and we’re engaged on rolling out a repair (doubtless 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 had been non-SXG.”
I came upon extra — this can be a recognized bug and we’re engaged on rolling out a repair (doubtless 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 had been non-SXG.
— John Mueller is usually not right here 🐀 (@JohnMu) December 22, 2022
Some reported visitors drops however possibly that isn’t the case, possibly it’s simply how the reporting works? Omer stated he didn’t discover any visitors points:
From my drilldown I can affirm the hyperlinks are exhibiting and getting clicks. We recognized the bug once we investigated the hyperlinks and noticed they result in common html and never sxg, like John stated
— Omer Rachamim (@Omerach) December 23, 2022
Earlier this yr, Google Search introduced signed exchanges assist to desktop – it went stay in July. Signed exchanges (SXG) permit Google Search to prefetch your content material whereas preserving the person’s privateness. In follow, which means that each AMP and non-AMP outcomes proven on Google Search could prefetch a couple of key sources (comparable to HTML, JavaScript, CSS, photos, 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.
