Google swapped our money URL: rebuilt price page 3 -> 24, stale 2025 article 96 -> 18 for the same term (GSC data)

Sharing this because I have not seen the pattern discussed much: Google swapping which of your own URLs it ranks for a money term, and the swap itself costing you the ranking.

Setup: Swedish roof-cleaning site, ~180 pages. Money term is our "roof cleaning price" query. Two URLs on the site can answer it: the main price page (rebuilt in stages, last big rebuild went live Nov 2) and an old 2025 blog article with a long price table that we had stopped caring about.

What GSC shows for that exact query (impression-weighted avg position per month, 16 months):

Main price page: Oct 2025 pos 3.6, Dec 10.7 (winter), Mar 2026 5.1, Apr 2.8, Jul 3.2, Aug 2.5, Sep 2.4, Oct 3.8. Then week 44: 7.3. Week 45: 24.5. Daily since Nov 2 it sits at 41-48 in our rank tracker (mobile), GSC avg 24 because desktop is kinder.

Old 2025 article: position 96 in Nov 2025, 60 most of 2026, basically dead. Week 43: 11.9. Week 44: 16.8. Week 45: 18.2 with 3 clicks. It is now the URL Google shows on page 2 for the term while the real page is on page 3-5.

So the pattern is: Google re-evaluated the site (we had a site-wide drop Oct 30 after publishing too many thin town pages at once, separate thread), and in the same window it stopped trusting the rebuilt page for the term and started surfacing the stale article instead. The rebuilt page was first recrawled Nov 8, so for a week Google ranked a version it had not even seen.

Screenshot is GSC, 6 months, this query only. Orange is position (inverted axis), blue is clicks.

Questions:
1. When Google picks a stale URL over your updated one for the same term, do you consolidate (301 the old article into the main page) or keep both and let it sort itself out? I lean 301 because the old article has a year of history and no reason to exist, but a 301 right after a site re-evaluation feels like adding noise.
2. Anyone measured how long a rebuilt page takes to regain a position it held for a year, when the content is objectively better but the URL was unstable for two weeks?
3. Is there any evidence that "price" pages with calculators/interactive parts get treated differently than static price tables? The old article is a plain table, the new page has a calculator and a lot more structure.

Numbers and dates from GSC, happy to share more.

Your price page only got recrawled Nov 8, so the swap happened against the old version. I doubt the rebuild is the cause. The town pages drop at the same week maybe thats more important.

I’d hold off on the 301. Two changes at once during a re-eval and you’ll never know which one fixed it.

Had a client with an old post sitting above the service page for the main term. What we did was boring stuff, a link near the top of the post to the service page with the money phrase and fixing the internal anchors that pointed the wrong way. Too early to say if it worked.

The calculator is worth a look in URL Inspection. If the prices only live inside it Google might see less actual price text than in your old table. A small static table on the page wouldnt hurt.

Did you cut much of the old copy in the Nov 2 rebuild?

Was the URL or canonical tag changed when you rebuilt the price page? Check Google's selected canonical in GSC and compare it with the canonical declared on the page. If they differ, that could help explain why Google started showing the older article instead.

Both good calls, and checking them turned up something I had wrong in the opening post.

@MarketSellCap - URL inspection in GSC: the price page itself is fine. URL unchanged, declared canonical = Google-selected canonical = the price page, last crawl Nov 9. But the "stale 2025 article" is not stale content competing with us. That URL has been a 301 to the price page for a while (htaccess rule). Google just has not recrawled it since July 26, so it still holds the July copy in the index, ranks it on page 2, and the 3 clicks it got actually landed on the price page via the redirect. Google-selected canonical for that URL is still itself, not the redirect target, because it never saw the redirect. Requested a recrawl of the old URL via the GSC button today; the Indexing API push yesterday did nothing for it (price page got recrawled, the old URL did not).

@sharifawan - agree on holding the 301 question, it is moot anyway since the redirect already exists. On your other points: the Nov 2 rebuild kept the copy, it was the Oct 27-29 edits that trimmed some price blocks (partly restored Oct 31). The calculator is lazy-loaded JS but the per-material price ranges are also in plain HTML tables on the page, so Google sees price text without executing anything. Rendered HTML in URL inspection shows the tables.

So the pattern is really: site-wide re-evaluation + Google serving a redirected URL it has not recrawled in 3.5 months. Will report what happens once the old URL gets crawled.

google swapping urls like that is annoying lol, i'd give the rebuilt page a bit more time before touching the old article tbh

Well, the 301 explains why the swap looks stranger in GSC than it is for users, since the old article's clicks still land on the price page.
However I'm more curious about why the price page itself fell so far after the site-wide drop. The recrawl of the old URL should show whether it moves the price page's position or only the address in the results.

Since the old URL has already had a recrawl request and an Indexing API push, would it help to put it back in the sitemap for a while with a fresh lastmod, so Google has one more reason to go back and actually see the 301? Or does listing a redirected URL in a sitemap just send mixed signals and make things messier? Curious if there's a cleaner way to get Google to revisit an old URL it hasn't crawled since July.

house wife said:

Since the old URL has already had a recrawl request and an Indexing API push, would it help to put it back in the sitemap for a while with a fresh lastmod, so Google has one more reason to go back and actually see the 301? Or does listing a redirected URL in a sitemap just send mixed signals and make things messier? Curious if there's a cleaner way to get Google to revisit an old URL it hasn't crawled since July.

Click to expand...

I'd leave the old URL out of the sitemap since it already redirects. Changing lastmod without a real update probably won't help, and the Indexing API isn't meant for regular articles either.