{"id":1468,"date":"2026-06-16T09:00:00","date_gmt":"2026-06-16T14:00:00","guid":{"rendered":"https:\/\/tolinku.com\/blog\/?p=1468"},"modified":"2026-03-07T03:49:26","modified_gmt":"2026-03-07T08:49:26","slug":"canonical-urls-app-content","status":"publish","type":"post","link":"https:\/\/tolinku.com\/blog\/canonical-urls-app-content\/","title":{"rendered":"Canonical URLs for App Content: Avoiding Duplicate Content"},"content":{"rendered":"\n

When your app content exists on the web, it often lives at multiple URLs. Your website has the content page, your deep link domain has a redirect URL, and your app store listing has a preview page. Search engines see each URL as a separate page. Without canonical tags<\/a>, they split ranking signals across these duplicates, weakening your search performance.<\/p>\n\n\n\n

This guide covers how to set canonical URLs correctly for app content and deep link domains. For deep link SEO benefits, see SEO benefits of deep linking<\/a>. For app landing page optimization, see SEO for app landing pages<\/a>.<\/p>\n\n\n\n

Where Duplicate Content Happens<\/h2>\n\n\n\n

Multiple URL Patterns for the Same Content<\/h3>\n\n\n\n

Your product page might be accessible at several URLs:<\/p>\n\n\n\n

https:\/\/www.yourapp.com\/products\/shoes-x          \u2190 Website URL (canonical)\nhttps:\/\/links.yourapp.com\/products\/shoes-x         \u2190 Deep link domain URL\nhttps:\/\/www.yourapp.com\/products\/shoes-x?ref=email \u2190 Tracked link\nhttps:\/\/m.yourapp.com\/products\/shoes-x             \u2190 Mobile subdomain\nhttps:\/\/yourapp.com\/products\/shoes-x               \u2190 Non-www variant\n<\/code><\/pre>\n\n\n\n
Each URL shows the same content. Without canonicalization, Google picks one URL to index (and may pick the wrong one) or splits PageRank across all of them.<\/p>\n\n\n\n
Deep Link Landing Pages<\/h3>\n\n\n\n
Many deep linking platforms create their own landing pages at the deep link domain:<\/p>\n\n\n\n
https:\/\/links.yourapp.com\/abc123 \u2192 shows a preview\/interstitial\nhttps:\/\/www.yourapp.com\/products\/shoes-x \u2192 the actual content page\n<\/code><\/pre>\n\n\n\n
If the deep link landing page is indexable, Google might index it instead of your real content page.<\/p>\n\n\n\n
Campaign URLs with Tracking Parameters<\/h3>\n\n\n\n
Marketing campaigns add tracking parameters to URLs:<\/p>\n\n\n\n
https:\/\/www.yourapp.com\/products\/shoes-x?utm_source=email&utm_medium=newsletter\nhttps:\/\/www.yourapp.com\/products\/shoes-x?ref=twitter\nhttps:\/\/www.yourapp.com\/products\/shoes-x?campaign=summer_sale\n<\/code><\/pre>\n\n\n\n
Google treats each parameter combination as a potentially different page.<\/p>\n\n\n\n
Setting Canonical Tags<\/h2>\n\n\n\n
On Your Content Pages<\/h3>\n\n\n\n
Every content page should have a self-referencing canonical tag:<\/p>\n\n\n\n
<head>\n  <link rel="canonical" href="https:\/\/www.yourapp.com\/products\/shoes-x" \/>\n<\/head>\n<\/code><\/pre>\n\n\n\n
This tells search engines: "This is the authoritative URL for this content. Any other URL showing the same content is a copy."<\/p>\n\n\n\n
On Deep Link Landing Pages<\/h3>\n\n\n\n
If your deep link domain serves landing pages (interstitials, previews), they should either:<\/p>\n\n\n\n
Option A: Not be indexable (preferred).<\/strong><\/p>\n\n\n\n
<head>\n  <meta name="robots" content="noindex, nofollow">\n<\/head>\n<\/code><\/pre>\n\n\n\n
Or return a X-Robots-Tag: noindex<\/code> HTTP header.<\/p>\n\n\n\n
Option B: Canonical to the content page.<\/strong><\/p>\n\n\n\n
<head>\n  <link rel="canonical" href="https:\/\/www.yourapp.com\/products\/shoes-x" \/>\n<\/head>\n<\/code><\/pre>\n\n\n\n
Option A is better because it prevents the deep link URL from competing with your content URL entirely.<\/p>\n\n\n\n
Handling Tracking Parameters<\/h3>\n\n\n\n
Tell Google to ignore tracking parameters using Search Console:<\/p>\n\n\n\n
    \n
  1. Go to Search Console<\/a>.<\/li>\n
  2. Navigate to Settings > URL Parameters.<\/li>\n
  3. Mark utm_source<\/code>, utm_medium<\/code>, utm_campaign<\/code>, ref<\/code>, and other tracking parameters as "No: does not affect page content."<\/li>\n<\/ol>\n\n\n\n
    Also, ensure your canonical tag strips parameters:<\/p>\n\n\n\n
    <!-- Page: \/products\/shoes-x?utm_source=email -->\n<link rel="canonical" href="https:\/\/www.yourapp.com\/products\/shoes-x" \/>\n<!-- Note: no parameters in the canonical URL -->\n<\/code><\/pre>\n\n\n\n
    www vs. Non-www<\/h2>\n\n\n\n
    Pick one and redirect the other:<\/p>\n\n\n\n
    # Redirect non-www to www\nserver {\n    server_name yourapp.com;\n    return 301 https:\/\/www.yourapp.com$request_uri;\n}\n<\/code><\/pre>\n\n\n\n
    Set the canonical to your preferred version:<\/p>\n\n\n\n
    <link rel="canonical" href="https:\/\/www.yourapp.com\/products\/shoes-x" \/>\n<\/code><\/pre>\n\n\n\n
    HTTP vs. HTTPS<\/h2>\n\n\n\n
    All URLs should use HTTPS. Redirect HTTP to HTTPS:<\/p>\n\n\n\n
    server {\n    listen 80;\n    server_name www.yourapp.com;\n    return 301 https:\/\/www.yourapp.com$request_uri;\n}\n<\/code><\/pre>\n\n\n\n
    The canonical tag should always use https:\/\/<\/code>.<\/p>\n\n\n\n
    Deep Link Domain Canonicalization<\/h2>\n\n\n\n
    When Your Deep Link Domain Shows Content<\/h3>\n\n\n\n
    If links.yourapp.com<\/code> shows content (not just redirects), it creates a duplicate content problem. Solutions:<\/p>\n\n\n\n
    Solution 1: Pure redirects.<\/strong> Your deep link domain only redirects; it never serves HTML content.<\/p>\n\n\n\n
    links.yourapp.com\/products\/shoes-x \u2192 302 redirect \u2192 www.yourapp.com\/products\/shoes-x\n<\/code><\/pre>\n\n\n\n
    A 302 (temporary) redirect is appropriate because the deep link URL is not the canonical destination. Google does not index 302 targets as duplicates.<\/p>\n\n\n\n
    Solution 2: Noindex on the deep link domain.<\/strong> If the deep link domain must serve content (e.g., for smart banners or previews), add noindex:<\/p>\n\n\n\n
    <!-- On links.yourapp.com pages -->\n<meta name="robots" content="noindex">\n<\/code><\/pre>\n\n\n\n
    Solution 3: Canonical to content domain.<\/strong> Set the canonical on deep link pages to point to the content domain:<\/p>\n\n\n\n
    <!-- On links.yourapp.com\/products\/shoes-x -->\n<link rel="canonical" href="https:\/\/www.yourapp.com\/products\/shoes-x" \/>\n<\/code><\/pre>\n\n\n\n
    When Your Deep Link Domain Is Separate from Your Content Domain<\/h3>\n\n\n\n
    This is the most common setup:<\/p>\n\n\n\n
    Content: www.yourapp.com (indexed, canonical)\nDeep links: links.yourapp.com (redirects only, not indexed)\n<\/code><\/pre>\n\n\n\n
    No canonicalization issues because the deep link domain does not serve indexable content.<\/p>\n\n\n\n
    Pagination and Filtered Views<\/h2>\n\n\n\n
    If your app has list pages with filters (categories, sort order, price range), each filter combination creates a different URL:<\/p>\n\n\n\n
    \/products?category=running\n\/products?category=running&sort=price\n\/products?category=running&sort=price&page=2\n<\/code><\/pre>\n\n\n\n
    Solution: Canonical to the Base URL<\/h3>\n\n\n\n
    For filtered views, canonical to the unfiltered base:<\/p>\n\n\n\n
    <!-- \/products?category=running&sort=price -->\n<link rel="canonical" href="https:\/\/www.yourapp.com\/products?category=running" \/>\n<\/code><\/pre>\n\n\n\n
    For paginated views, each page should self-reference:<\/p>\n\n\n\n
    <!-- Page 2 -->\n<link rel="canonical" href="https:\/\/www.yourapp.com\/products?category=running&page=2" \/>\n<link rel="prev" href="https:\/\/www.yourapp.com\/products?category=running&page=1" \/>\n<link rel="next" href="https:\/\/www.yourapp.com\/products?category=running&page=3" \/>\n<\/code><\/pre>\n\n\n\n
    Hreflang for Multi-Language Apps<\/h2>\n\n\n\n
    If your app content exists in multiple languages, use hreflang tags<\/a> to tell Google about the language variants:<\/p>\n\n\n\n
    <head>\n  <link rel="canonical" href="https:\/\/www.yourapp.com\/en\/products\/shoes-x" \/>\n  <link rel="alternate" hreflang="en" href="https:\/\/www.yourapp.com\/en\/products\/shoes-x" \/>\n  <link rel="alternate" hreflang="es" href="https:\/\/www.yourapp.com\/es\/products\/shoes-x" \/>\n  <link rel="alternate" hreflang="fr" href="https:\/\/www.yourapp.com\/fr\/products\/shoes-x" \/>\n  <link rel="alternate" hreflang="x-default" href="https:\/\/www.yourapp.com\/en\/products\/shoes-x" \/>\n<\/head>\n<\/code><\/pre>\n\n\n\n
    Each language version should be its own canonical URL. Do not canonical all languages to the English version.<\/p>\n\n\n\n
    Verification<\/h2>\n\n\n\n
    Google Search Console<\/h3>\n\n\n\n
    Use the URL Inspection tool to check canonicalization:<\/p>\n\n\n\n
      \n
    1. Enter a URL you suspect might have duplicate issues.<\/li>\n
    2. Check "Google-selected canonical" in the results.<\/li>\n
    3. If the Google-selected canonical differs from your declared canonical, investigate.<\/li>\n<\/ol>\n\n\n\n
      Site Search<\/h3>\n\n\n\n
      Search Google for your content and check which URL appears:<\/p>\n\n\n\n
      site:yourapp.com "product name"\nsite:links.yourapp.com "product name"\n<\/code><\/pre>\n\n\n\n
      If content from your deep link domain appears in search, it is being indexed when it should not be.<\/p>\n\n\n\n
      Crawl Reports<\/h3>\n\n\n\n
      Check your crawl reports for signs of duplication:<\/p>\n\n\n\n