An SEO professional asked John Mueller about core updates during a submitted Question and Answer segment of his hangout.
They asked: their website was ranking well, before they performed a design overhaul.
Their timing was terrible, because the core update was released just after the launch of this new website. And this website had some issues with internal links.
They suspect that Google reassessed the quality of the site at this time, but they could resolve the issues.
Their ranking and traffic dropped a lot, they lost all rich snippets in the process and their site has been in limbo for the past five or six months.
Do they wait for another core update for Google to assess their site quality again? Or does this happen when the site is re-crawled?
John answered that he thinks there are a few things that come together here. Firstly, he would recommend checking out their blog post that they did about the core updates.
John thinks it’s called “what site owners should know about core updates” – something along those lines.
And, it has a lot of information about core updates, especially about the kinds of issues that they look into there, and how things are resolved over time.
That’s the first thing they would do in a case like this. The information that they use for core updates, to understand the site, is something that’s collected more over the long term.
That means if you are seeing any effects from a core update, that’s usually due to a longer period of time where Google has run into issues that they are looking at with these core update algorithms.
Also, regarding technical issues, usually this is not a trigger for core updates, because technical issues are not the same as site quality issues.
There can be some technical issues, such as when a user looks at the website and the implementation makes it impossible to use the site.
But if it’s something small, like 404s on a page or broken links, then usually this is not a huge issue for Google. But there are many other things that their quality algorithms look for, and those are all listed in the blog post John mentioned.
This happens at approximately the 10:53 mark in the video.