How to fix malformed product URLs in Google Shopping

A product link needs a complete supported URL. Fix malformed source values while preserving the path and parameters that identify the correct offer.

Reviewed October 4, 2026 · Independent guidance · Static feed check with contextual limitations

What does this issue mean?

The link attribute should contain a HTTP or HTTPS offer URL, not a relative slug, an email address, a local file path or a HTML anchor element. URL parsing can detect these basic mistakes. It cannot establish that the destination is relevant, purchasable, crawlable or consistent with the feed’s price and availability.

Why this happens

Problems often come from exporting a handle without the storefront base URL, inserting whitespace around the address, or concatenating domains and paths incorrectly. Tracking rules can create broken query strings. Signed URLs and variant parameters may be significant, so a generic URL normalizer should not rewrite them casually.

How to diagnose and fix it

1. Compare the exported link with the actual public product URL for the same offer.
2. Use the supported protocol and correct storefront hostname, excluding embedded credentials and administration URLs.
3. Preserve variant selection and other meaningful parameters; verify encoded characters instead of deleting them.
4. Open the final address in a fresh session and rescan the regenerated feed.

Before and after example

The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.

Before

link = products/ceramic-mug

After review

link = https://example.com/products/ceramic-mug

Feed Doctor validates syntax and flags HTTP as a recommendation only. It does not automatically switch protocols, remove tracking parameters or crawl the destination to promise eligibility.

Shopify fix

Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies link. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.

Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.

WooCommerce fix

Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.

Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.

Verify the repair before submitting

Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.

Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.

Frequently asked questions

Related feed issues

• How to fix missing product links in Merchant Center
• How to investigate a product page unavailable error
• How to investigate price mismatch in Merchant Center

Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.