Note

You fixed your canonical tag and nothing happened. Google says give it two weeks.

Here is a frustration we hear from owners constantly: you find a duplicate-content problem, you fix the canonical tag, you resubmit the page, and then... nothing. Days pass. Google keeps showing the wrong URL. You start wondering if you broke something.

This week Google answered that directly. Per Search Engine Journal and Search Engine Roundtable coverage on July 10, 2026, Google's John Mueller said canonical re-evaluation can take up to two weeks after you make a change (searchenginejournal.com, seroundtable.com).

Two weeks. Not a bug, not a penalty, just how long the machinery takes to recrawl, reprocess, and re-decide which version of a page is the real one.

Why it takes that long

Canonicalization is not a switch, it is a verdict. Google weighs your canonical tag together with redirects, internal links, sitemaps, and which URL it has historically trusted. When you change the tag, you are submitting new evidence, not issuing a command. The system has to recrawl the pages involved, notice the change, and re-run the comparison. On a site it does not crawl often, that loop is slow.

What this means in practice

1. Fix it once, correctly, then stop touching it. Flip-flopping the canonical while you wait resets the clock and muddies the evidence. Make the change, verify it is actually in the served HTML, and leave it alone.

1. Make all your signals agree. The two-week clock runs fastest when the canonical tag, your redirects, your internal links, and your sitemap all point at the same URL. If your sitemap lists one version and your canonical names another, you are asking Google to referee a contradiction, and that can take a lot longer than two weeks.

1. Verify the fix shipped before you start waiting. This is the step people skip. A canonical set in a CMS field does not always reach the live HTML, and a canonical added by JavaScript may not be there when the crawler reads the raw page. If the fix never actually rendered, you are not two weeks from resolution, you are at day zero and do not know it.

The check that saves the wait

Before you settle in to wait out Google's clock, confirm three things: the canonical is present in the raw served HTML, it points at exactly one absolute URL, and nothing else on the page contradicts it. Our free scan reads your page the way Googlebot does and flags canonical problems in plain language, including the ones that only exist in the rendered version. Two minutes of checking beats two weeks of waiting on a fix that never shipped.

Sources: Search Engine Journal, July 10, 2026 (searchenginejournal.com); Search Engine Roundtable, July 10, 2026 (seroundtable.com).