How to start work with signed exchange in Google

Signed exchanges (SXG) allow Google to pre -upload the content of your site, while maintaining the customer confidentiality of the user. This means that both AMP and non-amp, which are displayed in Google, can pre-load several key resources (for example, JavaScript, CSS, images or fonts) if the corresponding site supports SXG.

When the user ultimately presses the result, the web page begins to load much faster, since key resources are already available, which improves the user's experience. This can lead to a reduction in time to maximum content visualization (LCP) for your content, which in turn can improve the general assessment of the page quality.

Implementation of SXG on your website for Google

To implement the SXG, follow the detailed guidance on Web.dev. After implementing, follow the LCP optimization instructions using signed exchange in Google.

For AMP pages, follow the instructions on the amp.dev website.

Additional requirements for Google Pois

Google uses SXG cache to pre -load your site content. Google can repeatedly show these cchelled SXGs.

To make sure that the current content is displayed in Google, correctly set the values of the SXG validity period. As a guideline, make sure that the date of expiration is less than the following two values:

• Cached time determined by your HTTP heads
• 1 day in advance if the content contains JavaScript or built -in JavaScript; In other cases - 7 days ahead

To make sure that content is correctly displayed on various devices, follow the following:

• Move personalized content, for example, shopping baskets, in lazily uploaded elements that are outside the SXG. Or add the Vary: Cookie headline so that SXG with this heading shows only users without cookies on your site.
• Build pages with adaptive design. Alternatively, provide different URLs for mobile and desktop versions of pages, or annotate the pages to indicate that they are not adaptive using the Supported-Media tag in the element. For example, add the following tag:

How to monitor signed exchanges on your site in Google

To monitor the SXG errors, use the AMP state report to Search Console.

If the Google Botto cannot steer the SXG, it can be transferred to the URL without the use of Application/ Signed-Exchange; V = B3 in the Accept title to get the text/ version.

SXG cache debugging in Google

To determine whether the cache complies with the SXG requirements, use the SXG Validator extension for Chrome.

Or request a cache in Google directly. For example, if SXG URL is https://signed-exchange-testing.dev/sxgs/valid., The corresponding URL cache will look like this:

HTTPS: // Syngnd-Chicchang--testing-girl. Webpkgsache.K.M.K.M.K.

The subdomain calculation algorithm is the same as for AMP Cache, however, the infix/doc//////////line will differ.

If the answer is SXG, this means that the response from the initial server meets the requirements of Google for caching SXG. If not, then it will contain HTTP heading, which will indicate the cause.

• If there is a Warning headline, this indicates a mistake that prevented the SXG from comply with the requirements of the cache.
• If there is a location title, this means that the contents have not yet been loaded into the cache. This is not a mistake in the SXG.

Regardless of the response, the cache initiates a request to the source URL to update the copy. This request will occur depending on many factors, including the speed with which Google Bott can scan your site.

Google does not cach SXG longer than the SXG signature period or the expiration date of the Unsigned SXG response headlines.

How to track caching errors for AMP pages

Use the URL Inspection Tool for debugging caching errors.

How to stay aware of the changes in signed exchanges for your site in Google

Subscribe to Webpackaging-Announc newsletter to be aware of the following changes:

• Changes in the SXG Google cache, which include new opportunities or discover old opportunities.
• The main changes in the SXG tools, such as Web Packager, the Nginx SXG and Libsxg module.

If you have questions about signed exchange for your Google website, visit the Search Central assistance community.

To get a SEO consultation for your site, you can contact the SEO.Computer SEO companis by email: info@seo.computer, WhatsApp: +79202044461.

ID: 74