I’ve discovered how essential it is to integrate trusted search intelligence across our enterprise. With the Conductor Data API, we’re extending these capabilities in ways I hadn’t imagined.
Seeing our data work harmoniously across platforms feels transformative, allowing us to leverage AI infrastructure like never before. This powerful insight has reshaped how we view our enterprise integration strategies.
Inspired by this post on Conductor Blog.
Is this the new technical SEO frontier? This question is top of mind for many of us as Google has recently unveiled an early preview of WebMCP, a protocol shaping the way AI agents engage with websites. According to André Cipriani Bandarra from Google, “WebMCP aims to provide a standard way for exposing structured tools, ensuring AI agents can perform actions on your site with increased speed, reliability, and precision.”
WebMCP offers developers the capability to communicate with LLMs through our websites about the specific actions that various buttons and links should initiate. With this protocol, websites can publish a “Tool Contract” using the new browser API, navigator.modelContext. This means rather than leaving the AI to guess, our websites can present a structured list of functions, like buyTicket(destination, date), allowing the AI to execute these functions directly.
Structured interactions for the agentic web. WebMCP introduces two new APIs enabling browser agents to act on behalf of users:
These APIs serve as a crucial bridge, making our websites “agent-ready” and facilitating more reliable and high-performance agent workflows compared to raw DOM actuation.
Use cases that Google has put forward highlight how AI agents can tackle complex tasks efficiently and confidently for users:
How to access the preview. If you’re interested in trying out WebMCP, you can apply for the preview through this link.
Why we care. The advent of agentic experiences marks a significant shift in search and potentially SEO. Esteemed voices in the industry, such as Dan Petrovic and Glenn Gabe, have highlighted this as a pivotal transformation, comparable to the impact of structured data and described it as a big deal.
Exploring these cutting-edge protocols could be extremely valuable for anyone keen on staying at the forefront of SEO developments.
Inspired by this post on Search Engine Land.
Have you ever wondered where your Performance Max ads truly run? With the latest Google Ads API v23 update, we finally have the answer!
An exciting change has arrived with the v23 Ads API launch. Now, Performance Max campaign results can be broken down by channel, including Search, YouTube, Display, Discover, Gmail, Maps, and Search Partners. Previously, all your performance data was lumped together, obscuring critical insights.
Here’s the inside scoop. In earlier API versions, I always received a MIXED value for the ad_network_type segment in my Performance Max campaigns. But with v23, these results have transformed into distinct channel enums. It’s a major step forward for those of us who crave precision in reporting and optimization.
Why this matters to us. This update isn’t just about new features — it reshapes how we comprehend Performance Max. With channel-specific reporting now on the table, marketers gain much-needed clarity on where these ads are displayed.
How we can leverage this. Now, we can access channel-level data at the campaign, asset group, and even individual asset levels. This means we can observe how each creative piece performs across Google’s array of platforms. Coupled with v22 segments like ad_using_video and ad_using_product_data, the possibilities for optimizing video performance on YouTube or Shopping ads on Search are endless.
Attention, developers. Upgrading to v23 unveils a level of reporting detail that was previously unreachable. If your system relied on the old MIXED values, it’s time to gear up for the new channel enums.
Keep an eye out for:
The takeaway. The newest Google Ads API rollout quietly transforms what was once a black-box campaign category into an analyzable channel-specific type. Finally, advertisers like you and me can dive into the metrics we’ve long sought.
Inspired by this post on Search Engine Land.
As I delve into Google Ads API v23, I’m excited to share this update marks the beginning of a faster-paced release cycle in 2026. With this update, I’m now able to access improved Performance Max reporting, sophisticated AI-driven audience tools, and more detailed campaign controls.
What’s new:
Performance Max Transparency: I’ve discovered that PMax campaigns now offer ad network type breakdowns, making it easier for me to analyze performance.
More Detailed Invoices: Through InvoiceService, I can retrieve campaign-specific costs, regulatory fees, and adjustments, allowing for more precise financial tracking.
More Precise Scheduling: It’s a game-changer for me to now schedule campaigns using precise start and end date-times instead of limiting to date-only fields.
Local Data Access: I’m now able to access store location details via PerStoreView, which matches the data in the Stores report accurately.
New Audience Dimension: With life-event-based audience building through LIFE_EVENT_USER_INTEREST, my Insights tools are more powerful than ever.
Smarter Demand Gen Planning: The conversion rate forecasts I rely on now vary by surfaces such as Gmail and Shorts, enhancing my strategy planning.
Generative AI Audiences: I can efficiently translate free-text audience descriptions into structured attributes, simplifying audience target creation.
Expanded Shopping Metrics: The inclusion of new competitive and conversion metrics by conversion date helps me improve my shopping ads performance.
Why I care: A quicker update cycle means I can leverage new features faster. With Google’s shift towards automation and AI-driven insights, staying on top of these updates helps me optimize campaigns effectively.
Between the lines: These updates require my team to upgrade client libraries and code, so scheduling development time is crucial to benefit fully from v23.
Bottom line: The Google Ads API v23 is setting the stage for 2026. I’m ready to embrace these improvements that introduce faster releases coupled with enhanced AI insights, refined reporting, and better campaign control for large-scale advertisers.
Inspired by this post on Search Engine Land.
As someone deeply invested in digital advertising, I recently learned about Google’s impending changes to their Shopping API. If you rely on Shopping and Performance Max campaigns like I do, switching to Google’s Merchant API isn’t just recommended—it’s essential to keep things running smoothly.
What’s happening. Google plans to phase out older API versions, making the Merchant API the go-to for all things Shopping Ads. I checked my own campaigns in Merchant Center Next under Settings > Data sources to see which API I’m using. Any listing marked as “Content API” needed my immediate attention.
Why this matters to us. Google has been actively notifying us advertisers to make the move to the new Merchant API. For those in beta, the deadline is February 28th, and for others using Content API, it’s August 18th. If I miss this, my campaigns that depend heavily on product feeds might just stop working. That’s not a risk I’m willing to take.
The risk. I realized that feed labels don’t seamlessly transfer during the migration. Overlooking this can cause significant issues in Shopping and Performance Max campaigns, which rely on these labels for structure or bidding strategies. Without proper updating, my campaigns could quietly fail.
What to do now. Google’s suggesting that we complete this migration sooner rather than later. On my end, that means reviewing my feed labels, reconnecting my data feeds, and making sure everything’s back on track. This transition process started in mid-2024 and is becoming urgent as legacy APIs are on their way out.
Bottom line. Ignoring this isn’t an option for me. This change is more than just a backend tweak—it’s a potential revenue disruptor if not addressed promptly.
First seen. I first caught wind of this update through Google Shopping Specialist Emmanuel Flossie. He flagged the issue on LinkedIn.
Inspired by this post on Search Engine Land.