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
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
Find out everything you need to know in our new uptime monitoring whitepaper 2021