Shopping feed titles: keyword-packed or the plain product name?

Take a store with about 2,000 SKUs where the feed titles are just the supplier names, something like "Acme K3 Pro 512GB Black". Shopping and PMax match queries against those titles, so someone searching "waterproof running shoes women" may never trigger the listing at all. The usual advice is to stuff every search term into the title, but I think that backfires past a point. Long titles get cut off on mobile, a cluttered title can drag CTR down, and loose matching pulls in junk queries that eat budget. A better approach is to put the highest-intent terms in the first 70 characters, keep brand and model, and add a modifier only when search-term data shows people actually use it. Has anyone seen a clean before and after on title rewrites, judged on conversion rate and not just impressions?

I'd disagree with waiting on search-term data first. If the title doesn't say "waterproof" or "women," the listing never gets those queries, so the data you're waiting for never shows up. Add the modifier to a handful of SKUs where it's accurate, then read the search terms.

Mira's right that the title is the gate, so waiting for search terms can be circular. But I'd add one filter before adding the word: only put a modifier in the title if the product honestly satisfies that query. A click from a shopper who wanted something else costs money and drags down conversion rate, which is the number Priya cares about.

Say a shoe is water-resistant but not waterproof. "Waterproof" in the title will match queries you'll lose on, and the search terms report will show those losses as junk, so you end up blaming the wrong thing.

My rule would be that if the attribute is a fact you could defend to a customer, it goes in the title. If it's a use case the product only sometimes fits, leave it out and test it in a separate campaign or with a custom label. Pick 20 to 30 SKUs with enough traffic to read, and compare their conversion rate against the rest of the catalog over a few weeks.

Your defensible-fact test is solid, and I'd add one more check: the claim should also live in a structured feed attribute, not just the title. If "women" is in the title but the gender attribute says unisex, the listing can get grouped and filtered inconsistently, and the search terms report won't show you why. Same with "waterproof" against a water-resistance field. Titles work as a summary, but attributes are where the engine reads product facts reliably.

So my rule of thumb is that a modifier goes in the title only if the same fact is in a feed attribute and on the product page. If you can't point to all three, treat it as a test for a separate campaign, not a title change.

As far as I know, Microsoft Shopping reads the same kinds of fields, so the same rule applies there if you run both channels.

I don't think the product page should be a hard gate too. Shopping matching and filtering run off the feed attribute, so if gender or water-resistance is set correctly there, the title is doing its job. Requiring the page to match as well would block title changes on most of a 2,000-SKU catalog, since supplier-fed pages are often thin, and then you're fixing a content problem before you've even shown the modifier helps. The page does matter for policy, though. If the title promises something the landing page contradicts, that's a misrepresentation issue, so run that as a separate check.

Dropping the page as a hard gate makes sense to me, but a thin page will still muddy your results. If you change titles on 30 SKUs and half of them have bare supplier copy, a conversion drop could come from the page, and you'd end up blaming the title.

So don't gate on the page, stratify the test instead. Tag each test SKU roughly by page quality (description length, real photos or not), then make sure the modified and control groups have a similar mix. A custom label on the test SKUs makes them easy to filter in the Shopping report.

Read conversion rate and cost per conversion for each group, not clicks or impressions. Clicks will almost always go up after you add a modifier because you're matching more queries, so they tell you very little about whether the change paid off.

Stratifying by page quality makes sense. On a supplier-fed catalog, a lot of thin pages also show a different price or stock state than the feed, so make sure test and control SKUs have the same out-of-stock rate over the test window. If half your test group runs out of stock, it'll look like a title failure in the conversion numbers.