Redirecting an Expired Domain: What Google Allows and What Gets Flagged

An expired domain redirect is the cheapest thing you can do with a domain that has history. Register it, add one server rule, and every old link on the web resolves to your site. It takes ten minutes, which is the problem. Ten minutes is also about how long most people spend deciding whether the redirect should exist at all.

This guide is about that decision, and then about the setup. What follows is what Google's documentation says and does not say, a test you can run on any domain before you commit, and the three DNS and server steps once you have decided.

One definition, once. "Link equity" is the SEO term for whatever value a link passes to the page it points at. I avoid the phrase from here on because it makes a redirect sound like a bank transfer, and it is not one.

What does Google's expired domain policy say about redirects?

Nothing. The expired domain abuse section of Google's spam policies is four sentences long and describes one practice: an expired domain "purchased and repurposed primarily to manipulate search rankings by hosting content that provides little to no value to users". The three examples are affiliate content on a former government site, medical products on a former charity, and casino content on a former school. Every example is about what gets hosted. A redirect hosts nothing.

The announcement post from March 2024 draws the line from the other side. Google wrote that "It's fine to use an old domain name for a new, original site that's designed to serve people first." Again, a site. Redirects are not named in either document, and our verbatim read of the policy goes through why that section turns on two things at once, a thematic mismatch and low-value content.

So a redirect is not expired domain abuse under that heading. It can still be spam. The same policy page has a section on sneaky redirects, which it defines as redirecting "to either show users and search engines different content or show users unexpected content that doesn't fulfill their original needs". The test Google gives is short: "consider whether or not the redirect is intended to deceive either the users or search engines." The same page lists "Moving your site to a new address" and "Consolidating several pages into one" as legitimate reasons to redirect.

Together the two sections are the whole rule. A redirect from an expired domain is fine when the destination is a plausible continuation of what the old links were pointing at, and it is a sneaky redirect when someone following a 2016 link to a charity's donation page lands on your pricing page.

What does a 301 actually do?

Google's redirect documentation says that with a permanent redirect "Googlebot follows the redirect, and the indexing pipeline uses the redirect as a signal that the redirect target should be canonical." The canonicalization page explains what canonical buys you. Consolidation lets search engines merge "the signals they have for the individual URLs (such as links to them) into a single, preferred URL."

That is the entire mechanism. A 301 is a claim that the old URL and the new URL are the same page, and Google decides whether to believe it. When it does, the old URL's links count for the new one. When it does not, the old URL is treated as a page that went away, and Search Console files it under Soft 404, a page that "returns a user-friendly 'not found' message but not a 404 HTTP response code". There is no partial outcome. Gary Illyes said in 2016 that "30x redirects don't lose PageRank anymore", and Search Engine Land recorded the tweet. Accepted or not, per URL.

A score never transfers. Domain Authority and Domain Rating are estimates published by Moz and Ahrefs, Google reads neither, and the tools recompute your number later from whichever links now resolve to you. The authority metrics guide covers why the referring domains are the asset and the score is a summary of them.

When does an expired domain redirect make sense?

The pattern that works is dull. The old domain and the new site are about the same thing, and the new site has pages that could stand in for the old ones.

The cleanest case is your own history. You rebranded, let the old name lapse, and want it back. The old links pointed at your company under a previous name, and Google's site move guidance is written for exactly this.

The second case is a successor in the same space. A software company launches on the domain of a software blog that covered its category. A clinic takes the domain of a clinic that closed. The linking pages were vouching for a subject, and the subject is still what the destination serves.

The third case is narrower than people want it to be. The domain had one strong section and you have a matching one. A domain that published water-quality research for a decade, redirected page by page to your water-quality resource pages, is a redirect where every old link still lands somewhere that makes sense. The rest of the old domain, the about page and the staff bios, should 404 rather than go to your homepage. A homepage redirect for a URL with no equivalent is the soft-404 case from above.

In all three cases, if you rebuilt a site on the old domain instead of redirecting, it would be about the same thing your site is about. That is the test.

When is it a mismatch?

The mismatch is any redirect where the destination has nothing to do with what earned the links. Gardening publication to a SaaS product, or regional newspaper to a crypto exchange. Those are the examples in the abuse policy with an HTTP hop added, and Google's own sneaky redirects text describes what a visitor experiences: "unexpected content that doesn't fulfill their original needs."

Two softer versions catch people who think they have passed the test. Redirecting everything to the homepage is the first. Registrar forwarding does this by default, so most expired domain redirects look like this. Even on a matched domain, a wildcard to the homepage tells Google that thirty different old pages were all the same page as your homepage. It rarely believes that.

The second is a domain whose history changed subject before it expired. Plenty of good domains spent their last two years hosting whatever the previous owner could sell them for, usually gambling or pharmacy affiliate pages. The links from that stretch point at that content, and the archive is where you find out how much of the profile that is.

How do you check the fit before redirecting?

Four checks, none of which need an account anywhere.

Start with the archive. The Wayback Machine shows what the domain published year by year, and the expired domain checker summarises the same history in one view. You want a single subject held over years, and you want to know what the final two years look like.

Then read the linking pages. Run the domain through the backlink checker and open ten of the referring pages. The anchor text is what the linking site thought the page was. If the anchors say "water quality report 2014" and you sell accounting software, the redirect fails before you set it up. The guide to reading an expired domain's link history covers this properly.

Third, check the category. Every listing in the Revised directory is categorised from its archived content, so a domain is filed under what it used to be, and the category hubs let you browse only domains that were in your space. That is the first half of the fit test done for you.

Last, look at your own site. For each old URL that carries links, name the page on your site that replaces it. If you cannot name one, that URL should 404. If you cannot name one for any of them, you are not redirecting a domain, you are attaching a random name to your site. The honest alternative is a small site on the domain about its old subject, which rebuilding on a domain you bought covers.

How should the redirect be set up?

Three steps, then the three places matched redirects still fail.

Point DNS at whatever will serve the redirect. Update the domain's records at your registrar to point at your host, CDN or redirect service. Ordinary domain configuration, the same as any new name.

Configure the 301 at the server, host or CDN. Cloudflare, Vercel, Netlify and most hosts do permanent redirects from a rule rather than a deployment. Map old URLs to their real equivalents here rather than pointing everything at one destination.

Verify the status code, not the browser. Visit the domain and confirm a 301 rather than a 302 or a meta-refresh. curl -sI https://example.com prints the status and the Location header, and registrar forwarding in particular often issues a 302 or an HTML frame instead.

Three points from Google's documentation are where matched redirects still fail.

Use a server-side 301 or 308. Google recommends "a permanent server-side redirect whenever possible" and calls it "the best way to ensure that Google Search and people are directed to the correct page". A 302 is temporary and is not used as a canonical signal.

Redirect straight to the final URL, protocol and subdomain included. Google's site move page says it follows up to 10 hops but advises "redirecting to the final destination directly" and keeping any chain "ideally no more than 3 and fewer than 5". An acquired domain redirecting to http, then https, then www, is three hops before anything has gone wrong.

Keep it up. The same page says to "Keep the redirects for as long as possible, generally at least 1 year." The old links count only while the redirect exists, and dropping the domain hands them to whoever registers it next. And skip Search Console's Change of Address tool, which is for moving a whole site between domains you have both verified.

How do you know whether it worked?

Google says that for medium-sized sites "it can take a few weeks or more" for new URLs to replace old ones. After a month, check the page indexing report in Search Console for the destination property. The old URLs should show up under "Page with redirect", which Google defines as "a non-canonical URL that redirects to another page". That is the redirect being seen and accepted. If they show up under Soft 404 instead, Google did not believe the mapping, and the fix is a better destination or a 404. The links report should also start listing the acquired domain's referring domains against your pages.

Three places to watch, in the month after:

• Search Console, page indexing. The old URLs under "Page with redirect" is the accepted case; under Soft 404 is the rejected one.
• Search Console, links report. The acquired domain's referring domains should start appearing against your pages.
• Analytics. Referral traffic arriving through the old domain tells you the links are still being followed by people, which is worth knowing separately from whether Google consolidated them.

Give it a few weeks before reading any of it, and leave the destination alone while you do. Changing where the redirect points restarts the clock, and inserting a second hop puts you back in the chain-length advice below rather than losing anything by itself.

The manual actions report will almost certainly be empty. Enforcement here is algorithmic, so a bad redirect does not get a notice. It gets silence, which is the outcome most people mistake for "not doing much yet".

John Mueller added a caution in 2025 that applies to any acquired domain. Search Engine Journal quoted him saying "Sometimes it just takes a lot of time for the old state of a domain to be shaken off (sometimes that's also the case when it was parked for a while)." A domain parked for two years may take longer than one that dropped last month.

Using the Revised directory for this

The redirect decision is a history check, so do the history check before you own the domain.

1. Open the directory and set Category in Basics to your own subject. Every listing is categorised from its archived content, so this is the thematic half of the fit test already done.
2. Add a Referring domains floor and set Spam signal to low. As of 16 September 2026 the directory holds roughly 11,000 expired domains, 84% of which pass a low spam screen, and every listing is spam-screened before it goes up.
3. Read Linked by down the column. A redirect lives or dies on whether those sources were writing about what your destination is about.
4. Narrow by linking source or by TLD if the old links need to come from a particular kind of site.
5. Open the listing page and read the archived timeline before revealing anything. What you are looking for is one subject held over years, and what the final two years look like.
6. After a reveal, run the name through the expired domain checker for the capture history and the backlink checker for the referring pages, then map old URLs to your own pages before you set a single rule.

Metrics and filters are free and need no account. We do not sell, hold or register the domains listed, so registering a revealed name is ordinary registrar work.

FAQ

Can I 301 redirect an expired domain to my new site? Yes, and Google's policy does not forbid it. The redirect holds up when the new site is about the same subject the old domain's links were pointing at and has pages that can stand in for the old ones. When the subject is unrelated, the redirect matches Google's definition of a sneaky redirect and the old links are ignored.

Is redirecting an expired domain considered expired domain abuse? Not under that heading. The abuse policy describes hosting low-value content on a repurposed domain. A redirect from an unrelated domain falls under sneaky redirects instead. Same page, different section, same outcome.

Do backlinks transfer through a 301 redirect? When Google accepts the redirect, the old URL's signals, links included, are consolidated into the new URL. When it does not, the old URL is treated as a soft 404 and nothing consolidates.

Should I redirect an expired domain to my homepage? Only for the old homepage, and only if the subjects match. Redirecting every old URL to your homepage is the most common way this fails. Map old pages to their real equivalents and return a 404 for the ones that have none.

Do I need a host to redirect a domain? Something has to answer the request, but it does not have to be a web server you run. A CDN rule, a redirect service or your existing host's domain settings will do it. What you want to avoid is registrar forwarding left on its default, which usually issues a 302 to your homepage for every old URL.