🤓 4 facts about the 404 page every SEO should know


Sponsored:

Explore the Wix Studio SEO resource center

Ramp up productivity with a growing library of expert-crafted templates, toolkits, and checklists, designed to speed up SEO implementation on any project. From a GA4 event cheat sheet to a customizable podcast planning template and a yearly client goal planner, these resources are created by the industry’s most trusted experts for SEOs, marketers, designers and developers.

Customize and use them on your next project to streamline SEO processes and set your clients up for lasting search success.

Download Resources>

Of course you know what a 404 page is.

But do you know these 4 facts about how Google treats 404 pages?

(The 3rd one might be the most unexpected)

Fact 1:

Your 404 page must return a 404 HTTP response code.

If it returns a 200 code, it will be seen as “soft 404”. It is Google's interpretation of a 200 page that is blank, has thin content or looks like a 404 page.


Fact 2:

When a URL returns a 404 error for some time, Google starts crawling it less frequently. So when Googlebot comes to the website, it first focuses on those URLs which historically don’t return errors. This ensures that the crawl budget isn’t wasted.


Fact 3:

Google won’t use content on a page which returns a 404 (or soft 404) error and will drop this URL from the search.

Fact 4:

If a page returns a 404, Google will ignore all the content found on this page, including any canonical or noindex tags.

One of my Tech SEO Pro students discovered that most pages on his client's website returned 404s instead of 200 HTTP status codes. The pages looked normal at first glance; they had all the content and optimization. But the wrong HTTP status code was ruining everything. They did a pretty easy fix and my student was seen as a hero who finally resolved the mystery 🕵🏼‍♂️

💡 Pro tip:

Monitor your 404 pages in GA4 or your server logs to see which error pages are visited by real users and need to be fixed.

4 facts about the 404 page

Download a free PDF with a copy of this post, so it's easy for you to get back to it when you need (no signup required) 👇👇👇

Smart SEO Newsletter

I'll help you trade an imposter syndrome for a technical SEO superpower. My mission is to break down and simplify complex technical SEO things so that you can understand and use them to advance your SEO career.

Read more from Smart SEO Newsletter

Critical knowledge alert 🚨🚨🚨 As a technical SEO, it’s crucial you know the difference between source code and rendered HTML them. Source code It is the initial code of the page before any JavaScript files are executed and CSS files are parsed. It’s the code you see when viewing the source code of a page in your browser. Rendered HTML It is displayed after CSS and JavaScript are processed. When you inspect an element on a page using Chrome dev tools, you’re looking at the rendered HTML. Why is...

JavaScript is a great option to make website pages more interactive and less boring. But it’s also a good way to kill a website’s SEO if implemented incorrectly. Tired Oh No GIF by Law & Order That’s why, as a technical SEO, you need to be comfortable debugging JavaScript issues. Here’s how you do it in 3 steps 👇👇👇 Step 1: Disable JavaScript in the browser using Web Developer Chrome extension The easiest way to do it is to disable JavaScript in your browser. I use the Web Developer Chrome...

Google and JavaScript

Here’s the truth every SEO needs to know: No matter how great your website is, if Google can’t index it due to JavaScript issues, you’re missing out on traffic opportunities. JavaScript is a great option to make website pages more interactive and less boring. But it’s also a good way to kill a website’s SEO if implemented incorrectly. So here’s what you need to know about Google and JavaScript relationships👇👇👇 Google doesn’t interact with your content Googlebot can’t click the buttons on your...