Adding a multi-language field to the backend takes an afternoon. The part that takes months sits in …
Google Rewrites Your Product Titles. Your PDP Has No Idea.
Google Rewrites Your Product Titles. Your PDP Has No Idea.
Google can now show an AI-generated alternative title in Shopping ads whenever the system judges it more relevant than the original title in your feed. What's new is a dedicated "product titles" report that puts both versions side by side, with impressions, product clicks, CTR, cost, and average CPC per title. For the first time, you can measure exactly what shoppers read before they land on your PDP.
What the new product titles report actually shows
The underlying mechanism isn't new, according to Search Engine Land: Google has been testing AI-generated title replacements in Shopping ads when the system rates them as more relevant to the search query. Your original title is preserved and can still be served. What's new is the report itself: it puts the original and the AI variant side by side and shows impressions, product clicks, CTR, cost, and average CPC for each.
Before this, the gap was invisible to you. You could measure campaign performance, but not which title triggered the click, and whether that title matches what's actually on your product detail page.
The real story is the gap, not the control
It's tempting to read this report as a control feature: finally, you can see what Google does with your titles. That's not the point. The point is that the report makes visible a gap that never showed up in any conversion analysis, because nobody could see the two titles side by side.
A shopper clicks an ad built around a product message you didn't write, and lands on a PDP tuned for your original title and your original attributes instead. That's a message-match break happening in the middle of the purchase decision. It costs conversions, but until now nobody could trace it, because the cause sat between two systems: the feed you control, and the ad Google assembles.
It's the same pattern we're seeing in Google's Tag and Tag Manager merger: an automation layer above your frontend takes over a decision that used to sit inside the store, and the effect only shows up where shoppers actually land. System1's AI creative testing is the same shift, just pointed at the landing page instead of the ad.
If Google's title wins, that's a PIM finding
Here's the practical read: if the AI variant consistently outperforms your own title in the report, that's not an AI win. It's a feed quality finding. Google isn't rewriting creatively, it's filling gaps your original title leaves open, missing attributes, generic phrasing, or search terms shoppers actually use that your PIM never captured as a structured field. This report is, at minimum, the best free PIM audit you're going to get.
Three scenarios worth distinguishing when you pull the report:
- AI title consistently wins: an attribute gap in your feed, your PDP structure isn't reacting to what demand is actually searching for.
- Original title consistently wins: your title logic is working, PDP match is stable.
- Both titles perform similarly: the title isn't the bottleneck, look elsewhere on the PDP next.
Akeneo and Magento show the same root problem from the other direction: the PIM ships clean data, but the storefront doesn't surface it in the structure that decides discovery and conversion.
What this means for feed and PIM owners
The report on its own doesn't change your PDP. The follow-up is a frontend task: your product detail page needs to surface, prominently, the attributes Google's AI is systematically rewriting toward, not bury them ten rows down in a spec table. How those attributes actually travel from PIM to storefront is easier to see on a real Pimcore integration: the data is usually already there, it just never reaches the part of the PDP structure that decides the click.
For merchants and feed owners, that means pulling the report on a schedule, prioritizing titles with the biggest CTR gap, and tackling two things in parallel. First, add the attribute Google filled in as a structured field in your PIM instead of leaving the fix on Google's side. Second, restructure the PDP so that exact attribute is visible above the fold instead of disappearing into a generic description.
FAQ
Does Google permanently replace my original product title? No. Your saved title is preserved and can still be served. Google decides per auction which version looks more relevant.
Where do I find the product titles report? In the product performance section of Merchant Center, alongside your Shopping ads reporting.
Do I need to rewrite my entire title catalog now? Not across the board. Use the report as a priority list, start with the titles that show the biggest CTR gap instead of rebuilding your whole catalog logic at once.
Is this a Google Ads issue or a PIM issue? Both, and that's the point. The ad is only the visible symptom, the actual gap sits between your feed data model and your PDP structure.
What this means for your frontend
This week's stories all point at the same thing: the more decisions get automated above your frontend, from tag definitions to creative screening to product titles, the more expensive a frontend becomes if it can't reflect those decisions. The product titles report is the first time that's measurable for product data. What you do with it gets decided on your PDP, not inside Google Ads.
If you want to see what a PDP structure looks like when it actually surfaces PIM attributes instead of hiding them: see how Laioutr builds Composable Headless Frontends.
More from the Laioutr Platform
About the author: Laioutr Team. We build the Frontend Management Platform that lets marketing and feed teams control PDP structure independent of the backend.