Google has made changes to a few of its Google search help documentation over the past couple of days. The documents updated include HTTP status codes, the Googlebot and job posting help documentation. Note, the HTTP status code aspect is not new, the content was just moved from one location to another.
On the Googlebot how many bytes of textual content, such as HTML, Googlebot will crawl specifically over here. Here is the new lines of text:
Googlebot can crawl the first 15MB of content in an HTML file or supported text-based file. After the first 15MB of the file, Googlebot stops crawling and only considers the first 15MB of content for indexing.
On the job postings, Google specified that when you use the jobLocation property, you must also include the addressCountry property.
HTTP Status Codes
FWIW the soft-404 docs were just moved, they’re … not new 🙂
— 🐝 johnmu.csv (personal) 🐝 (@JohnMu) June 23, 2022
soft 404 errors
A soft 404 error is when a URL that returns a page telling the user that the page does not exist and also a 200 (success) status code. In some cases, it might be a page with no main content or empty page.
Such pages may be generated for various reasons by your website’s web server or content management system, or the user’s browser. For example:
- A missing server-side include file.
- A broken connection to the database.
- An empty internal search result page.
It’s a bad user experience to return a 200 (success) status code, but then display or suggest an error message or some kind of error on the page. Users may think the page is a live working page, but then are presented with some kind of error. Such pages are excluded from Search.
When Google’s algorithms detect that the page is actually an error page based on its content, Search Console will show a soft 404 error in the site’s Index Coverage report.
Fix soft 404 errors
Depending on the state of the page and the desired outcome, you can solve soft 404 errors in multiple ways:
Try to determine which solution would be the best for your users.
The page and content are no longer available
If you removed the page and there’s no replacement page on your site with similar content, return a 404 (not found) or 410 (gone) response (status) code for the page. These status codes indicate to search engines that the page doesn’t exist and the content should not be indexed.
If you have access to your server’s configuration files, you can make these error pages useful to users by customizing them. A good custom 404 page helps people find the information they’re looking for, and also provides other helpful content that encourages people to explore your site further. Here are some tips for designing a useful custom 404 page:
- Tell visitors clearly that the page they’re looking for can’t be found. Use language that is
friendly and inviting.
- Make sure your 404 page has the same look and feel (including navigation) as
the rest of your site.
Consider adding links to your most popular articles or posts, as well as a link to your
site’s home page.
- Think about providing a way for users to report a broken link.
Custom 404 pages are created solely for users. Since these pages are useless from a search engine’s perspective, make sure the server returns a 404 HTTP status code to prevent having the pages indexed.
The page or content is now somewhere else
If your page has moved or has a clear replacement on your site, return a 301 (permanent redirect) to redirect the user. This will not interrupt their browsing experience and it’s also a great way to tell search engines about the new location of the page.
Use the URL Inspection tool to verify whether your URL is actually returning the correct code.
The page and content still exist
If an otherwise good page was flagged with a soft 404 error, it’s likely it didn’t load properly for Googlebot, it was missing critical resources, or it displayed a prominent error message during rendering. Use the URL Inspection tool to examine the rendered content and the returned HTTP code. If the rendered page is blank, nearly blank, or the content has an error message, it could be that your page references many resources that can’t be loaded (images, scripts, and other non-textual elements), which can be interpreted as a soft 404. Reasons that resources can’t be loaded include blocked resources (blocked by robots.txt), having too many resources on a page, various server errors, or slow loading or very large resources.
Hat tip on this from Kenichi Suzuki on Twitter.
Those are the changes spotted in the past couple days to Google’s help documentation.
Forum discussion at Twitter.
Google Officially Brings Continuous Scroll To Desktop Search
Google has officially brought the continuous scroll feature from the mobile search results to the desktop search results. Google has been testing this for a while after bringing it to mobile in October 2021, and now it is live in the US English search results.
Here is a GIF of it in action:
Google has been continuous scroll for mobile search last October. Google has also tested infinite scroll on desktop search for many many many years. Again, we have seen Google test this countless times, as far back as 2015 and even back to 2011. So it is not surprising to see this roll out.
Brodie Clark spotted this rollout last week and posed about it on Twitter but it was not “fully” rolled out until this week and still is gradually rolling out.
Google told me “we’re bringing continuous scrolling to desktop so you can continue to see more helpful search results with fewer clicks. It’s now even easier to get inspired with more information at your fingertips.” “Now, when you scroll down you’ll continue to find relevant results so that you can discover new ideas. When you reach the bottom of a search results page, up to six pages of results will be automatically shown until you see a “More results” button if you wish to continue further,” Google added.
Also, what this means for Google Ads:
Hi Julie, Yes, this article captures the impact that infinite scroll will have on desktop as well https://t.co/EGoCrZq4lF
— AdsLiaison (@adsliaison) December 5, 2022
Forum discussion at Twitter.