Why does your Search Console data disappear without any apparent reason?

What is canonical URL aggregation in Search Console?

Search Console collects billions of data daily: impressions, clicks, average positions, indexing coverage. To prevent overwhelming users with hundreds of lines for nearly identical pages, Google aggregates everything under a single reference URL: the canonical one it has chosen.

Specifically? If you have a product page accessible via /product?utm_source=fb, /product?ref=email, /product#session=123, Google considers them as variants of /product. All metrics are aggregated to /product, the canonical URL. This is transparent when everything goes well.

What happens when the canonical switches between two URLs?

The problem arises when Google hesitates between two canonicals for the same page. Imagine one day it chooses /category/blue-product, the next day /blue-product-v2. This flapping creates fragmentation: part of the data aggregates under the first URL, another part under the second.

You then see in your reports two distinct lines with truncated curves, impressions that seem to drop when in reality they are just being counted elsewhere. Analysis becomes a nightmare: impossible to know if a drop in traffic is real or artificial, if a page is advancing or stagnating.

Why doesn't Google rely on the canonical declared in the HTML?

Because the canonical tag is a signal, not a directive. Google can ignore it if it believes it points to a less relevant, less performant, or technically problematic URL. It cross-references this signal with others: site structure, redirects, sitemaps, internal links.

In practice, if your internal linking heavily points towards a URL variant different from your declared canonical, Google may favor this variant. Or worse: constantly hesitate, creating that infamous flapping that fragments your data.

• Search Console aggregates everything by the canonical URL chosen by Google, not the one you declare.
• Canonical flapping leads to report fragmentation: data scatters across multiple URLs.
• Google can ignore your canonical tag if it deems another URL more legitimate.
• Performance analysis becomes nearly impossible when metrics are scattered across multiple rows.
• Flapping often masks structural issues: inconsistent internal linking, poorly managed redirects, non-standardized URL parameters.

Is this statement consistent with real-world observations?

Absolutely. We regularly observe websites whose Search Console curves look like roller coasters for no apparent reason: no technical changes, no penalties, no seasonality. Digging into the "URL Inspection" tab, we discover that Google switches between two canonicals every 3-4 days.

The classic case? E-commerce sites with faceted URLs (/shoes?color=red&size=42) where the internal linking sometimes points to the parameterized version, sometimes to the clean version. Google eventually loses track of which URL to prioritize, and your reports go haywire.

What nuances should be added to this statement?

Google doesn't disclose how long this "flapping" lasts before stabilization, nor how fragmented the data becomes. [To verify]: Does a brief switch (1-2 days) suffice to create visible fragmentation, or is prolonged oscillation (weeks, months) required?

Another point: the statement implicitly suggests that the problem always lies with the site. However, we have seen cases where Google hesitated between two strictly identical URLs in content, simply because one was in HTTPS and the other in poorly redirected HTTP. This is a crawl issue, not a real ambiguity.

In what cases does this rule not fully apply?

If your site has no duplication — unique URL per page, no parameters, no facets, no variants — you will never see this problem. But let's be honest: how many sites achieve this level of technical purity?

Very simple sites (blogs, one-page showcase sites) are not concerned. However, once you have filters, sorting, sessions, tracking parameters, the risk of flapping skyrockets.

How can I detect a canonical flapping issue on my site?

First step: identify anomalies in Search Console. Open the Performance report, filter by page, and look for URLs that seem to duplicate the same search intent with offset curves over time. If two URLs have impression peaks that compensate for each other, it's suspicious.

Then, use the "URL Inspection Tool" on each variant. Note the canonical URL declared by Google ("Canonical URL selected by Google"). Repeat the inspection every 3-5 days for two weeks. If the canonical URL changes between inspections, you have confirmed flapping.

What concrete actions can stabilize the canonical?

Clean up your internal linking. If you declare /blue-product as canonical but 80% of your internal links point to /category/blue-product, Google will hesitate. Unify: all internal links must point to the declared canonical URL.

Next, normalize your URL parameters via Google Search Console ("URL Parameters" section in older versions, or strict canonical tags in HTML). Block session parameters, tracking, and non-SEO filters via robots.txt or noindex if necessary.

What should I do if Google continues to ignore my declared canonical?

If flapping persists after cleaning, it means Google detects a stronger signal than your canonical tag. Check your 301 redirects: a poorly managed redirect chain can muddle the waters. Also, check the XML sitemap: does it include the right canonical URLs, or variants?

In extreme cases, it may be necessary to completely block non-canonical variants via robots.txt or noindex, to force Google to crawl only the desired URL. It's radical, but it works when everything else fails.

• Manually inspect 5-10 representative URLs weekly for a month to detect canonical switching.
• Conduct a complete audit of internal linking: all links must point to the declared canonical URL, never to a variant.
• Normalize URL parameters via Search Console or via strict canonicals in HTML.
• Check 301 redirect chains: none should point to a different URL than the canonical.
• Clean up the XML sitemap: it should only contain canonical URLs, never variants.
• If flapping persists after 3 months: consider blocking non-canonical variants via noindex or robots.txt.