Here is the question this guide actually answers, because it's the one most PrestaShop merchants get wrong: not "should I run Search ads or Shopping?" but "now that Shopping and Performance Max already drive my product sales, what is a text Search campaign still for?" If you sell physical products, the default and correct advice is to lead with Shopping — a product listing with an image, a price and a title converts harder than any sentence you can write. So a Search campaign that just re-targets "buy linear shower drain" sits underneath your own Shopping listing, pays more per click, and converts less. That's the trap. Search ads earn their budget on the queries and surfaces Shopping physically cannot reach — and knowing exactly where that line falls is the difference between a smart complement and wasted spend.

This post is about that line: when a Search campaign adds coverage your Shopping feed can't, when it's just redundant, and how to wire both into a single PrestaShop store without them fighting. It assumes you already have Shopping running. If you don't yet — if you're standing up your first campaign — start with Google Ads for beginners first, then come back.

What Shopping can't see — and Search can

A Shopping ad is generated from a product in your Google Merchant Center feed. No product in the feed, no ad. That single fact defines the entire boundary. Shopping (and the Shopping inventory inside Performance Max) can only ever answer a query with a product you sell, listed at a price, on a product page. Everything outside that envelope is invisible to it:

  • Your own brand name. Shopping shows products for a brand search, never a brand message — and a competitor can bid a text ad above your organic result while your Shopping carousel just lists items.
  • Informational queries. "How to install a linear shower drain", "what size shower tray do I need" — no product matches, so Shopping stays silent, even though the searcher is a customer three steps from buying.
  • Things that aren't catalogue products. Installation services, made-to-measure quotes, a trade/wholesale enquiry form, a category landing page, a buying guide. None of these can live in a product feed, so none can run as Shopping.
  • The exact words people type. Shopping decides which queries match your products, and Performance Max reports queries only as aggregated search themes — less actionable than a Search term report, even if not entirely hidden.

Those four gaps are the whole case for Search. Walk through each and you have a decision framework, not a vibe.

The decision: when a Search campaign is worth it (and when it isn't)

SituationRun a Search campaign?Why
Customers search your brand nameYes — alwaysCheapest, highest-return campaign you'll run; defends the query you've already earned.
Informational / "how-to" demand around your productsUsuallyShopping can't appear; sends top-of-funnel traffic to content Shopping ignores.
You sell services, bespoke items, or want to push a category pageYesNothing here exists in your feed, so Search is the only Google option.
Merchant Center still in review, store needs traffic todayYes, temporarilySearch has no feed-approval gate; it runs while Shopping waits.
Generic product, transactional query, Shopping already runningNo / minimalYou'd pay more to sit under your own Shopping listing. Let Shopping win it.
Total budget under a few hundred € / monthNo — consolidateSplitting starves both. Put it all in Shopping/PMax first. See choosing the right budget.

Read top to bottom, the pattern is simple: Search is for coverage Shopping lacks, not for competing with Shopping on the same product query. The moment you find yourself bidding a text ad on the same transactional keyword your Shopping feed already serves, ask whether you're buying new coverage or just paying twice.

Brand protection: the one Search campaign every store should run

If you do nothing else with Search, run a brand campaign. When someone types your store name, that results page should be entirely yours — your text ad up top, your Shopping listings, your organic result below. The economics are unusually friendly: because your own site is the most relevant possible landing page for your own name, your Quality Score on brand keywords is as high as it gets, which keeps the cost per click very low (often a small fraction of what a generic product keyword costs — measure it on your own account rather than trusting a quoted figure).

The reason it's non-negotiable is defensive. Competitors are allowed to bid on your brand name, and many do. Without a brand campaign, a rival's ad can sit above your organic listing on a search for you — intercepting a customer who already chose you. A brand text ad also lets you control the message in a way Shopping can't: "Official [Brand] Store" with sitelinks straight to your bestsellers and current promotion. This matters most for niche stores, where the brand name effectively is the moat — a customer who found you through a blog post or word of mouth and searches your name later should never land on a competitor.

The real payoff: Search ads as a feed-improvement engine

Here's the part that justifies a product-keyword Search campaign even when Shopping is performing well, and it's the strongest argument in this post. A Search campaign gives you the full search terms report — every actual query that triggered your ad, what it cost, and whether it converted. Standard Shopping can show search-term data too, but Performance Max is far more aggregated — and Search still offers the cleanest keyword-controlled testing of the three. That raw query data is the highest-quality keyword research you can buy, because it's real commercial intent backed by your own conversion numbers, and it loops straight back into the rest of your Google Ads setup:

  • A query that converts well in Search tells you exactly which phrase belongs in your PrestaShop product titles and descriptions — which is what your Merchant Center feed is built from. Strengthen the feed and your Shopping/PMax matching improves for free. The mechanics of that feed live in Merchant Center feed optimization.
  • A query that gets clicks but never converts becomes a negative keyword — and added as an account-level negative or a shared negative list applied to those campaigns, it trims wasted Shopping/PMax spend too (a campaign-level Search negative won't reach them on its own).
  • The vocabulary your real buyers use (regional terms, sizes, use-cases you'd never have guessed) becomes the language you write your category descriptions in.

So a Search campaign isn't only an ad channel; it's the instrument panel for the channels you can't see into. If your aim is purely the precision of exact-match keyword bidding for a specialised catalogue, that deserves its own treatment — we covered it in why exact keywords are gold for niche stores.

The PrestaShop wiring that makes any of this trustworthy

Search, Shopping and Performance Max all report back to the same place — and on PrestaShop, that reporting is where stores quietly mislead themselves. If conversion tracking is wrong, every "Search converts worse than Shopping" conclusion above is built on sand. Three things to get right before you trust a single ROAS number:

  • The conversion fires on the real confirmation page. A purchase in PrestaShop completes on the order-confirmation controller (URL index.php?controller=order-confirmation) — but that page can be reloaded or revisited, so the tag must fire with the transaction/order ID and de-duplicate on it, or you'll double-count. That is the only page your Google Ads conversion tag — or your GA4 purchase event imported as a conversion — should fire on. Firing on the generic "thank you" CMS page or on a cart step double-counts or under-counts; either way your channel comparison is fiction.
  • Pass the real order value, not a placeholder. Whether you inject the tag through Google Tag Manager (a GTM module on the displayHeader / displayFooter hook) or a dedicated tracking module, the implementation must pull the order ID/reference, total, currency and products from PrestaShop's order context — server-side data, not anything the URL exposes. Hard-coded or rounded values make Smart Bidding optimise toward the wrong orders.
  • De-duplicate across channels. If both a GTM-fired tag and a marketing module fire a purchase event, you'll count some orders twice and Search will look better or worse than it is. Pick one source of truth.

Get this layer right and the comparison between Search, Shopping and PMax finally means something. Get it wrong and no amount of campaign structure saves you. (This is also the same plumbing that powers your Merchant Center feed — the Merchant Center for PrestaShop PPC overview covers how the feed gets built, and getting products into Google Shopping covers the first-time setup.)

A campaign structure that complements Shopping instead of fighting it

Once tracking is honest, structure the Search side around the four gaps — not around products Shopping already covers. A workable shape for a PrestaShop store already running Shopping/PMax:

CampaignTargetsMatch typesJob it does that Shopping can't
BrandYour store name, name + product type, common misspellingsExact + phraseOwns your own SERP; blocks competitor interception.
Non-product pagesServices, bespoke/quote queries, broad category termsPhrase + exactPromotes things that have no feed entry at all.
InformationalHow-to, "vs", sizing and spec questionsBroad + Smart BiddingReaches research-phase buyers Shopping never sees.
Competitor (optional)Rival brand + product typeExact onlyCaptures comparison shoppers — ad copy must never use the rival's name (policy).

Notice what's missing: there's no "everything I sell, again, as text ads" campaign. Generic transactional product keywords stay with Shopping, where the image and price do the selling. The Search campaigns sit beside Shopping covering its blind spots — which is exactly why there's no cannibalisation between them.

Do Search and Shopping cannibalise each other? No — and here's why

This worry stops a lot of merchants from running both. It shouldn't. Google decides which of your ad types to show for each query based on Ad Rank, and Shopping and Search ads frequently appear together on the same results page — your products in the carousel up top, your text ad in the link positions. Two placements for one query generally lifts your combined click-through rate, because the searcher sees you twice. You aren't bidding against yourself; you're occupying more of the page.

Where genuine overlap exists — the same transactional keyword served by both your Shopping feed and a Search ad — the fix isn't to drop one channel, it's to let each do what it's better at. Keep the product query in Shopping, point the Search budget at the four gaps, and the question disappears. Performance Max, meanwhile, is the broad automated engine running underneath all of it; what it actually does and when to lean on it is a topic of its own, covered in the Performance Max for PrestaShop guide and the shorter what PMax does and when to use it.

The one situation where Search comes first, not second

Everything above assumes Shopping is live. There's a clear exception: a brand-new store, or a new product range, before Merchant Center approval clears. Shopping ads can't serve until your feed passes Google's review, and that review can sit in a pending state for days while Google verifies your site, your business details, your prices and your checkout. Search has no feed-approval gate — write the ads, set the keywords, and once your ads clear the usual ad review it can often launch much faster.

So for a launch the order is: turn on Search against your highest-intent product keywords for immediate traffic, submit the feed in parallel, and as soon as Shopping clears, shift the generic product keywords back to Shopping and re-task Search onto the four gaps. (If your feed is what's stuck in review, the usual culprits and fixes are in fixing Google Merchant feed errors.) Treat day-one Search as scaffolding, not the finished building.

Where mypresta.rocks fits

None of this works on bad measurement, and on PrestaShop the measurement depends on the feed and the tracking tags being correct at the source. That's the practical role our Google/Merchant and tag-management modules play: they build the product feed from your real catalogue data and fire the conversion on the order-confirmation controller with the true order value — so when you compare Search against Shopping against PMax, you're comparing real numbers, not tracking artefacts. So what does that buy you? Confidence that the budget decisions in the table above are based on what actually converted, configured from your back office rather than hand-edited template files that break on the next upgrade. The campaign strategy is yours to run; the modules make sure the scoreboard is honest.

The bottom line

Search ads aren't a rival to Shopping and they aren't a relic — they're the coverage layer for everything a product feed can't reach: your brand name, your buyers' research questions, your non-product pages, and the exact search terms that tell you how to improve every other campaign you run. Lead with Shopping for product sales. Add a brand Search campaign because it's cheap and defensive. Add product-keyword Search for the search-term intelligence that feeds back into your PrestaShop titles and Merchant Center feed. And keep the two from overlapping by giving each the job it's better at. Do that on top of honest conversion tracking, and Search stops being an expense you're unsure about and becomes the part of your Google Ads setup that makes the rest smarter.

Share this post:
David Miller

David Miller

Over a decade of hands-on PrestaShop expertise. David builds high-performance e-commerce modules focused on SEO, checkout optimization, and store management. Passionate about clean code and measurable results.

Enjoyed this article?

Get our latest tips, guides and module updates delivered to your inbox.

Comments

No comments yet. Be the first!

Be the first to ask a question or share useful feedback.

Loading...
Back to top