Mismatched domains

What Google requires

The link on your verified domain, the redirect on the link's

Two related requirements. Your link has to be on the domain you have verified and claimed in Merchant Center; a link on another domain raises Mismatched domains. Separately, since the launch of parallel tracking, the domain of any ads_redirect (and mobile_link) has to exactly match the domain of the link.

What Google does

The link mismatch can block; the redirect mismatch disrupts tracking

A link on a domain the account has not verified can disapprove the product — that is the Mismatched domains issue. An ads_redirect whose domain differs from the link is a separate problem: Google requires the domains to match and warns that a mismatch can disrupt tracking, rather than always disapproving the item.

How to fix it by hand

Bring every URL onto the link's verified domain

• Put the link on your verified, claimed Merchant Center domain.
• Set any ads_redirect to exactly the same domain as the link.
• Move tracking that needs a different host into the account's tracking template rather than the feed.

What FeedMender checks today

One check applies, read from the scanner's registry

ads_redirect_domain_mismatch flags where the ads_redirect domain differs from the link domain — the parallel-tracking requirement above. It reads both values from the feed.

• ads_redirect_domain_mismatchblocks

What the scan does not check today: the official Mismatched domains condition itself, which compares the link against your verified Merchant Center account domain. That registered domain is an account setting, not a feed field, so FeedMender cannot read it, cannot confirm a product disapproval on that basis, and does not detect cloaking.

The quicker way

Let the scan compare the domains

Run the free scan and it lists every product whose ads_redirect points at a domain other than the link's. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.

Scan your feed