Google fixes the cache 404 issue with mobile-first indexing

After several months, Google has fixed the bug that caused the cache page to fail to load.

Chat with SearchBot

Error 404 Ss 1920

For several months, some Google cache links on search results pages have been serving 404 page not found errors when people clicked. While Google confirmed that this mobile-first indexing cache bug didn’t affect the site’s ranking, that didn’t stop webmasters from being concerned.

Google fixed the bug: This weekend, Google rolled out a fix that has resolved the issue that was causing the cache link to serve a 404 page.

Google has not yet confirmed that they fixed it fully but, based on all of my tests, the issue is certainly not as widespread as it once was.

What was the bug? You were simply unable to view the cached version of your web page from the Google search results. There was a hack, but that is no longer needed. Here is a screenshot of the error that people were seeing:

Google Mobile First Google Cache 404 1527507934

Why did it matter? The truth is, it didn’t matter much. It caused concern amongst SEOs and site owners that the cache link would 404. But Google said it didn’t impact rankings or anything else; it was just an internal bug.


About the author

Barry Schwartz
Staff
Barry Schwartz is a Contributing Editor to Search Engine Land and a member of the programming team for SMX events. He owns RustyBrick, a NY based web consulting firm. He also runs Search Engine Roundtable, a popular search blog on very advanced SEM topics. Barry can be followed on Twitter here.

Get the must-read newsletter for search marketers.