How to Remove Old URLs From Google Index on a Bought Domain

If you want to know how to remove old URLs from Google index after buying a domain, the short answer is that there are two layers. The Removals tool in Search Console hides a URL from Google Search quickly, but only for about six months. The permanent fix is on your server: make the old URL return a 404 or 410, put a noindex rule on it, or password-protect it, and then let Google recrawl it.

On a bought expired domain, a site: search often still shows the previous owner's product pages, a dead blog, or hundreds of spam URLs. Here is how to clear them out for good.

How to remove old URLs from Google index: the two layers

Google's Removals tool documentation says a temporary removal lasts about six months and does not stop crawling. If the URL still returns content after that, it can reappear. Use the tool to buy time and the server-side methods to finish the job.

You need to own the Search Console property to use the Removals tool; verifying it and reading the Manual Actions report are covered in what to do after buying a domain.

Find what Google still has

Build a list of the old URLs and sort them into patterns. You will decide per pattern, not per page.

1. Run site:yourdomain.com. Note the folders and URL shapes that repeat: /product/…, /blog/2019/…, /?p=…, or strings of foreign-language slugs. Our guide to checking whether a domain is indexed explains how to read the results.
2. Pull the old URL list from the Wayback Machine. The /* view on web.archive.org lists archived URLs, including ones site: may not show.
3. Open the Page indexing report in Search Console. It lists example indexed URLs and, as you work, the old ones dropping out as "Not found (404)".
4. Check subdomains separately. Spam often lived on a subdomain. A Domain property covers every subdomain.
5. Group the list. Each group gets one decision.

Say the domain shows three groups: a former bakery's blog, a /shop/ folder of product URLs, and a /jp/ folder of Japanese keyword spam added after the bakery closed. Each needs a different treatment.

Decide per URL pattern: rebuild, redirect or let go

Not every old URL should disappear. Some have backlinks, and those are part of why you bought the domain.

• Rebuild pages whose topic matches your new site and that have backlinks. Put real, useful content back at the same URL. The full method is in how to rebuild an expired domain, and restoring from the Wayback Machine covers recovering the old text.
• 301 redirect an old URL only when you have a genuinely equivalent page. Google treats 301 and 308 as a strong signal that the target should be processed, and 302 or 307 as a weak one. Redirecting a whole folder of unrelated pages to your home page is not an equivalent; the 301 redirect guide explains how to map URLs one by one.
• Let it go with a 404 or 410 for everything else: old products you will never sell, thin pages, and all spam.

In the bakery example: rebuild the handful of blog posts that earned links and fit your topic, return 404 or 410 for the shop folder, and remove the /jp/ spam completely. If the archive shows a takeover like that, read the Japanese keyword hack before you decide the domain is worth keeping.

Use the Removals tool for urgent cases

The temporary removal is for URLs you cannot wait on: spam showing for your brand name, adult or gambling content, anything embarrassing while you fix the server.

Single URLs

In Search Console, open Removals, start a new request and remove the URL temporarily. Google says the tool can take a page out of results within a day. You can also clear only the snippet, which wipes the description until the page is indexed again.

The prefix option for spam folders

For a folder like /jp/, choose "Remove all URLs with this prefix". It blocks every URL beginning with that path, on both www and non-www. Other subdomains are not covered, so a spam subdomain needs its own request.

The tool removes nothing from other search engines and nothing permanently. Treat every request as a six-month deadline for the server-side fix.

Make the removal permanent

404 or 410

Google's documentation on HTTP status codes states that indexed URLs returning a 4xx status are removed from the index, and that all 4xx errors except 429 are treated the same. A 410 does not remove a page faster than a 404. Pick whichever your server or CMS handles cleanly, and apply it to whole patterns with a server rule rather than page by page.

noindex

A noindex meta tag, or an X-Robots-Tag: noindex HTTP header for non-HTML files such as PDFs, tells Google to drop the page from Search results. Use it when the page has to stay reachable for visitors but should not appear in Google. The rule only works if Google can crawl the page and see it.

Password protection

A login keeps crawlers out.

Why robots.txt does not remove pages

Blocking a folder in robots.txt feels obvious, and it is the most common mistake. Google's guide to removing information says not to use robots.txt for this. A block stops crawling, so Google never sees your 404, 410 or noindex, and the old URL can stay in results while other pages link to it.

The order is: remove the content or add noindex first, leave the URLs crawlable, and wait until they have dropped out. Only then decide whether a robots.txt rule is useful for crawl budget.

Soft 404s and other mistakes that keep old URLs alive

• Soft 404s. A page that returns a 200 status but shows "page not found" or an empty template is flagged as a soft 404. Missing pages must send a real 404 or 410 status.
• Catch-all redirects. Sending every unknown URL to the home page hides the problem.
• Restored spam. If you restore the old site from an archive, check the files for spam pages before you publish.
• Sitemaps listing dead URLs. List only the pages you want indexed.
• Wildcard DNS. It can make a spam subdomain resolve again on your new host.

How long it takes and how to speed it up

There is no fixed timeline. Google removes a 4xx URL when it recrawls it, and its noindex documentation warns that a revisit can take months for pages it considers unimportant. Old spam on a long-offline domain is often exactly that.

To move things along:

1. Use URL Inspection in Search Console on a few representative URLs from each pattern and request indexing, so Google recrawls them and sees the new status.
2. Use temporary removals on the URLs that hurt you most while you wait.
3. Re-run the site: search every couple of weeks and note which patterns are shrinking.

Expect the old pages to fade gradually. If you are still choosing a domain, starting with a clean history saves this work: the domain checker reads the archive and flags spam before you buy, and the live list of expired domains shows only domains that passed those checks.

Frequently asked questions

How long does it take for Google to remove old URLs?

A temporary removal can take effect within a day and lasts about six months. A permanent removal through a 404, 410 or noindex happens only when Google recrawls each URL, which can take anywhere from days to months depending on how often Google visits those pages. Requesting a recrawl in URL Inspection helps for the most important URLs.

Is a 410 better than a 404 for removing pages from Google?

No. Google states that all 4xx status codes except 429 are treated the same, so a 410 gives no speed advantage. Use whichever your server returns reliably, and make sure it is a real status code rather than a soft 404.

Can I remove old pages from Google without Search Console?

Yes. The permanent methods need no Search Console: return a 404 or 410, add noindex or password-protect the pages, then wait for Google to recrawl. Search Console is needed only for temporary removals and recrawl requests.

Should I block old URLs in robots.txt?

Not while you want them removed. A block stops Google from crawling the URLs, so it never sees the 404 or noindex. Remove or noindex the pages first, keep them crawlable until they drop out, and add robots.txt rules only afterwards if needed.