Every now and then we get questions about robots.txt, robots meta tags, and the control functionality that they offer. Following our December series on crawling, we thought this would be the perfect time to put together a light refresher. So, if you're curious about these controls, follow along in this new blog post series!

We're excited to announce that Search Central Live is coming to New York City for the first time on March 20, 2025. The Google Search team has organized events in the city several times, but this time we're bringing our main Search event to the city that never sleeps. Come and join us for a day of discussion, listening, and meeting new people.

Mobile searchers will soon see a cleaner, more streamlined look for how URLs appear in search results. Initially introduced as part of the "site hierarchy" feature, we've found that the breadcrumb element isn't as useful to people who are searching on mobile devices, as it gets cut off on smaller screens. Starting today, we'll no longer show breadcrumbs on mobile search results in all languages and regions where Google Search is available (they continue to appear on desktop search results).

We're excited to announce that Search Central Live is returning to São Paulo in 2025. Following our successful events in 2023 and 2024, we're continuing our mission to help Brazilian businesses enhance their site's performance in Google Search. And this year we're visiting Recife for the first time.

It might happen that by the end of this post you're going to try to decide who wrote this blog post, a large language model (LLM) or Gary. And you'd be right to ponder that and delve into the intricacies of the language used that gives away LLMs, for this is the time of the year when we can get away with publishing a blog post with barely any review (future Gary will deal with the potential, nay, likely fallout I guess). As we often do in the last post of a year, we're looking at what happened on Google Search Central in 2024 according to an LLM (or Gary), and maybe hinting at what might be coming in 2025 (but maybe this is just a hook to keep you reading...).

Content delivery networks (CDNs) are particularly well suited for decreasing latency of your website and in general keeping web traffic-related headaches away. This is their primary purpose after all: speedy delivery of your content even if your site is getting loads of traffic. The "D" in CDN is for delivering or distributing the content across the world, so transfer times to your users is also lower than just hosting in one data center somewhere. In this post we're going to explore how to make use of CDNs in a way that improves crawling and users' experience on your site, and we also look at some nuances of crawling CDN-backed sites.

Faceted navigation is a great way to help users find what they need on your site, but it can create an SEO nightmare if not implemented carefully. Why? Because it can generate a near-infinite number of URLs, which causes all sorts of crawling problems.

The Search Central Live events in Kuala Lumpur and Taipei were nothing short of amazing, in large thanks to the over 600 people who attended the events! We were thrilled to see the level of enthusiasm and engagement from attendees even if, on the day prior to the Taipei event, we collectively had to deal with typhoon Kong Rey, the first supertyphoon in Taiwan's history to make landfall after mid-October. Here's a deeper dive into what made these events so special and what's next.

To better help you monitor the recent performance of your content, we're launching the '24 hours' view to the SC performance reports and improving the freshness of the data. We're rolling out these changes to all properties gradually over the next few months, so you might not see changes right away.

Allow us to cache, pretty please. As the internet grew over the years, so did how much Google crawls. While Google's crawling infrastructure supports heuristic caching mechanisms, in fact always had, the number of requests that can be returned from local caches has decreased: 10 years ago about 0.026% of the total fetches were cacheable, which is already not that impressive; today that number is 0.017%.