Your domain expired. What happens to your Google rankings?

Published On: — | Last Modified On: —

When your domain expires, your registrar switches off its DNS, so every page on your site becomes unreachable rather than broken, and Google removes unreachable URLs from its index within days. Renew inside the grace period and the pages usually come back. Leave it a month and the recovery gets slower.

Most people find this out the hard way. A card expired, the renewal notice went to an inbox nobody checks any more, and the first real warning is a customer asking why the site won’t load. Then you search your own brand name and there is nothing. It is a horrible hour, and most of what you find while you are panicking was written to sell expired-domain lists rather than to get your site back.

What actually happens the day your domain expires?

Your registrar stops the domain resolving, which means visitors and Googlebot get a DNS failure instead of your website. ICANN’s Expired Registration Recovery Policy requires that interruption — it exists so that you notice. Your files are untouched. Your hosting is untouched. The name that points at them has simply stopped working, and to anything outside your server the site no longer exists.

That distinction matters more than it sounds. A 404 tells Google a specific page is gone. A DNS failure tells Google nothing at all, because there is no server left to answer the question, so every URL you have ever published is in the same state at the same moment.

How long before Google drops your pages?

Days. Google’s documentation on network and DNS errors says crawling starts slowing immediately when a host stops responding, and that already-indexed URLs which stay unreachable are removed from the index within days.

You will see far more precise numbers than that elsewhere. De-indexed in 48 hours, most of your traffic gone inside a fortnight, six months to recover. Nobody publishes a method behind those figures, Google has never published a threshold of its own, and anyone quoting you an exact number of hours is guessing. The nearest thing to an official limit sits in Google’s guidance on pausing an online business, which says taking a site fully offline should last a few days at most before it has significant effects in Search.

So treat it as a race measured in days rather than weeks, and stop reading after you have renewed.

Will your rankings and backlinks come back?

Yes, in almost every case where the domain comes back quickly, because nothing about your site’s history was deleted. A link on someone else’s site is a line of HTML sitting on their server, and it stays there whether your domain resolves or not. Your content is still on your host. Your registration date, if you renew rather than let the name drop, never changes.

What you lose is index presence while the site is dark, and that is a recrawl problem rather than a penalty. Google has to come back, find a working server, fetch the pages again and put them back. For a small site that is usually days rather than weeks, and it happens on Google’s schedule, not yours. The pages that were ranking best tend to return first, because they were being crawled most often to begin with.

How long do you have to get the domain back?

Longer than the panic suggests, though the price climbs in steps. There is no single universal deadline: how many days your registrar leaves the name renewable is its own policy, which is why two registrars give you wildly different answers to the same question. ICANN’s recovery policy sets the floor around it. For at least the last eight consecutive days that the name is still renewable, DNS has to stay interrupted, so the site being down and the name being recoverable overlap by design. Registrars are also required to publish their renewal fee, their post-expiration renewal fee where it differs, and their restore fee, so you can look up what each stage will cost you before you call anyone.

After the registrar deletes the name it enters a 30-day redemption period. You can still get it back there, but through a restore rather than a renewal, and a restore costs a great deal more than the renewal you missed.

The registry record tells you which stage you are in without a phone call. The WHOIS Domain Lookup returns the expiration date and the current status codes: a name showing clientHold or serverHold is deliberately out of DNS, which is why the site is dark, while redemptionPeriod means the registration has already been deleted and you are buying it back.

Those strings are not registrar jargon. ICANN publishes what each status code means, and the words printed on your record are the words your registrar’s support team will use, which makes that conversation a great deal shorter.

Why does a parked expired-domain page make things worse?

Because it answers every URL on your site with HTTP 200 and the same handful of words. Some registrars don’t simply switch DNS off; they point the name at a holding page instead, and ICANN’s recovery policy requires any such page to state plainly that the registration has expired. Your post about pricing, your contact page and your homepage all now serve identical content that says nothing.

Googlebot has no way to read that as an outage. It reads it as your site, and a thousand URLs returning one short, near-identical page is the pattern behind soft 404s and mass duplicate detection. A clean DNS failure is honest about being a failure. A parking page quietly tells Google your content has been replaced, which is a slower thing to undo.

What should you check the hour the domain comes back?

Confirm the name resolves before you touch anything else. Renewal is not instant at the DNS layer, and Google’s own troubleshooting advice allows up to 72 hours for changes to propagate, so a site that is still down twenty minutes after payment is not evidence that something else is wrong.

Then check what your URLs actually return, because a restored domain sometimes comes back pointing at the registrar’s parking nameservers rather than your host. Paste your homepage and your best pages into the Bulk HTTP Status Code Checker and confirm each one answers 200 from your own server, not a redirect to a holding page. Switch the user agent to Googlebot while you are there.

Resist the urge to hammer the Request Indexing button afterwards. It is rate limited, it was never designed for whole-site recovery, and a working server is the signal that brings Googlebot back at volume.

Does Search Console show what happened?

It does, in the Crawl Stats report rather than the indexing report most people open first. Crawl Stats carries a Host status section with a graph for DNS resolution, and Google’s help text for a failure there tells you to check with your registrar that the site is set up correctly — which is exactly the right instruction and almost nobody reads it in time.

The property itself survives. Verification through DNS records can break while the domain is down, so a domain property may need re-verifying, but your history and your data are not deleted along with the registration. Expect the page indexing report to lag by a few days in both directions, going red after the recovery has already started and clearing long after the site is fine.

How do you stop it happening again?

Auto-renew alone is not enough, because auto-renew fails silently when the card behind it expires. Two renewals in a row can go through on a card that dies in month three, and nobody hears about it until the domain does.

The reminder emails ICANN requires your registrar to send — roughly a month out, a week out, and again just after expiry — go to the registrant address on the record, which for a lot of small sites is a freelancer who built the site in 2019. Check that address is one you read. Then put the expiry date in the same calendar you keep everything else in: the Domain Expiry Date Checker pulls it from the registry in a couple of seconds, so you can verify what the registry thinks rather than trusting a dashboard you last logged into a year ago.

Final Thoughts

A lapsed domain is one of the few SEO emergencies with a clean fix: pay, wait for DNS, verify the pages answer 200, leave Google alone. The damage scales with how long the name stayed dark, so the hour you spend renewing is worth more than any recovery tactic you read afterwards. Check the registrant email on your record this week, before it is the thing standing between you and your own website.

Frequently Asked Questions

No. Your domain registration and your hosting are separate contracts, often with separate companies and separate renewal dates. A lapsed domain leaves your files sitting safely on a paid-up server that nothing can reach. That is why restoring the name usually brings the whole site back untouched.

Not immediately. The name has to pass through your registrar’s renewal window, deletion, a 30-day redemption period and a short pendingDelete stage before it returns to the public pool. Desirable names are caught within seconds of dropping, though, so treat the redemption deadline as the real one.

There is no need. Google re-reads your sitemap on its own schedule once the host answers again, and resubmitting does not add priority. Spend the time confirming your pages return 200 from your own server instead, since a sitemap full of URLs that still fail helps nobody.

Your property and its historical data survive the outage. A domain property verified through a DNS TXT record can lose verification while the name is out of DNS, so re-verify if Search Console prompts you. Crawl errors logged during the downtime clear on their own once crawling resumes.