CartVisual
Sign inCreate account

Assets & tasks / PRACTICAL ANSWER

Will a shared product link reopen the color and size shown in my ad?

Check the actual destination with no saved selection. A correct ad can still open the default variant if the link does not preserve the intended option.

Illustrated review route: Will a shared product link reopen the color and size shown in my ad?
Original CartVisual review diagram; illustrative, not a real product or generated result.
01 / WILL A SHARED PRODUCT LINK REOPEN THE COLOR AND SIZE SHOWN IN MY AD?

Define the intended arrival state

A fictional coat ad shows the green medium option. The seller copies the generic coat URL while their browser already has green selected. A new shopper opens it and sees black small. The creative may be accurate, but the arrival state is wrong. Write the expected color, size, image and offer before choosing the destination link.

Google’s variant examples describe single-page and multi-page URL approaches. Use your store’s supported strategy rather than inventing parameters that only look plausible.

02 / WILL A SHARED PRODUCT LINK REOPEN THE COLOR AND SIZE SHOWN IN MY AD?

Replay the link without seller state

CheckExpected stateFailure signal
Initial pageGreen medium selectedDefault black small
Hero imageApproved green coatAnother variant image
OfferCorrect intended variantUnrelated price/availability
Selection controlsReadable chosen optionNo indication of selection

Open the actual shared URL in a fresh anonymous context and allow the page to finish updating. Then verify it on a phone. Do not use a screenshot from the seller’s existing session as proof that every visitor will receive the same state.

  1. Copy the actual campaign URL, including its supported option identifiers.
  2. Open it without the seller’s saved selection; record redirects and the final URL.
  3. Read the selected color/size and compare the hero, price and availability for that exact option.
  4. If the store allows it, add one item to a test cart and inspect the option identity; do not complete a purchase.
  5. Stop the campaign handoff if the cart or destination selects a different item. Record an unavailable option as unavailable, not as an acceptable default.

This is a proposed manual test, not an executed store checkout. A displayed green coat is insufficient when the cart selects black. Ask the store owner to verify its actual variant identifier if the interface is ambiguous.

03 / WILL A SHARED PRODUCT LINK REOPEN THE COLOR AND SIZE SHOWN IN MY AD?

Review the URL implementation

If the store supports variant-specific links, use the documented link and confirm it survives redirects. Ask the developer to review canonical and structured-data relationships for that URL strategy. A marketing team should not apply a blanket canonical rule without understanding whether the product family and selected variants are separate documents.

Keep the campaign URL and approved asset in the creative record. An ad image’s file name does not control which product option the destination selects.

Google’s current variant guidance includes direct preselected URLs that show the correct image, price and availability and allow that variant to be added to the cart. Its single-page ProductGroup approach uses one group canonical; the equally important multi-page approach has a different relationship. A usable campaign deep link therefore does not automatically need a self-canonical, and a group canonical does not excuse a broken selected-option destination.

Keep the human arrival test and the developer’s markup/canonical review as separate records. Use the CTA destination contract for the action promised by the creative, and a change ledger after routing changes.

04 / WILL A SHARED PRODUCT LINK REOPEN THE COLOR AND SIZE SHOWN IN MY AD?

Recheck after store changes

Repeat the arrival-state test after theme changes, product-option edits or redirects. If the intended option is unavailable, revise the campaign deliberately rather than leaving the ad linked to an unrelated default. CartVisual can create the asset; the store controls variant routing and selection. Keep those responsibilities separate when diagnosing the defect.

Published by CartVisualPublished Updated Evidence and editorial policy
SOURCES & SCOPE

Sources and further reading

Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are CartVisual editorial guidance, not independently measured results.

QUESTIONS, ANSWERED

Frequently asked questions

Is my selected browser state enough proof?

No. Test the shared URL without saved selection.

Should I invent a color query parameter?

Use the actual supported store URL strategy.

Can an image file select the store variant?

No. The destination implementation determines arrival state.

Does a working variant URL have to be self-canonical?

That depends on the actual single-page or multi-page product strategy. Verify its selected option and cart separately from canonical and structured-data relationships.

PREPARE ASSETS FOR YOUR NEXT STEP

Create supporting product assets in CartVisual.

Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.

Explore asset creation tools Check pricing and credits