Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



In a Google Webmaster Central Hangout recently, a question was put to Google’s John Mueller.
“Wondering if Google checks status codes before anything else, like before rendering content?”
This is a great question to John – in very simple terms do Google care about the status code on your website?
The answer is categorically yes. Google does indeed check the status code of a website page before indexing it, or rendering content.
A 200 “OK” success status code is the standard response for successful HTTP request, and for a page that is working correctly. As such the Google crawler looks for the 200 status code before it does anything else – it tells Google that there may be content on that page that it should index.
Alternatively if a page responds with a status code that suggests an error with page, e.g. a 4xx or 5xx status code, or redirect then this is a signal that Google uses in its decision not to go ahead and start indexing the page.
Given the important of rendering content and indexing it in Google website owners should ensure that their website is giving a correct status code at all times. A website monitoring tool such as StatusCake can be used to alert you if a status code other than the OK “200” is being triggered. So for instance if your website starts responding with a 4xx or 5xx status code you’ll be alerted immediately. Status code monitoring means you can ensure pages on your website which respond with the wrong code are immediately corrected, ensuring your site content doesn’t get ignored by Google leading to a fall in traffic to your website, and thereby revenue.
Share this
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes

3 min read IPFS is a game-changer for decentralised storage and the future of the web, but it still requires active monitoring to ensure everything runs smoothly.

3 min read For any web developer, DevTools provides an irreplaceable aid to debugging code in all common browsers. Both Safari and Firefox offer great solutions in terms of developer tools, however in this post I will be talking about the highlights of the most recent features in my personal favourite browser for coding, Chrome DevTools. For something

6 min read There has certainly been a trend recently of using animations to elevate user interfaces and improve user experiences, and the more subtle versions of these are known as micro animations. Micro animations are an understated way of adding a little bit of fun to everyday user interactions such as hovering over a link, or clicking
Find out everything you need to know in our new uptime monitoring whitepaper 2021