The Product Page Audit I Run Before a Campaign

TLDR

Open Shopify Analytics and GA4 first — the pages pulling traffic without converting are where the audit starts.
Klaviyo session paths show what visitors actually did before they left, not just where the funnel dropped.
The first scroll on mobile is the audit. If decision-critical information is below the fold, most visitors never see it.
Every claim your ad makes needs to appear on the page before the visitor scrolls, in the same language the ad used.
The same page serves three visitors with three different questions: cold paid, organic search, and returning customer.

A merchant I mentor runs a children’s boutique in the UK. She was getting strong engagement on a category she knew was popular, Mustard Made lockers, high visual appeal, high interest, but the traffic wasn’t converting. The page looked right, the product was right, and the audience was clearly interested. There was no obvious problem to investigate.

The real conflict was the price point. Mustard Made lockers run $200 to $400. A customer who has never heard of your store isn’t making a fast decision on a $300 purchase. The consideration cycle is longer, and the bar to clear before a first-time visitor hands over that much money to a brand they found twenty minutes ago is substantially higher than it is for a $40 item. Before they evaluate the product, they’re evaluating the store: whether you have reviews, what your return policy is, how you handle shipping, and whether anything on the page gives them enough confidence to spend that much with someone they’ve never bought from.

We started with competitive research. We pulled the PDPs of other retailers carrying the same line and audited what was visible above the fold: what information appeared first, in what order, and what each page prioritized before asking for the add to cart. The stores converting on high-ticket items weren’t leading with product imagery alone. They were leading with the information that reduces purchase risk, positioned where a skeptical first-time visitor would see it immediately.

She made one focused change: brought her extended return policy, free shipping threshold, and current promotion out of where they had been buried and into the trust bar at the top of the page. The information was already true about her store. Moving it to where a skeptical visitor would see it before scrolling changed the outcome.

There’s a version of this audit that gets done: when there’s a concrete problem, a clear investigation, and a moment when the data confirms the fix. Running it before the problem exists is harder. When the page seems fine, traffic is acceptable, and nothing is obviously wrong, there’s no confirmation moment. You’re looking for problems that haven’t surfaced yet, which makes them genuinely harder to prioritize than problems that are already costing you.

Start with the data, not the page

Open Shopify Analytics and GA4 before you look at any product page. Two lists matter: which pages are driving revenue, and which pages are pulling significant traffic without converting. They point to different products and different problems.

For high-traffic, low-conversion pages, the gap between visits and adds-to-cart tells you something is interrupting the decision. The referral source tells you who’s arriving and what state of mind they’re in. A page not converting organic search traffic has a different problem than the same page not converting paid social traffic. Run them as separate audits.

For individual session behavior, I use Klaviyo to spot-check journeys of identified profiles by referral source. Aggregate funnel data shows where drop-off happens. Watching actual session paths of real visitors shows what they did before they left: which products they looked at, how far they scrolled, whether they came back. Session paths show you things that conversion percentages bury.

What you’re reading in a Klaviyo session path is the sequence of decisions the visitor made. A visitor who lands on a product page, scrolls to the bottom, visits two more products, and leaves without adding anything to cart behaved very differently from a visitor who lands, barely scrolls, and exits within ten seconds. The first visitor engaged and didn’t find a reason to commit. The second visitor didn’t engage at all. These are page problems with different causes. The first is a conversion issue: the information was there but didn’t resolve the objection. The second is a relevance or trust issue: the visitor decided quickly that the page wasn’t for them. If you’re seeing a high share of the second pattern on pages that get paid traffic, start with the ad-to-page message match.

Cross-referencing session paths against referral source gives you a sharper picture than either source alone. A visitor from a branded search behaving differently from a visitor from a competitor keyword search on the same product page tells you the page is doing different things for different intent levels. That’s worth investigating before you touch anything.

Separate these two problems before you start: high impressions with no clicks in Google Ads is a pre-page problem. Your title, creative, or bid isn’t winning the click. High clicks with no conversion is a page problem. Fixing one won’t fix the other.

What the first scroll actually shows

Open the page on your phone. A visitor who doesn’t know you gets one scroll before they’ve formed an impression. Look at what’s actually visible in that scroll.

On most product pages, that first view shows a large image and the product title. Price, variant selector, CTA, social proof, and promotional messaging sit below it. By the time the visitor sees any of the information that would help them decide, they’ve already decided.

Check whether price, variant availability, the primary reason to buy over an alternative, and any active promotion are all visible before the visitor has to interact with the page. If they’re below the fold on mobile, a significant portion of your traffic never sees them, regardless of how good they are.

Do the same check on desktop. Mobile and desktop layouts differ, but the question is whether a mobile visitor sees the same decision-critical information in roughly the same scroll position as a desktop visitor. That gap is usually where mobile conversion underperforms.

Read the page as someone who just clicked your ad

When a campaign is running, go to the page the ad sends traffic to and read it as someone who just clicked. Read it as the visitor who saw the ad and landed, not as the person who built the page.

The ad made specific claims: free shipping over $50, limited stock, 20% off, a bundle deal. The visitor clicked because of one of those things. On the page, that claim needs to be visible immediately.

I’ve done this directly across my stores. The implementation I use: a slim banner directly below the header on the PDP, running only when the relevant campaign was active, restating the exact offer language from the ad. The same wording, the same framing, confirmed the moment they landed. The visitor’s first impression is either “I’m in the right place, the offer is real” or a moment of uncertainty where the thing they clicked for isn’t immediately visible. That uncertainty loses a significant share of paid traffic before they’ve read anything else on the page.

Restating a promotion in the same language the ad used reads as confirmation. A different framing of the same offer reads as a different offer, or creates a moment where the visitor has to reconcile what they saw with what they’re seeing now. That reconciliation costs you attention you need to close the sale.

Go through every specific claim your ad makes and check whether it’s visible before the visitor scrolls. Free shipping needs to appear in the trust bar or near the CTA, not only at checkout. Urgency created by the ad needs an inventory or timing signal on the page to sustain it. A percentage discount shown in the ad needs to be reflected in the page price display, not just in a promotional code field at checkout. Every claim the ad makes that the page doesn’t confirm immediately is a gap between why the visitor clicked and what they found when they arrived.

Pull your competitors’ PDPs and run the same check

Auditing your own pages in isolation gives you a partial picture. Pull the PDPs of the two or three competitors your customers are most likely to check before buying, and run the same audit on them.

Look at what their first scroll shows, how they present social proof, what their mobile layout prioritizes, where their CTA sits. If a competitor’s page resolves the purchase decision faster than yours, that’s the specific gap to close.

Your competitors have built and tested these pages against your shared customer. Their PDPs tell you where the real standard sits more accurately than any best-practice article, because what converts in your category for your customer type may differ substantially from general CRO guidance.

Walk the page as three different visitors

Your product page serves visitors with fundamentally different questions depending on how they found you. Walk through it three times: as a cold paid visitor, as an organic search visitor, and as a returning customer.

Three visitor types reading a Shopify product page: cold paid ad visitor, organic search visitor, and returning customer, each with different questions and trust levels

The cold paid visitor needs credibility before they need product information. They found you through an ad, which means they’re aware they were targeted. Before they read a single product detail, they’re asking whether this store is real, whether other people have bought from it, and what happens if the product isn’t right. Reviews need to be visible without scrolling. Return policy needs to be stated plainly, not hidden in a footer link. Shipping terms need to be clear. If none of that is visible in the first scroll, the product information below it is being read by a visitor who hasn’t yet decided whether to trust the page they’re on.

The organic search visitor came with intent. They typed something specific, your page appeared, and they clicked because it looked relevant. Their question is fit: is this the right version of what I searched for, and does this store have it at a price and with terms that make sense? They’re comparing your page against other results they have open. The page needs to confirm fit fast: specific attributes in the title and description that match how they searched, clear variant availability, and enough product detail to distinguish this from the alternatives they’re considering. Credibility still matters for this visitor but it’s secondary to fit. If the page doesn’t answer the fit question in the first scroll, they go back to search results.

The returning customer already trusts you. Their question is whether this particular product is worth it right now. They don’t need the trust signals a cold visitor needs. They need product details and a clear reason to act: an active promotion visible near the CTA, accurate stock levels, and a description specific enough to confirm this is the right choice. The urgency that feels manipulative to a cold visitor feels useful to someone who’s already decided they want something from you and is just deciding whether now is the right time.

When organic traffic drops on a PDP

A drop in organic sessions to a product page shifts the investigation from conversion to content. Ask whether the page title matches how buyers search for this product. Check whether the description is thin or duplicated from the vendor. Confirm that structured data is populated and that the specific attributes buyers search for are actually in the copy.

SEO problems on a PDP are almost always missing content. Buyers search for specific attributes: material, dimensions, compatibility, use case. If those attributes aren’t on the page, the page doesn’t rank for those queries. If organic traffic dropped after a page edit, look at what was removed. Copy cut for design reasons is often what was driving search relevance.

Where to start

Open your highest-traffic product page on your phone and look at the first scroll. Would a visitor who doesn’t know your store see enough there to stay and keep reading, or is the information that would convince them below the fold?

Then open your top competitor’s equivalent page and run the same check. One of those pages resolves the purchase question faster. Make sure it’s yours.

What does your highest-traffic product page show in the first scroll on mobile? Is the information that would convince a first-time visitor visible before they have to interact with the page?

Your Shopify Catalog Is the Foundation Everything Else Runs On

TLDR

Your Shopify catalog is the data layer everything else in your store runs on.
A clean catalog means customers find products, promotions apply correctly, and your data reflects reality.
A messy one means broken filters, wrong collections, promotions that apply to half of what they should, and reports you can’t trust.
Single-brand stores have a discipline problem. Multi-brand retailers have a systems problem.
The work pays back in discovery, conversion, and scale every day your store is live.

Most merchants treat catalog quality as a maintenance task, something to get to eventually, between launches, when there’s time. Your catalog isn’t a filing system sitting quietly in the background. It’s the data layer that search, filtering, collections, promotions, reporting, and every third-party app in your stack runs on. When it’s inconsistent, all of those things are unreliable, and the failures show up downstream in ways that are hard to trace back to the source.

A well-structured catalog pays back every time a customer finds what they’re looking for, every time a promotion applies to everything it should, every time a report actually reflects what’s happening in the business. That’s not a one-time benefit. It’s the baseline your store operates from.

What a clean catalog actually buys you

The most direct payoff is discoverability. Shopify’s storefront search runs on product titles, tags, and product types. If those fields are inconsistent: tags in different cases, product types that vary by whoever entered the product, titles that follow no particular structure, search returns unreliable results and filters show duplicates or gaps. Customers who can’t find what they’re looking for don’t contact support. They go somewhere else.

Collections and promotions are where the cost becomes visible in revenue. A smart collection built on a tag only pulls the products where that exact tag value exists. A discount rule targeting a product type only applies where that product type is spelled and cased exactly right. These aren’t edge cases. They’re standard Shopify behavior. A messy catalog means promotions are quietly applying to 60% of what they should, and the gap is invisible until a customer notices or you run a reconciliation.

Reporting is the quietest casualty. Inconsistent product types make sales-by-category reports noise. Four different spellings of the same vendor name mean filtering by vendor gives partial data. Decisions made on those numbers aren’t wrong in obvious ways. They’re miscalibrated in ways that compound over time.

Every tool in your stack that personalizes recommendations, powers search, or automates merchandising learns from your catalog data. Feed it inconsistent data and it produces worse results. The app works correctly. It’s the inputs that are wrong.

The discipline problem versus the systems problem

For a single-brand merchant, catalog quality is a discipline problem. One product structure, one vendor, one set of conventions. The challenge is applying them consistently as products get added quickly, as the team grows, as campaigns create temporary tags that never get cleaned up. Clear standards, applied consistently, get you most of the way there without a lot of infrastructure.

For a multi-brand retailer, it’s a systems problem of a different order. Every vendor has their own title structure, their own tagging logic, their own idea of what a product type is. A pet goods store carrying forty brands receives forty different product data formats and has to normalize all of them into one coherent catalog. A pop culture merchandise store carrying licensed products from dozens of IP holders has the same challenge. The catalog debt compounds with every new vendor, and without a system for normalizing incoming data, you’re always behind.

The stakes scale accordingly. For a single-brand store, a messy catalog is an inefficiency. For a multi-brand retailer, it’s a structural problem that affects every layer of the business: what customers can find, which promotions work, what the data actually says. The mechanics of what breaks and how to audit it are covered in depth here.

How catalog quality connects to search and AI discovery

Google’s product search depends on structured, consistent product data to index and surface your products correctly. Inconsistent product types send mixed category signals. Titles written for internal conventions rather than how people search lose impression share. Missing or incorrect GTINs mean your products compete poorly against other retailers listing the same item with clean data.

At Google Marketing Live earlier this month, Google announced AI agents that can complete purchases on behalf of users. Those agents navigate stores by reading product data, and a messy catalog is exactly what they can’t parse. What that shift means for merchants is worth understanding in full, but the catalog implication is direct: structured data isn’t just good housekeeping anymore.

Why this work keeps getting skipped and what it actually returns

Catalog work gets deprioritized because the cost of a messy catalog is distributed and invisible, while the work of fixing it is concentrated and visible. That framing has it backwards. The distributed cost is real and it’s ongoing. It shows up as conversion rate underperformance you can’t explain, promotions that require customer service recovery, and reports you’ve quietly stopped trusting.

Customers who find what they’re looking for convert. Promotions that apply correctly don’t generate exceptions. Reports that reflect reality support better decisions about inventory, pricing, and what to stock next. Apps that learn from clean data make better recommendations. A catalog structured for search is one that Google and AI shopping tools can index and surface accurately. None of that shows up as a single line item, but all of it is measurable if you look at the right things.

Catalog audits and product onboarding are two of the tasks I’ve handed to Claude across my stores, including the multi-brand catalogs where this problem is most acute.

Pull up your storefront filter and search your best-selling category. Does every option show exactly the products it should? Are there duplicates, missing options, or results that don’t belong?

What’s the thing in your store that keeps behaving strangely that you haven’t traced back to the catalog yet?

The Shopify Tasks I’ve Handed to Claude (And the Ones I Haven’t)

TLDR

Setting up new products used to take most of a day, sometimes more depending on how many came in at once.
Claude handles the repetitive parts well: titles, tags, collections, menus, in the right order.
It can’t figure out your rules on its own. You have to encode them first.
You don’t need years of systems in place to start. One rule, one product type, is enough.
What you get on the other side is an operator who never forgets what you told it.

Setting up a new product used to be an all-day job, sometimes longer depending on how many new SKUs came in at once. Optimize the title, map to the right tags and product type, create the collection if it doesn’t exist, wire it into the right menus, check that every attribute follows the vendor’s conventions. With ten new products from two different vendors, that work spills into the next morning and products sit unpublished while the backlog grows.

I run stores with very different catalogs: dog goods and accessories, and pop culture merchandise. They’re all mine, run at different times, and each has its own vendors, naming conventions, and rules for nearly everything. The catalog work that used to pile up is now something I hand off to Claude and review rather than build from scratch. But it took more setup than I expected, and it’s worth being honest about what that setup actually involves.

What made it possible was Claude Code and the ability to build a custom MCP (Model Context Protocol) server: a direct connection between Claude and the store’s Admin API. I built mine before Shopify launched their official connector, and it has capabilities that connector doesn’t: full catalog scanning without hitting token limits, tag dependency checking across smart collections before any changes are made, theme file searching to catch hardcoded references, metafield and metaobject read/write, sales data access, and a built-in dry-run mode so nothing gets committed without explicit approval. Other AI tools I tried couldn’t parse large product exports accurately or connect to Shopify at all. Everything was copy-paste, which defeats the point when you’re trying to operate at scale.

What Claude actually handles in my Shopify store

Product onboarding is the clearest win. New product comes in, I run it through the workflow: title gets structured correctly, tags get mapped to the standardized set, product type gets assigned, collection gets created or the product gets added to the right existing one, menu placement gets handled. What used to eat most of a day now takes a fraction of it, and the product goes live without sitting in a queue.

Order operations is the other area. I built an internal platform to track orders across one of my stores, and getting Claude to read order status correctly required getting specific about definitions. What does “fulfilled” mean in this store’s workflow? What counts as pending? Those aren’t obvious answers, and Claude can’t infer them from context. Once they’re defined and documented, it handles them correctly every time.

Catalog audits are where it genuinely surprises me. Spotting inconsistencies across a large catalog: products where the title doesn’t follow the right structure, tags that don’t match the standardized set, attributes that conflict. That’s tedious work I used to do manually in batches. Claude can scan the whole catalog and surface the issues faster than I can scroll through a spreadsheet.

Why I never let Claude touch the store without a checkpoint

This isn’t a one-prompt operation. I run it with checkpoints built in. Before anything gets written to the store, I review the plan. Before a bulk update runs, I spot-check a sample of the output. There are approval steps before anything commits. The write guards in the MCP reinforce this too: dry-run is the default, and writes require explicit sign-off. The goal is to move faster without losing control of what’s actually happening in the store.

Matrixify is part of how this works in practice. When Claude prepares a bulk update, it formats the output as a Matrixify-ready spreadsheet. That file is the checkpoint. A spreadsheet is easy to review, easy to spot-check, and easy to understand at a glance before anything goes live. Once I sign off, it uploads to Matrixify and the changes execute. The format isn’t just a technical requirement. It makes the review step something you can actually do.

The first few passes with a new vendor or product type reveal gaps in what I explained, not failures in Claude. When an output is wrong, it’s almost always because I didn’t account for something in the rules I gave it. That’s useful feedback. It forces you to make your own logic explicit in a way that running on instinct never does.

What you have to teach Claude before it’s useful

None of this worked out of the box. The product title structure I use isn’t arbitrary: there are rules per vendor, rules per product type, edge cases learned from years of managing these catalogs. I can’t tell Claude to “optimize product titles” and expect it to know what I mean. I have to explain the structure, give examples, explain why the rules exist, and document the exceptions.

The same is true for tags. My tag taxonomy is standardized across stores with very different product types. Claude doesn’t know that taxonomy. I had to build it out, explain the mapping logic, and make sure the patterns were clear enough that it could apply them consistently to products it had never seen.

How my old Shopify SOPs became Claude’s training material

I’d already done a version of the groundwork before Claude was part of the picture.

Years of bulk importing and updating products through tools like Matrixify forces you to think in systems. Every time I mapped a new vendor’s catalog to my store’s structure, I had to make decisions: what does this product title become, which tags apply, what product type does this map to. Do that enough times and you start writing it down, not because you’re building infrastructure, but because you can only hold so much in your head. The result was a set of mini SOPs. Practical notes to my future self: here’s how vendor X structures their titles, here’s the mapping logic, here’s what to watch for.

I’d also built out the underlying frameworks those SOPs mapped to. A tag taxonomy with real logic behind it. A product type hierarchy I’d designed deliberately, thinking about SEO, storefront filter conditions, and how customers actually navigate a catalog. I’ve been doing SEO since 2007, and those fundamentals shaped how I structured everything long before AI was part of the workflow.

When I started using Claude for catalog work, those frameworks became the training material. I wasn’t asking it to invent structure. I was handing it structure that already existed and asking it to apply it consistently at scale.

Claude also pressure-tested what I’d built. Once it was running catalog work through my rules, it surfaced patterns I hadn’t explicitly documented: vendor quirks I knew intuitively but hadn’t written down, edge cases that fell between two rules. Some confirmed the logic I already had. Some prompted me to go back and tighten it. The frameworks I have now are more precise than the ones I started with, partly because explaining them to Claude forced me to make the implicit explicit.

How to start using Claude for Shopify ops today

You don’t need the same foundation in place to get going. The SOPs I handed Claude were built one vendor at a time, one problem at a time.

Pick your best-selling product type. Write down how a title should be structured for it and explain why. That’s one rule. Give it to Claude and ask it to apply that rule to a product that doesn’t currently follow it. The gaps in your explanation become the next rule. You build it forward from there, the same way I did, just with Claude in the loop from the start instead of added later.

The starting point is one thing you know well enough to write down. Most merchants already know more than they’ve documented.

The Shopify decisions I still make myself

Anything that requires judgment about the business: what to stock, how to price it, which vendor relationships are worth maintaining, what a customer complaint is actually telling me. Claude is good at applying rules consistently at scale. It’s not good at deciding what the rules should be.

The setup itself is also still on me. Encoding your catalog logic, your operational definitions, your store-specific conventions takes real work. It’s not a one-time cost either, because the rules evolve and the memory needs to stay current. But it compounds. Every hour spent making the rules clearer pays back every time a product gets processed correctly without your hands on it.

Claude does what you encode. If you’ve encoded your actual rules, it works well. If you haven’t, you get generic output that doesn’t fit how your store actually runs.

Shopify’s Managed Payment Methods Are Worth Knowing About Before You Enable Them

TLDR

Shopify’s new managed payment methods feature automatically activates local payment options and personalizes checkout order based on customer location.
It requires Shopify Network Intelligence, which means your store contributes customer behavior data to Shopify’s cross-merchant data pool.
For US-only merchants, the conversion upside is minimal and you can ignore it for now.
For merchants with EU or international traffic, manually activating the relevant local payment methods gets you most of the benefit without the data trade-off.
Before opting in, understand what SNI is because the feature depends on it and turning it off later requires cleanup.

Shopify announced managed payment methods this week, and the pitch is simple enough: enable the feature and Shopify automatically activates local payment methods for the regions where you sell, then dynamically orders them at checkout based on what’s most likely to convert for each customer. It sounds like a clean, low-effort win, and for a lot of merchants it probably is, but there’s one dependency baked into it that’s worth understanding before you flip the switch.

What it actually does

When you enable managed payment methods, local payment methods get activated automatically based on where your customers are, so buyers in Belgium see Bancontact at checkout, buyers in Poland see BLIK, buyers in the Netherlands see iDEAL, and so on across the markets where Shopify has mapped local payment preferences. These aren’t obscure alternatives. They’re the dominant payment methods in those markets, and card-only checkout converts meaningfully worse there, so if you’ve been selling into those regions without them you’ve been losing sales you couldn’t see in your data.

The feature also personalizes checkout ordering, meaning the payment methods most likely to result in a completed purchase are shown first for each customer based on their location, purchase history, and aggregated conversion data from across Shopify’s merchant network. Your existing settings are left alone: manually disabled methods stay off, existing checkout customizations aren’t overwritten, and there’s no additional fee on top of the standard Shopify Payments transaction rates you’re already paying.

The part worth slowing down on

To use managed payment methods, Shopify Network Intelligence has to be active in your Customer Privacy settings, and that’s the part most merchants will click past without thinking about it.

SNI is Shopify’s cross-merchant behavioral data network, and when it’s on your store contributes customer behavior data including browsing patterns, purchase behavior, and payment preferences into Shopify’s aggregated pool, which is what powers the personalization. That’s a different relationship with your customer data than most of what happens in your admin, and it’s worth being clear-eyed about before you opt in rather than after.

Shopify is transparent that the data is anonymized and aggregated, and that’s genuinely true, but a few practical things follow from it. In the EU, SNI requires proper cookie consent handling under GDPR, so if a customer opts out and your consent implementation doesn’t catch it correctly you have compliance exposure that’s easy to miss until it isn’t. New payment methods can also be activated automatically as Shopify adds support for them and you get notified, but they go live before you explicitly approve them, which matters if you have a tightly controlled checkout or specific compliance requirements around which payment options appear. And if you disable SNI later, managed payment methods shuts off with it, meaning any methods that were automatically activated stay on but you’re back to managing them manually, which is fine but requires cleanup you might not be anticipating.

Whether it makes sense for your store

For merchants selling primarily in the US, the honest answer is that there’s not much here worth acting on right now. Bancontact and iDEAL aren’t relevant for US buyers, standard card and digital wallet coverage already handles the US market well, and the checkout ordering personalization adds value at the margin but not enough to justify enabling SNI if you wouldn’t otherwise.

For merchants with real volume from EU or international markets, local payment methods do move the needle on conversion and that’s well documented enough to take seriously. The question is whether you need managed payment methods specifically to get that benefit, and you don’t. You can go to Settings > Payments right now and manually activate the local methods relevant to your actual markets, it takes fifteen minutes, and you get the same payment method coverage without contributing to SNI. You lose the dynamic checkout ordering optimization, but for most merchants that’s a reasonable trade.

If you use Managed Markets, cross-border transactions continue running through Global-E and aren’t affected by this feature at all. Managed payment methods only applies to domestic transactions, so if the majority of your international volume runs through Managed Markets the upside here is smaller than the announcement makes it sound.

What to actually do

If you want local payment method coverage without enabling SNI, go to Settings > Payments, look at where your actual customer volume comes from, and manually activate the relevant methods for those markets. That’s the whole job, no trade-off required.

If SNI is already on and you’re comfortable with it, managed payment methods is genuinely useful and the checkout personalization is a real conversion tool worth having. Just keep an eye on what gets automatically activated as Shopify adds new methods over time.

If you’re US-focused, nothing here is urgent.

Your Customer Has Already Decided Before They Hit Your Store

TLDR

By the time someone clicks through to your product page from an AI search result, they have already done the research.
Your product page is not convincing them. It is confirming a decision they have nearly made.
If your page contradicts what the AI told them, or makes them re-learn the product, you lose the sale to whoever loads faster.
The job of a PDP in AI search is to remove the last two or three objections standing between a near-decision and a purchase.
Specific proof beats star ratings. Confirmation beats persuasion.

At Google Marketing Live last week, Google’s VP of Ads demoed what AI search looks like in practice. She searched for a walking pad for her home office, loves hiking, wanted something reliable and quiet, and Google returned a ranked comparison table with personalized recommendations. Then she said 75% of people report making faster, more confident purchase decisions when they use AI overviews and AI mode, and landed on the line that should change how you think about your product pages: by the time they visit your site, they’re ready to buy.

That sentence has a practical implication most merchants haven’t caught up with yet.

The research phase is gone by the time they click

A year ago, a customer shopping for a walking pad would open ten tabs. They’d read Reddit threads, watch YouTube reviews, cross-reference specs on two or three retailer sites, and eventually land somewhere to buy. Your product page had to do real persuasion work. It was meeting someone mid-consideration.

That journey still happens, but increasingly it’s happening inside a single AI search session before anyone clicks anything. The AI reads the reviews, surfaces the comparisons, answers the follow-up questions, and hands the buyer a shortlist. By the time they tap through to your store, the research is done. They’re not deciding. They’re confirming.

This is a different customer than the one your product page was built for.

What a confirmation page needs to do

A page built to convince starts with the product story. It builds a case. It addresses broad objections. It educates.

A page built to confirm does something narrower. It answers the specific questions a near-buyer still has. It matches what the AI already told them about you. It gets out of the way.

The practical difference shows up in a few places.

Match what the AI said. If an AI overview described your product as “quiet and durable, good for small spaces,” and your product page leads with “the ultimate home office fitness solution,” you’ve created a mismatch. The buyer arrived expecting confirmation and found a different pitch. That gap breeds doubt. Your title, your opening description, your key specs: all of it needs to reflect how your product actually shows up in AI search results. Search your own products in AI mode. Read what Google says about you. Write to that.

Answer the last objections, near the buy button. A buyer this far along isn’t wondering what a walking pad is. They’re wondering whether yours ships fast enough, whether it’ll fit their space, whether the motor will be audible on a video call. Those are the last two or three things standing between them and the purchase. Put the answers near the button, not buried in an accordion three scrolls down. A tight FAQ block right above the add-to-cart, built from your actual support ticket themes, does more work at this stage than a long features section.

Specific proof over star ratings. A 4.8 with 200 reviews says nothing to someone in confirmation mode. “Whisper-quiet at 3mph, use it on calls” from a verified buyer says exactly what they needed to hear. Surface the review content that matches the specific reasons people buy your product: the quotes that confirm the claim, not just the aggregate score.

Speed. A buyer in confirmation mode is one back-button away from the next result. If your page loads slowly, if they have to scroll past a hero video to find specs, if the size guide is a PDF download, they leave. Not because they changed their mind about the product. Because friction at the confirmation stage feels like a signal that something is off.

What this doesn’t mean

It doesn’t mean strip your product pages down to nothing. Buyers who arrive from other channels (email, paid social, direct) still need more context. The goal is not to remove the product story. It’s to front-load the confirmation elements so the near-ready buyer can find them without effort, and leave the fuller context available for everyone else.

It also doesn’t mean your page should just repeat whatever the AI said verbatim. The AI pulled its description from your content. If that content is thin or generic, the AI’s summary will be thin and generic, and the buyer who confirmed against a thin summary arrives with low confidence. The answer is better source content, which is also the SEO answer, and the subject of the next post.

The practical version of this

Open your best-selling product page. Search for that product in Google AI mode. Read what it says about you. Then ask: does my page confirm that, or does it start over?

Why Your Product Page Is Losing Sales You Will Never See

TLDR

Your page is the product experience, not a description of it
Shop competitors before rewriting anything
Specific copy, contextual images, and honest reviews move buyers more than design
Objection handlers belong near the buy button, not the footer

For most buyers, your product page is your product. They will never hold it, try it, or smell it before deciding whether to hand over money. Whatever you put on that page is the entire experience — and it will be judged with the same standard they would apply to the physical thing. Would you ship a product that was not finished, had not been photographed properly, and came with instructions written by someone who had never used it? The product page gets that treatment constantly, from stores that would never cut those corners on the product itself.

Getting it right is not a design problem or a copywriting problem. It is a readiness problem. Your product page needs to be as ready to face a customer as the product it is selling.

What does your product page actually answer?

A buyer landing on your product page is running through three questions whether they realize it or not: does this do what I need, do I trust this seller, and is the price worth it. If your page does not answer all three clearly and quickly, the sale does not happen — and you will not get a reason why.

Most merchants optimize for the first question and neglect the other two. The copy explains what the product is. The images show what it looks like. But trust and value justification get left to a 4.8 star rating and a footer link to the returns policy.

Shop your competitors before you rewrite anything

Open five stores in your category and spend thirty minutes buying nothing. Browse the way a real customer would — skeptically, quickly, with a tab open to a competitor the whole time.

The stores converting well tend to be doing similar things. The ones that are not are usually missing the same things in the same order, as if there is a shared template for a mediocre product page and half the industry downloaded it. Pay attention to how they handle the questions buyers always have: does this fit, what does it actually look like in real life, what happens if it is wrong. That thirty minutes will tell you more about your own page than a month of staring at your analytics dashboard hoping it develops a personality.

Is your copy describing the product or helping someone picture owning it?

Most product descriptions explain what the product is, which is not the job. The job is to help someone picture having it — using it, wearing it, installing it, solving the problem they came to solve.

Powerful and flexible means nothing to someone deciding whether to spend $80. Works with any Shopify theme, no code required means something. Specific beats impressive. Write for the person who is already interested but not yet sold — they do not need an introduction, they need the one detail that tips them over.

Do your images actually show the product?

A buyer cannot touch the product, so your images are the closest thing to handing it to them. Showing it on a white background is a starting point, not a strategy. Show it in use. Show scale — next to something familiar. Show the detail someone would check in person: the stitching, the finish, the way it opens, the size of the ports.

If your product solves a problem, show the before. If it has a learning curve, show someone using it correctly. Video helps more than most merchants expect — even fifteen seconds of someone actually using the product answers questions people are too passive to type into a search bar.

Are your reviews doing any work?

A 4.8 average with forty reviews that say great product, fast shipping proves nothing to a hesitant buyer. That is background noise wearing a badge.

What moves someone is a review like: I had tried two similar products and returned both — kept this one. Specific, from someone who doubted it first. Surface your most useful reviews near the buy button rather than burying them below the fold. And change how you ask for them: instead of leave a review, ask customers what made them decide to keep it. You will get very different answers.

Where are your objection handlers living?

Returns policy. Shipping time. Warranty. Who made this and why. Merchants consistently put these in the footer, between the sitemap and the cookie policy, where no one making a buying decision will ever find them in time. Buyers look for this information right before they commit, not after.

If your return window is generous, say so on the product page. If you ship within 24 hours, say that too. These are not legal disclosures — they are the last things standing between a hesitant buyer and a completed order, and they belong somewhere a hesitant buyer will actually see them.

One fix to make this week

Open your best-selling product page, spend ten minutes shopping two competitors in your category, and come back with one question: what are they answering that you are not. That gap is where your next sale is hiding.

Shopify B2B Is Now for Everyone. Three Catalogs, Though.

TLDR

Shopify opened native B2B to all paid plans on April 2, 2026: company profiles, payment terms, volume pricing, up to 3 catalogs
Three catalogs works for simple wholesale setups, not for merchants running multiple tiers, markets, or customer segments
The features that handle real complexity stayed behind the Plus wall
If your wholesale operation has grown past basic, the gap between what is included and what you need is real

Shopify opening its native B2B features to every paid plan is a genuine win. Company profiles, payment terms up to Net 90, volume pricing, ACH payments in the US, vaulted credit cards: these are real tools that cost nothing extra and used to require a Plus subscription. For merchants just getting started with wholesale, this is a meaningful unlock.

The three-catalog limit is where it gets complicated.

What three catalogs actually gives you

A catalog in Shopify B2B controls pricing for a group of buyers. You create one, assign it to a company or market, and those buyers see prices specific to them. Three of those, free, across your entire store.

For a merchant with a straightforward wholesale setup, say a single wholesale tier at a fixed discount, three catalogs is more than enough. A retail catalog, a wholesale catalog, and a distributor catalog covers a lot of ground without hitting the ceiling.

The limit starts showing its edges when your business is more layered than that.

Where three runs out

Shopify three catalogs are shared across your entire store, across all B2B markets combined. A US operation using one catalog each for Bronze, Silver, and Gold pricing tiers has used all three. There is nothing left for a UK market, a Canada-specific price list, a distributor channel with different margins, or a key account that negotiated their own terms.

Most wholesale businesses are not simple. Pricing reflects relationships, minimums, geography, and negotiation history. Three catalogs handles the clean version of that. The messier, more realistic version runs out of room quickly.

The other features worth knowing

Beyond catalogs, the non-Plus B2B rollout includes some genuinely useful additions. Company profiles let you organize wholesale buyers properly, with multiple locations per company, each carrying their own shipping address, payment terms, and tax settings. Payment terms cover Net 7 through Net 90. Volume pricing lets you set quantity-based discounts at the variant level.

What stayed Plus-only: unlimited catalogs, partial payments, and deposits. Those are the features that handle the operational reality of larger wholesale accounts, progress payments on big orders, deposits on custom work, pricing structures that do not fit into three buckets.

The honest read

Shopify built a solid foundation for wholesale on non-Plus plans. If you are new to B2B or your wholesale channel is a secondary revenue stream with a simple structure, the native tools may cover everything you need.

If wholesale is a primary channel, if you have multiple customer tiers, sell across markets, or manage accounts with negotiated pricing, you will find the edges of this feature set faster than expected. The platform gives you the starting point. Scaling past it requires more than three catalogs.

What that looks like in practice, and what merchants are actually doing to work around it, is what we will get into next. It is also, not coincidentally, what led us to start building something of our own.