Short answer: prepare Google Merchant Center for seasonal demand by validating feed truth before increasing campaign pressure. Audit product identifiers, titles, descriptions, images, price, availability, shipping, returns, promotions and landing pages. Submit changes with enough review buffer, save diagnostics/readback evidence and keep a named owner for every exception. Google’s August 19, 2026 holiday episode is the news hook; the current Merchant Center specifications are the operational authority.
This checklist was prepared for 3 September 2026. It does not report a Merchant Center account, inventory, disapproval, sale or performance result. The seasonal decision is whether the feed and storefront can represent the offer accurately when shoppers arrive, not whether a checklist guarantees Shopping visibility.
What to audit first
Google’s 19 August 2026 Ads Decoded episode says the holiday rush is close and discusses product data, shipping, returns and promotions. Start with the products and offers that matter most to the business, but do not hide long-tail errors. Save a dated export of diagnostics, feed processing status, policy warnings and the landing-page checks used to approve the release.
| Area | Check before seasonal changes | Evidence to save |
|---|---|---|
| Feed identity | Stable IDs, correct variants, brand/GTIN where required and one source of truth. | Feed version, processing result and exception list. |
| Offer truth | Price, sale price, currency, availability, shipping and return promises match the storefront. | Product-page and checkout examples plus policy links. |
| Eligibility | Resolve disapprovals, missing attributes and account warnings before a peak. | Diagnostics snapshot and owner for each unresolved issue. |
| Experience | Landing page is crawlable, stable, mobile-usable and able to handle expected load. | URL checks, test order path and change window. |
| Promotions | Offer, code, dates, discount, conditions and price are policy-consistent. | Promotion submission, approval status and redemption test. |
Product, price and availability checks
Use Google’s current product data specification as the field-level source. It lists an item ID limit of 50 characters, a title limit of 150 characters and a description limit of 5,000 characters. It also documents price, currency, images, availability, shipping, expiration and variant requirements. The specification says image requirements of at least 500 by 500 pixels begin enforcement on 31 January 2027; that is a future policy date, not a claim that every account is already failing today.
- ID and variants: keep IDs stable and use the documented item-group relationship for variants. Do not create a new ID every time a seasonal price changes unless the product identity actually changes.
- Titles and descriptions: put the most useful product information first, describe the offer accurately and respect field limits. Avoid stuffing a promotion into a title when the promotion belongs in the promotion programme.
- Price: send the currency and amount that the shopper sees. Check sale-price dates and the checkout total, including material conditions.
- Availability: use the documented
in_stock,out_of_stock,preorderorbackordervalue. The availability guidance requires the feed, landing page and checkout to agree; preorders and backorders need an availability date. - Temporary stock changes: follow the current guidance rather than deleting an item for a short out-of-stock period. Preserve a truthful product state and document the operational reason.
- Images: check the primary image, variant mapping and future size enforcement. Do not copy a third-party image or add an AI-generated featured image to this editorial article.
Promotions, shipping and returns
Promotions are separate from the base product feed. Google’s promotion data specification documents supported sources, promotion IDs, titles, dates and offer conditions. Keep the ID within the documented 50-character limit and avoid spaces or unsupported symbols. Check title limits, promotion start/end times and country/program eligibility. A free-shipping promotion needs a valid redemption code when the policy requires one.
Use the promotion policy page to verify that the offer adds value, the discount/conditions are clear and the price source matches the landing page. The Promotions add-on documentation lists eligibility for Shopping, local inventory and free listings and includes country-specific considerations. Do not claim that a submitted promotion is approved until the account status says so.
Shipping and returns are trust signals as well as feed fields. Confirm handling time, delivery range, shipping cost, return window and exclusions in Merchant Center, on product pages and during checkout. If the offer is limited to a region, customer type or code, say so consistently. A holiday campaign should never promise a delivery date that the fulfilment team cannot support.
Landing pages, structured data and timing
Google’s big-event preparation guidance recommends checking feed timing, product data, promotions and landing pages before a launch. It says an initial feed crawl can take up to 72 hours. It also recommends submitting promotions at least 24 hours before launch; review is often faster but can take longer at peak times. Treat these as planning buffers, not service-level guarantees.
- Check that the product URL returns a stable page and that Googlebot can crawl it. A page that errors or times out can make items ineligible.
- Keep price, availability and key offer information visible and consistent. Avoid changing the page structure in a way that makes values difficult to extract during a seasonal release.
- Confirm that structured data describes the same product, price and availability as the feed and page. Google’s Product structured-data documentation describes eligibility for product snippets and merchant listings; use it with a feed where appropriate.
- Allow time for the first crawl, feed processing, promotion review and fixes. Save the status after every material change.
- Ask the site/fulfilment team to confirm capacity and checkout behavior before budget is raised.
For a feed integration that still uses the older Content API, use the site’s Merchant API migration checklist. That page owns API shutdown and migration decisions. This seasonal page owns operational readiness. Likewise, the Google Ads API release guide covers Ads API version changes, not product-data truth.
A seven-day readiness plan
- Day 1 — baseline: export diagnostics, feed processing, account warnings, top products, offer calendar and landing-page owners.
- Day 2 — product truth: fix IDs, variants, titles, descriptions, price, currency, images and availability. Cross-check a sample at page and checkout.
- Day 3 — delivery and trust: reconcile shipping and return settings with the storefront and fulfilment operation.
- Day 4 — promotions: validate promotion IDs, codes, dates, discounts and conditions. Submit with the documented buffer.
- Day 5 — crawl and structured data: test critical URLs, structured data and mobile checkout; resolve errors before the campaign window.
- Day 6 — readback: confirm processing, approvals and product eligibility. Record unresolved issues and owners; do not silently ship them.
- Day 7 — freeze and monitor: publish a change calendar, set alert ownership and review stock, price, promotion and landing-page health during the seasonal period.
Use the ChatGPT product-feed setup guide when a separate product-feed destination is involved, and the AI for Google Ads guide for campaign automation questions. If seasonal query research creates editorial work, start with the keyword research guide and route the evidence through the research-first SEO brief rather than mixing content planning with feed approval.
Frequently asked questions
How early should I submit a holiday feed?
Start as soon as the product and offer data are stable. Google’s event guidance says an initial feed crawl can take up to 72 hours and recommends submitting promotions at least 24 hours before launch. Those are planning buffers, not guarantees, so leave room for errors and peak-time review.
Should I delete temporarily unavailable products?
Use the current availability guidance. A temporary out-of-stock state is different from deleting a product, and the feed, landing page and checkout must agree. Keep the product state truthful and document when inventory is expected to return.
Is structured data enough without Merchant Center?
Google’s Search documentation says Merchant Center is not mandatory for every general Search appearance, but it is required for some Shopping surfaces. Structured data and a Merchant Center feed are complementary; eligibility is not guaranteed by either one alone.
Will better feed data guarantee more Shopping traffic?
No. Better data can remove preventable eligibility and consistency problems, but the sources reviewed do not establish a traffic or sales guarantee. Measure outcomes separately after the feed is truthful and approved.
Bottom line: use Google’s current specifications as the checklist authority, give feeds and promotions review buffer, reconcile every promise across feed, page and checkout, and save readback evidence before seasonal budgets are changed.
