Google Shopping Link Attribute: Requirements, Best Practices & Examples

What is the link attribute?

The link attribute contains the URL of the landing page that shoppers reach when they click your Shopping ad or free listing. It is one of the three most critical required attributes (alongside title and price) because it is the entry point for every conversion your Shopping campaign can drive. A broken, mismatched, or poorly optimised link directly translates to wasted ad spend, product disapprovals, and lost revenue.

Beyond being a click destination, the link URL is actively crawled by Google to verify that what you advertise matches what the landing page shows. This means the link attribute is not just about directing traffic — it’s about maintaining data integrity between your feed and your website. Google’s crawler checks price, availability, title match, and page accessibility, and disapproves products where discrepancies are found.

Technical specifications

Where it displays

• Shopping Ads — Every click on a Shopping ad sends the shopper to the link URL (or ads_redirect URL if set). The displayed domain in the ad (“example.com”) is extracted from this URL. Shoppers see the domain but not the full URL in most ad formats.

• Free Product Listings — In the Shopping tab, free listing clicks also use the link attribute as the click destination. The same URL matching and crawl verification requirements apply to free listings as to paid ads.

• Dynamic Remarketing — Google uses the product landing page URL to associate user behaviour signals (page views, add-to-cart events) with specific products for remarketing audience building. The URL must match the page your remarketing tag fires on.

• Google Actions / Buy on Google — For merchants participating in Buy on Google, the link serves as a fallback destination for transactions not completed within Google’s ecosystem.

Rules

• HTTPS required for Shopping ads — HTTP URLs cause automatic disapproval for paid placements. SSL certificate must be valid (not expired, not self-signed).

• Must resolve to the specific product page — The URL must return a page showing the exact product advertised, not a category page, search results page, or homepage.

• Must return HTTP 200 — 404, 410, 500, or redirect to an error page causes disapproval. Temporary server errors (503) may result in warnings before disapproval.

• Landing page must match feed data — Price, availability, and the general product shown must match what’s in the feed. Google’s crawlers verify this.

• No interstitials or login walls — Pages that require login, age verification pop-ups that block access, or full-page interstitials before showing the product are not permitted.

• No JavaScript-only pages — If the product information is only rendered via JavaScript (not present in the HTML source or structured data), Google’s crawler may not be able to verify feed data, leading to mismatches and disapprovals.

Best practices

Use canonical, clean URLs as your base

The link attribute should point to the canonical URL of the product — the clean, permanent, canonical version without session IDs, pagination parameters, or UI state variables. Keep tracking parameters in ads_redirect or use UTM parameters that don’t affect page content. Clean canonical URLs are more stable across site updates and easier to manage in feed pipelines.

Schema.org structured data alignment

Add Schema.org Product markup to your product pages and keep it synchronized with your feed. When Google’s crawler finds matching structured data (same price, same availability status, same GTIN), it validates your feed data faster and with more confidence, reducing disapproval risk. Products with accurate structured data are less likely to be flagged for mismatches even during brief data synchronization gaps.

URL stability during site migrations

E-commerce platform migrations are the leading cause of mass link-related disapprovals. Planning checklist for migrations:

• Map all existing product URLs to new URLs before cutover

• Implement 301 redirects for all moved product pages immediately at cutover

• Update your Merchant Center feed to new canonical URLs as soon as new URLs are live

• Monitor Merchant Center diagnostics daily for the first 2 weeks post-migration

• Test a sample of 50+ product URLs pre-migration using a URL checking tool

Tracking without contaminating the feed

Impact on performance

• Disapproval rate — Link-related issues are among the top 3 causes of product disapprovals in Merchant Center. A 1% disapproval rate on a 10,000-product feed means 100 products not eligible to show, directly reducing campaign reach and revenue.

• Quality Score and ad rank — Google’s Landing Page Experience component of Quality Score is partially influenced by the landing page quality at the linked URL. Slow, thin, or mismatched landing pages lower Quality Score, increasing CPC at the same ad position.

• Conversion rate — Sending users to the exact product they clicked on (as opposed to a category page or homepage due to broken redirects) can improve conversion rates by 20–40%. Precise landing pages reduce bounce rate and increase purchase intent at arrival.

• Crawl verification latency — After a feed update, Google’s crawlers may take 1–3 days to re-verify product URLs. During this window, products with recent link changes may experience temporary impression drops until the crawl confirms data validity.

Common mistakes

• Using HTTP instead of HTTPS for product URLs — immediate disapproval for paid placements

• Linking to a category or search results page instead of the specific product detail page

• Using session-based URLs (containing SESSIONID= or similar) that expire and result in 404s when crawled

• Not implementing 301 redirects when product URLs change, causing mass 404 disapprovals

• Embedding tracking parameters that alter the page content or trigger different prices for tracking traffic

• Using JavaScript-rendered pages without static HTML equivalents or structured data, making Google’s crawler unable to verify product details

• Pointing multiple product variants to the same URL — all share the same price/availability and Google cannot distinguish them

Pro tips

• Set up automated URL monitoring — Use a server-side URL health check on your top 500 products (by ad spend) that runs daily and alerts on non-200 responses. A broken link caught within hours costs far less than one discovered after 3 days of wasted spend. Tools like Screaming Frog, custom scripts, or GMC feed monitoring services all work.

• Implement Schema.org markup on all product pages — Product schema with accurate price, availability, sku, and gtin lets Google’s crawler cross-reference your feed data against structured data, making mismatches easier to detect and fix — and validated products less likely to be flagged for crawl-time discrepancies.

• Use the ads_redirect attribute for all paid tracking — Keep link as the clean canonical product URL and put all tracking (UTMs, click IDs, redirect chains) in ads_redirect. This makes your feed easier to audit, canonical URLs remain stable for organic/free listing purposes, and tracking changes don’t require feed updates.

• Test links programmatically in your feed generation pipeline — Before submitting a feed update, run a lightweight HEAD request check on all URLs in the feed batch. Anything that returns non-200 should be flagged and investigated before the feed is submitted to Google. This single validation step prevents the majority of link-related disapprovals.