Blog / Shopify & e-commerce /

The operational handoff between SEO and Shopify merchandising

SEO sends over a ticket that says “optimise collection”. Merchandising reads it, shrugs and files it under later. Three weeks on, the collection page is technically tidy and features products that are out of stock, while a genuinely valuable product group stays buried.

SEO can recommend a collection structure, but merchandising knows the assortment, the stock and the commercial context. If the two teams work from separate queues, both sides lose. A practical handoff spells out what SEO needs, what merchandising controls and how a decision becomes a live change.

Share the right evidence

SEO brings search intent, landing-page performance, crawl findings and internal-link observations. Merchandising confirms product eligibility, availability, seasonality and category logic. Neither view replaces the other. Put the evidence in one shared brief: the affected collection, the question, the recommendation, your confidence and the decision you need.

Clarify responsibilities

Agree who owns collection names, product assignment, copy, filters and release timing. Note which changes need supplier or management approval. If a recommendation depends on stock or margin data, use approved channels and access controls. And skip the vague ticket. “Optimise collection” tells nobody what to do. Explain the outcome you want and which part needs a merchandiser’s judgement.

Close the loop

After the change goes live, check the collection the way a shopper would. Do the products, links, filters and supporting copy match the plan? Share what shipped and what was deferred, then revisit the evidence after a sensible period.

Make the handoff small and regular

A short weekly slot beats a long quarterly meeting. Bring three or four collections, the evidence for each and one decision per collection. Merchandising can say yes, no or not yet, with a reason. I prefer an honest “not yet, the range changes next month” to a quiet delay.

Keep a running list of what was agreed, who owns it and when it will be checked. It doesn’t need tooling. A shared sheet works, as long as both teams update it.

Agree what “done” means

Decide up front what a finished change looks like. For a collection, that might be the right products in the right order, a clear heading and intro, working filters, and internal links from related pages. Write it in the brief so neither side has to guess. It also makes the follow-up check quick, because you’re ticking off a list instead of arguing about taste.

Apply the review to one real case

Define what a finished handoff changes for the shopper, not just what work each team did. Use the same scope and definitions across examples and note what you left out, so one collection doesn’t pass for the whole catalogue.

Follow one real collection from the brief to the live page, and check what a visitor can understand or do without anyone explaining it. Before acting on a recommendation, confirm which source holds the underlying fact and whether it’s current. A copied export may describe an earlier range or configuration.

Otherwise a sound recommendation stalls between queues. Make the trade-offs visible too: accuracy against speed, coverage against upkeep, simplicity against a useful exception. Treat collections that share a template differently from collections that share a shopper need.

Check the result where customers see it, because imports, apps, caching or theme behaviour can alter an approved change. When SEO and merchandising data conflict, compare timestamps, definitions and ownership before choosing a value. The gap may point to a process problem, not an error.

Keep sensitive commercial details out of shared notes and link to the approved system instead. If the information is incomplete, I’d rather run a small reversible test than apply a sitewide rule, especially where a wrong change could reach several customer journeys. Allow an exception only for a real operational problem, and write down its boundary. When you close a task, check nearby content that depends on the same facts, such as feeds, support answers and linked pages.

Ask a merchandiser to review one example without the background conversation. If they can follow the evidence and explain the next action, the handoff is clear enough to keep. If not, fix it before it’s reused. Make sure whoever owns the collection knows where the current guidance lives and how to restore the previous state.

What information would make your SEO-to-merchandising handoff easier to act on?