Google is moving the Google Ads Developer Blog, the channel through which it tells agencies, tool vendors and in-house engineers about breaking changes to its advertising APIs, off Blogger and onto its main developer documentation site. In a post dated Tuesday, November 10, 2026, Google said that from November 11 the old address, ads-developers.googleblog.com, redirects to developers.google.com/ads/blog, where the publication takes a new name: the Google Advertising and Measurement Developer Blog. The existing feed stays online but, according to Google, receives no updates after November 10.

In Short

Google has moved its Google Ads Developer Blog from Blogger to developers.google.com/ads/blog, and from November 11 the old address redirects there under a new name. Anyone who follows Google Ads API, Data Manager API, Display & Video 360 API or ad SDK changes through the old feed will stop seeing new posts, because Google says only the new feed is updated after November 10. The new feed sits at developers.google.com/ads/blog/rss.xml, carries only the 25 most recent posts across every product, and leaves out everything published before 2024.

What changes, and when

The announcement, signed by Trevor Mulchay of the Advertising and Measurement Developer Relations Team, opens plainly. "Today we're announcing the move of the Google Ads Developer Blog from Blogger to the Google for Developers platform," the post says, adding that the blog will join the Google Advertising and Measurement Developers Hub and be known as the Google Advertising and Measurement Developer Blog.

Three things happen from November 11, 2026, according to Google. The Blogger homepage at ads-developers.googleblog.com redirects to developers.google.com/ads/blog. Any post published on or after January 1, 2024, and any Blogger label page updated since that date, redirects automatically to its migrated version on the new platform. And all new posts are published solely on the new site, with the most recent one always available at developers.google.com/ads/blog/latest.

That last address is a small but practical addition. A fixed URL that always resolves to the newest post gives monitoring scripts and internal dashboards a single location to check, rather than a list page whose layout may change.

The cutoff date of January 1, 2024 splits the archive in two. Posts from roughly the past 34 months move, by PPC Land's count, while everything from the preceding years stays where it is.

What stays on Blogger

"Any blog posts published before 2024 will continue to be hosted solely on Blogger," according to the announcement. Those older posts will not appear in any feed on the new platform. They will, however, be listed in reverse chronological order on an archive page at developers.google.com/ads/blog/posts/archive and remain reachable at their original URLs.

The archive page already reflects that split. Entries from 2024 onward point to the new platform, while a separate section for posts published before 2024 links back to Blogger addresses, such as the 2022 announcement of version 12 of the Google Ads API at ads-developers.googleblog.com/2022/10/announcing-v12-of-google-ads-api.html.

The practical effect is that the Blogger domain does not disappear. It continues to host several years of migration guides, version announcements and deprecation notices that are still cited in forum threads, internal wikis and code comments. Links to those pages keep working because nothing moves. Links to posts from 2024 onward keep working because they redirect.

What the post does not say is what kind of redirect Google is using. A permanent 301 redirect signals to search engines and link checkers that a page has moved for good, while a temporary redirect does not. Google also does not say how long it intends to keep the pre-2024 posts on Blogger, or whether they will eventually be migrated.

The feed is where the work is

For most readers, the redirects require nothing. The feed is different. "If you receive our content using RSS, point your RSS reader to our new feed at developers.google.com/ads/blog/rss.xml," the post says. Google gives two constraints on the replacement: "This new feed contains the most recent 25 posts and doesn't support product-specific feeds."

The old feed is not being shut down. "While blog updates will be reflected only in our new RSS feed after November 10, the existing feed will continue to be accessible to avoid breaking existing integrations," according to the announcement. In other words, a subscription to the old address will keep resolving without errors, but it will simply stop receiving new posts. A silent RSS feed produces no error to catch, which makes this the kind of change that can go unnoticed for weeks.

What the new feed looks like

Several technical details sit outside the announcement text. The new file, despite its rss.xml name, is written in the Atom format rather than RSS 2.0, and its feed title is "Google Advertising and Measurement Developer Blog". Most feed readers handle both formats. Custom parsers written for RSS 2.0 elements such as item and pubDate, however, would find entry and published elements instead.

The old Blogger feed address, ads-developers.googleblog.com/feeds/posts/default, currently forwards to a FeedBurner address, feeds.feedburner.com/GoogleAdsDeveloperBlog. Subscribers may therefore be following the blog through either of two legacy URLs, both of which now sit on the frozen side of the move.

The newest entries in the new feed show its scope. The five most recent are the move announcement itself (November 10), a post on display targeting changes in Demand Gen campaigns starting the week of December 1 (November 9), a post on preparing for CocoaPods read-only mode by migrating iOS apps to Swift Package Manager (November 6), and two posts on November 4: one on Data Manager API support for Google Ads call conversions and row-level diagnostics, the other on upcoming changes to multi-party approvals in the Google Ads API.

One feed for every product

The loss of product-specific feeds matters because the blog covers far more than Google Ads. The labels attached to the move announcement list the products it spans: Ad Manager API, Authorized Buyers, Data Manager API, Bid Manager API, Display & Video 360 API, Google Ads API, Google Ads scripts, IMA SDK, Structured Data Files, Mobile Ads SDK and Campaign Manager 360 API. That is eleven product labels on a single post.

On Blogger, label pages such as google_ads_api grouped posts by product. On the new platform, the post's label links point to addresses under developers.google.com/ads/blog/feeds/labels/, but the google-ads-api address returns a web page listing posts rather than a machine-readable feed. A developer who maintains only Google Ads scripts, or a publisher whose engineers care only about the IMA SDK, will now receive a single combined stream that includes everything else and has to be filtered downstream.

The 25-post cap interacts with that. The new feed carried five posts in the first ten days of November alone. At that pace, by PPC Land's arithmetic, a 25-post window would cover roughly seven weeks of history across all products. For a reader that polls daily, that is ample. For an integration that needs a longer back catalogue, the archive page rather than the feed becomes the source.

Why the blog matters to advertisers

The blog is a niche publication, but the decisions announced on it reach far beyond developers. Agencies running bulk management platforms, bid management vendors, reporting tools and in-house teams using Google Ads scripts depend on it for notice of changes that can break production code on a fixed date.

Its recent output shows how much moves through it. On July 22, 2026, Google used the blog to release version 25 of the Google Ads API, which removed two lifecycle goal resources and forced code rewrites without a transition window. In September, it dropped developer tokens from Ads API access decisions, tying access levels to Google Cloud projects from September 10. On October 12, Google said the Google Ads API would move to two releases a month starting with v26, keeping four major versions a year and leaving sunset dates unchanged. Two days later came v26 itself, which added 15 Search Lift metrics.

The pace has not slowed this month. On November 4, Google announced that the Google Ads API would change multi-party approvals for user access invitations from the week of December 7. The same day, the Data Manager API gained support for call conversions, with phone numbers accepted only in hashed form. On November 9, Google said that from the week of December 1 the API would move the Display opt-out for Demand Gen campaigns to ad groups, with requests that set the old campaign-level field returning an error.

Two of those changes take effect in the first two weeks of December, one of them in the week that begins on the Monday after Thanksgiving. Any follow-up reminders Google publishes about them will appear only on the new site and in the new feed.

The blog is not the only channel, and it is not complete. When Google announced the twice-monthly cadence in October, it said release blog posts would move to twice a quarter and pointed developers to the release notes page, which can notify subscribers when it changes. And when Google's open-source Google Ads MCP server gained four write tools in version 0.0.6 on November 2, PPC Land found no Google announcement of the release at all, even though the server launched through the Developer Blog in October 2025 as a read-only tool.

A new name, and a familiar platform

The rebrand drops "Google Ads" from the title, which matches what the blog already covers. The developer hub it now sits inside lists products well beyond Google Ads, including the Display & Video 360 API, Campaign Manager 360 API, Data Manager API, Ads Data Hub, Meridian, the Google Mobile Ads SDKs for AdMob and Ad Manager, the Ad Manager API, Google Publisher Tag and the Interactive Media Ads SDK.

Google's stated case for the move is presentation, not substance. The post says the move "won't change the content" and will bring "a new look, improved formatting, and additional features such as clearer tagging and curated product pages." The Google for Developers platform already hosts guides and reference documentation for those products, so the blog will now sit alongside the documentation it frequently points to.

This is not the first Google developer blog to leave Blogger. In November 2020, Google relocated its Webmaster Central blog to developers.google.com/search/blog, where it continues as the Search Central blog.

Google acknowledged that the change disrupts habits. "After 15 years of the Google Ads Developer Blog on Blogger, we know that our dedicated readers and developers are accustomed to how they hear from us," the post says. "Our priority with this migration is to make a better experience for you, and we intend to continue updating our blog with that in mind."

Questions and complaints have a designated, if temporary, home. Google created a channel called #ads-developer-blog on the "Google Advertising and Measurement Community" Discord server, which it says "will be available for the next few weeks."

Mulchay's name has appeared on the blog recently in another context. He signed the October 22 post that opened the Display & Video 360 API v5 public beta, which removed Customer Match audience management and moved it to the Data Manager API.

What remains unclear

Several points are left open by the announcement. Google does not say whether the old feed will eventually be retired, only that it "will continue to be accessible." It gives no timeline for product-specific feeds, if any are planned. It does not specify the redirect type for migrated posts, or what happens to Blogger label pages that have not been updated since January 1, 2024, which by the post's own wording fall outside the redirect rule. Nor does it say whether the 25-post limit on the new feed is fixed.

For a publication whose main job is to give engineers advance warning of breaking changes, the move itself arrived with a single day's notice: announced on November 10, effective on November 11.

Timeline

Summary

Who: Google's Advertising and Measurement Developer Relations Team, in a post signed by Trevor Mulchay, and the developers, agencies, tool vendors and publishers who follow the Google Ads Developer Blog for notice of API and SDK changes.

What: The Google Ads Developer Blog moves from Blogger to the Google for Developers platform and is renamed the Google Advertising and Measurement Developer Blog. The Blogger homepage, posts from January 1, 2024 onward and label pages updated since then redirect to the new site. Older posts stay on Blogger and are excluded from the new feed. The new feed, at developers.google.com/ads/blog/rss.xml and formatted as Atom, holds the 25 most recent posts and offers no product-specific feeds. The old feed stays accessible but receives no new posts after November 10.

When: Announced on Tuesday, November 10, 2026. Redirects and new-site-only publishing begin on November 11, 2026.

Where: The blog moves from ads-developers.googleblog.com to developers.google.com/ads/blog, inside the Google Advertising and Measurement Developers Hub. Feedback goes to a temporary #ads-developer-blog channel on the Google Advertising and Measurement Community Discord server.

Why: Google says the platform brings a new look, improved formatting, clearer tagging and curated product pages without changing the content. The move matters because the blog announces breaking changes across Google's advertising APIs, including two that take effect in the first weeks of December, and subscribers to the old feed will not see any further posts.