In the previous page you have seen how Fetch and Render serves as troubleshooter to identify potential issues with your content, which may make it user unfriendly.
As we sign up for Google Search Console, Googlebot will crawl our website overall. However we do not want to risk individual pages and future posts and reviews to miss out in the process. That is why it is recommendable that we fetch and render every new content piece we publish.
Furthermore, as Kyle advises that we should always go back to our old reviews and spruce them up in an attempt to ensure that our content remains as correct and up to date as possible, we risk Google not crawling new versions of our posts and reviews.
That is when Fetch and Render becomes essential in inviting Google to index your changed content.
So, how to fetch and render? Find out in the next page.
Reply
How about you young Rebecca, how are you faring??
In passing though, as I try to fetch and render, I keep getting a partial reading - it keeps telling me it's something to do with the coding, which is well beyond my knowledge.
Some say fetching should be enough, others swear you should go for the double function.
