An older Google Webmaster Tools feature name for retrieving a page and inspecting how Google could render it, now generally encountered in historical instructions.
Older audits may tell you to use Fetch as Google or Fetch and Render. The practical task was to investigate whether the crawler could retrieve the URL and see important content. Those instructions should be translated to the current URL Inspection workflow rather than followed as a search for a missing menu.
URL Inspection separates information about Google’s indexed version from a live test of the URL. That distinction matters after a release: a successful live test describes current accessibility, while the stored inspection can still reflect an earlier crawl.
Rendering is only one part of diagnosis. Check the response, resources and main content together. A screenshot that looks correct does not by itself prove the page has been indexed, selected as canonical, or ranked for the intended searches.
Takeaway: Use current URL Inspection evidence to test crawler access and rendering, and label whether findings came from a live or indexed version.
Example
A page loads its product description with JavaScript. After a repair, a live test shows the description, while the indexed inspection still records the older crawl. The team records both rather than declaring indexing complete.
What to check
Save the tested URL, test type and timestamp. Check that the inspected URL is the actual canonical destination rather than an outdated redirect.
For more detail, see Google URL Inspection documentation.