Fetch and Render

The Fetch & Render tool within Google Search Console enables you to test how Google crawls a page on a website, along with how they visually render it on mobile and desktop devices. This enables you to pinpoint and fix any errors which may be occurring. While it is a useful tool, there are some guidelines which should be adhered too, these are covered within our Hangout Notes along with further advice from Google.

Image sitemaps can be useful for sites that use lazy loading

November 1, 2021 Source

When “lazy loading” images on a page in a way that doesn’t include defined image elements, it’s recommended to have back-up in the form of structured data or an image sitemap. That way, Google will know to associate those images with the page even before they’re loaded.

Fetch & Render Tool in GSC Doesn’t Reflect Real Rendering

November 16, 2018 Source

Getting ‘temporarily unreachable’ messages in the Fetch & Render tool doesn’t reflect how Google is rendering content for its index. Google’s rendering service has a longer cutoff time and uses caching.

Scroll Events Shouldn’t be Used in Isolation to Execute Lazy-loading

October 30, 2018 Source

Scroll events aren’t always the best solution because they are expensive, users on desktop may resize their window to get more content which wouldn’t trigger a scroll event, and Google doesn’t scroll. Test lazy-loading is working by using Fetch & Render and Intersection Observer.

Text That’s Hidden by Default During Rendering is Fine For Google

October 2, 2018 Source

Some sites will prevent content from being visible until the page has finished rendering to stop elements from jumping around the screen as they are loaded. This is fine for Google as long as the textual content is in the HTML, but check what Google can see with the mobile-friendly testing tool and Fetch & Render in GSC.

Google’s Cache Isn’t an Accurate View of Googlebot Rendering

July 24, 2018 Source

The Fetch & Render tool in GSC and the Mobile-friendly Test tool show a more accurate view of how Googlebot is able to render a page than Google’s cache view, as this can easily be broken.

GSC Will Still Have the Option to Fetch Desktop Pages After Mobile-first Indexing

June 26, 2018 Source

Google still wants website owners to be able to check how their desktop pages appear even if the content is being taken from mobile for mobile-first indexing, so there will still be an option to fetch both page versions in GSC.

Ensure Google is Shown the Same Title When the Page is Fetched & Rendered

June 12, 2018 Source

If Google is switching the titles between individual URLs, then something with the back-end of the website may be wrong. Google should be able to get the same title when it initially fetches the page as when it is rendered.

Fetch as Google Doesn’t Make Any Changes to the Index

April 3, 2018 Source

Fetch as Google only requests the page so it can’t be used to bring Google’s attention to an updated status code, for example. In order to affect the index you need to use Submit to Index where additional processing will be done.

Remove CSS Stretching Images to Max Viewport to See How Full Page Renders

December 12, 2017 Source

If the CSS sets images to the max viewport this will stretch them and stop you being able to see how the rest of the page is rendering in Fetch as Google. However, this view doesn’t represent what Googlebot is actually rendering.

Related Topics

Crawling Indexing Crawl Budget Crawl Errors Crawl Rate Disallow Sitemaps Last Modified Nofollow Noindex RSS Canonicalization