The renew-forever rule: why letting an old domain drop costs you more than the renewal

The rule, in one sentence

Any domain you ever pointed at a site you still own has to stay registered until you no longer own that site. Forever. Not 'until the redirect stops sending traffic.' Not 'until I forget about it.' Forever.

The reason is uncomfortable: once a 301 is in place, the receiving domain's authority is partially dependent on the redirecting domain's continued existence. Drop the redirect source and you don't just lose new traffic from it — you hand the equity it was passing to whoever catches it next. The domain forwarding explainer covers the underlying mechanics.

How catchers actually work

Expired-name monitoring is a small, mature industry. SpamZilla, ExpiredDomains.net, NameJet, GoDaddy Auctions, DropCatch — all watch the expired pool, and a subset of their users filter specifically for names that currently have 301 redirects pointing into other properties. The aged-domain value guide covers what makes those captures attractive.

The reason that filter exists: a name with an active redirect into a high-authority site is a more valuable buy than a comparable one without. The buyer can keep the redirect and inherit whatever equity was flowing, kill it and host new content, or repoint it at a different target.

From the original owner's perspective, all three outcomes are bad. The first dilutes whatever effect you had because a stranger now controls the on-ramp. The second cuts the equity off. The third reroutes link equity that used to flow to you into a different site — possibly a competitor. The parked-domain stack explainer covers routing once you decide to keep an inherited name alive.

The math, plainly

Open preview

The ratio is absurd and the decision is not close. Every dollar you save by letting a redirect source lapse costs you between $40 and $400 in equivalent replacement effort.

Open preview

Why people let domains drop anyway

Three patterns explain almost all of it:

One: the email at the registrar is a personal Gmail nobody checks anymore. Renewal notices go to /dev/null. The domain expires silently. By the time anyone notices, the catcher has already filed the trademark complaint to keep it.

Two: the credit card on file expired. Auto-renewal fails. The grace period runs out. Same outcome.

Three — the worst one — the redirect was set up by someone who no longer works at the company, and nobody on the current team knows the domain exists, let alone what it's doing.

Open preview

What 'multi-year prepay' actually buys you

ICANN caps single registrations at 10 years. That's the longest you can prepay any domain at once. Most registrars let you stack — you can renew a domain currently expiring in 2027 out to 2037, then renew it again in 2030 out to 2040.

Doing this once a year, as part of the audit, costs roughly the same as the original renewal but pushes your expiration risk window from 12 months out to a decade. The renewal-notice email going unread no longer matters — the next risk is 10 years away, not 30 days.

For domains that are doing real work — meaningful inherited equity, brand defense, or active 301s — multi-year prepay is the closest thing to 'set and forget' you can buy.

How the redirect itself is wired — and why it matters for equity

Before you argue about whether to renew an old domain, know how the redirect was set up, because the redirect type decides how much SEO value survives. A 301 is a permanent redirect — it tells search engines and browsers the old URL has permanently moved to a new URL, and it passes the bulk of the link equity to the destination URL.

A 302 signals a temporary move, so search engines don’t reliably consolidate ranking signals onto the new domain, and a source stuck on a 302 quietly leaks value even while registered. Fixing the 301 vs 302 question is often a bigger lever than the renewal itself.

The plumbing depends on where the domain lives. On a server you control, you set redirect rules in an .htaccess file on Apache, or a location block on nginx, mapping each old URL to its destination URL. Without server access — the common case for a bare source — you use URL forwarding at the domain registrar (Namecheap, GoDaddy) or redirect rules on Cloudflare that rewrite the request at the DNS layer.

SSL, HTTPS, and the details that break a redirect silently

A redirect that throws a certificate warning is almost as bad as no redirect. Modern browsers and search engines expect https redirects, so the redirect source needs a valid SSL certificate even though no one ever types it in. Cloudflare handles this with automatic HTTPS; on a server you provision one through Let's Encrypt. Let either lapse and the redirect returns errors that search engines read as a broken on-ramp.

DNS is the other quiet failure point. The Domain Name System turns the source URL into a server it can reach, so it only resolves if its dns records — an A record to the right IP address, or a CNAME to the destination — are intact. A registrar transfer, a nameserver change, or an expired account can wipe those records and turn a working forward into a 404 without the registration ever expiring.

One more certificate angle: over HTTPS the redirecting server presents a public key certificate, and Transport Layer Security plus Certificate Transparency logs are what let a browser trust it. An auto-issued cert quietly stops working the moment issuance breaks — and unlike an expired registration, nothing emails you.

From a valuation chair, the takeaway is blunt: renewing is necessary but not sufficient. The redirect has to actually fire, on the right redirect type, over HTTPS, with clean DNS. A redirect source paid up for a decade but quietly serving a 404 passes exactly zero equity — and it looks fine on the renewal invoice. This is an automated, editorial view, not technical or financial advice; verify your own configuration before acting.

How domain redirects work, briefly

A domain redirect — a url redirect that sends one domain to another — is just an instruction the web server hands back when a browser requests the old name. URL redirection lives inside the ordinary client–server model: the browser asks, the server answers with an HTTP status code and a destination, and the browser follows it to the new URL.

Worth flagging for the marketing-minded: a name you once ran a campaign on is exactly the kind of redirect source people forget. The marketing spend that built its links is sunk, but the equity those links still pass is recurring — which is precisely why letting it drop is the expensive mistake. The cleanest setup is a permanent forward using DNS plus redirect rules; whichever method you pick, the renew-forever rule sits on top of it.

How domain redirection affects SEO rankings (and can boost your SEO)

The question under all of this is simple: do domain redirects affect SEO, and how does redirection impact SEO rankings? Yes, redirects impact SEO — and the type of redirect decides whether they help or hurt. In search engine optimization terms, redirects help when you use 301 redirects correctly to maintain SEO when you change your domain; done wrong, redirects are bad for SEO and quietly tank your rankings.

When you use a 301 redirect, the 301 redirect signals to users and search engines that the move is permanent, and the redirect passes the original page’s SEO value to the destination. That is how 301 redirects pass equity and preserve SEO value through a domain change. A proper redirect from the old domain to the new one is the most important step when switching to a new domain, so the SEO value stays put and the new page inherits the rankings.

A temporary redirect is different. If you use 302 redirects (or a 307 redirect) when the move is permanent, the SEO benefits never transfer and you do not maintain SEO value. So set up a 301 redirect for a permanent change, and only use a 302 redirect or 307 redirect when you genuinely want to temporarily redirect users — using the wrong redirect type is the most common way a domain migration goes wrong.

Two more rules keep redirects and SEO working together. First, always redirect directly: redirect each old URL straight to the most relevant new page, not through a chain. Avoid redirect chains and any redirect loop — they waste crawl budget, hurt user experience and SEO performance, and a redirect loop can take a page out of the index. Second, redirect to the most relevant destination, not the homepage, which throws away the SEO value built into each page.

If you run WordPress, redirect management is easiest with a plugin like Yoast SEO. On a server you set up redirects in the .htaccess file on Apache, a config block on nginx, or rules at a content delivery network like Cloudflare.

The pattern for changing domain names is the same every time: set up a domain redirect from the old domain to a new one, use 301 redirects so the redirect passes the original page's SEO value and ensures the new URLs inherit rankings, then verify in Google Search and Search Console that they index.

What makes redirects bad for SEO is almost always execution. The difference between 301 and 302 redirects is the headline issue, but a Google Search crawler also penalizes long chains that hurt SEO by wasting crawl budget — forcing the web crawler to follow hop after hop instead of reaching the web page — and a broken forward inflates bounce rate, hurting SEO and user experience.

A clean redirect written into the .htaccess file on an Apache HTTP Server or as a rule at your domain name registrar lands users on the right search engine results page in one hop. Delete the redirect and ranking signals move with it.

The short version: a redirect is a way to move users and search engines from one URL to another, so use domain redirects deliberately. A 301 will pass SEO value and is how you boost your SEO when you want to redirect permanently; a 307 redirect is temporary, so only use a 307 redirect for a genuinely temporary move. On a server (computing) the rules live in an .htaccess file; on WordPress a redirects plug-in (computing) writes them for you.

From a valuation chair, this is why an inherited domain's redirect setup belongs in due diligence. A single domain that should redirect directly to your website domain but is stuck on the wrong type of redirect leaks SEO equity every day. Audit the redirect type alongside the renewal date — traffic from one domain only becomes value on the new site when the redirect is right. This is an editorial, automated view, not technical or financial advice.

When to actually let a domain drop

There is one case: a domain you registered, never used, never linked from anywhere, and that has never had inbound backlinks of any kind. Those have no inherited equity and can drop without consequence.

Everything else — any domain that has been live, any domain you redirected, any domain that ever held content — is on the renew-forever list. The $12 is not the point. The point is that the alternative is paying $5,000 to a link agency to replace what you just gave away.

Before deciding which inherited domains are worth the renewal, run the domain appraisal calculator and read the DNS / Workers / 301 vs 410 walkthrough for the routing decision.