Both domain collisions I found were with domains I already owned. Search your own registrar for the brand name before you build on a new TLD. One aged domain and two collisions, reported as they happened, not a statistically powered study.
What happened when an aged domain got repurposed?
bestreviews.co.uk was bought aged for its water-softener and home-products backlink profile. It launched in April 2026 as a cost-comparison hub with 95 towns times 10 services of programmatic pages, then was rebuilt reviews-first in late July: on 26 July, 1,130 of those town/service pages were deleted as thin spun content and wildcard-301'd into 10 national hubs.
Search Console recorded 4 clicks and 17,069 impressions from 20 June to 15 September 2026. Average position across the period was 82.7.
<table> <thead> <tr><th>Metric</th><th>Value, 20 Jun–15 Sep 2026</th></tr> </thead> <tbody> <tr><td>Clicks</td><td>4</td></tr> <tr><td>Impressions</td><td>17,069</td></tr> <tr><td>Average CTR</td><td>0.02%</td></tr> <tr><td>Average position</td><td>82.7</td></tr> </tbody> </table>
Daily impressions ran 150-650 through June and July, then fell to under 40 a day from 21 August. Average position moved from the mid-80s to the 60s and 70s over the same window, mostly sitting 59-75. That shift followed the 26 July deletion of 1,130 town pages, so it reflects fewer low-ranked URLs pulling the average down, not pages climbing. Nothing reached page one, before or after.
Domain age and inherited backlinks did not rescue spun location pages. One case, but it is the case the aged-domain pitch says should not happen: real backlink history, still stuck at position 80+ on thin content, and the only ranking-shape change came from deleting pages, not from the domain's age.
What is a domain collision?
A domain collision is a second live domain carrying the same or a similar brand name as an unlaunched new build. A portfolio audit on 29 July 2026 found two domains matching this pattern and a third that turned out to be something else.
<table> <thead> <tr><th>Live domain</th><th>Intended new build</th><th>Condition found</th></tr> </thead> <tbody> <tr><td>dampfree.co.uk</td><td>dampfree.uk</td><td>Dormant WordPress install, one 2019 post, homepage retitled with no real content</td></tr> <tr><td>bestwalkingpads.com</td><td>bestwalkingpads.co.uk</td><td>Live branded site with broken navigation on every main category link</td></tr> </tbody> </table>
A third domain checked in the same audit, ideeeas.com, turned out to be a misconfiguration rather than a collision: its own homepage was pointed at the wrong WordPress page and a Rank Math redirect rule sent every unmatched path to the sitemap.
dampfree.co.uk carried a single "Hello World" post from 2019 under an old web-design-agency template. Its homepage had been retitled "DampFree UK – Moisture Absorbers" with none of the actual DampFree content behind it. bestwalkingpads.com carried real "Best Walking Pads" branding, but its navigation linked to /reviews, /category/guides and /category/reviews, and all three returned 404, with no posts under /blog.
As of 18 September 2026: dampfree.co.uk is still live in the same broken state, and its intended replacement dampfree.uk has not launched. bestwalkingpads.com no longer resolves at all, and bestwalkingpads.co.uk has not launched either.
What should you check before launching a new domain?
Search the exact brand name across every TLD you already hold before building on a new one. Both collisions were on domains I already owned, not domains a competitor held. Checking the target domain alone misses this.
Once a collision is found, the fix is a decision:
- Redirect the old domain to the new one once the new build is live.
- Repurpose the old domain for unrelated content if the brand should not carry across both.
- Retire the old domain if neither option earns its renewal cost.
Neither case above was fixed at the time; both needed WordPress admin or DNS access, not a code change. Status on 18 September 2026: dampfree.co.uk unresolved, bestwalkingpads.com gone, neither new build launched.
Does buying an aged domain still make sense?
Buying an aged domain buys its backlinks. The ranking still has to be earned by the content you put on it. bestreviews.co.uk kept a backlink history built for one niche and moved into a different one; the domain's age did not follow it there.
Treat an aged domain as link equity for a closely related niche. Check its link profile and history against the planned content before paying for age.
How was this checked?
This covers one aged domain and two verified collisions from my own portfolio, not a statistically powered study. Domain-collision findings are dated 29 July 2026; current live/resolving status is dated 18 September 2026. Search Console figures for bestreviews.co.uk are dated 18 September 2026, for the window 20 June to 15 September 2026.
Evidence limits: these are properties I own; nothing here was independently audited by a third party. Domain status can change after publication, check current status directly before treating either collision case as fixed or unfixed.
