How to Remove a Website From Google Search Console (and From Google Itself)

Here is the uncomfortable thing about this question: the setting called Remove property does not do what most people searching for it want done. It removes the site from your dashboard. Google keeps crawling, indexing and ranking every page exactly as before.

"Remove a website from Google Search Console" is really three different jobs wearing one name. Which one do you mean?

• Declutter your account: stop seeing an old client site or a dead project in your property list.
• Remove pages from Google: get a URL, a directory, or a whole site out of search results.
• Revoke access: remove a former employee or agency from a property they can still see.

Each has its own tool, its own steps, and its own trap. This guide walks all three, in that order.

Three removals that share one name

The reason the confusion matters: two of these jobs are reversible housekeeping, and one changes what the world can find. Mixing them up in one direction wastes ten minutes. Mixing them up in the other direction can hide a revenue page from Google for half a year.

Remove a property from your account

This is the housekeeping version: the old client site, the staging property you verified in 2023, the domain you sold. Four steps:

1. Open the property you want gone, using the property selector in the top-left corner.
2. Go to Settings in the left sidebar. You need to be a verified owner; delegated users do not see the option.
3. Click Remove property and confirm. The property leaves your account list immediately.
4. Optionally, delete your verification token (the HTML file, meta tag, or DNS record). If you leave it in place, you can re-add the property with one click, which is usually what you want for your own sites.

What property removal does and does not do

Worth being precise, because this is where the biggest misconception lives:

• It does not touch Google Search. Rankings, indexing and crawling continue unchanged. Google does not interpret property removal as a signal about the site.
• It does not delete the data on Google's side. Re-verify the site next year and the performance history reappears, subject to the rolling 16-month window that applies to everyone.
• It does not notify or affect other owners. Their access and their view of the property are untouched. You are only editing your own list.

One genuine caution before removing a property you manage for someone else: export anything you still need. Search Console shows a rolling 16 months at most, so any history you don't capture yourself is on a schedule to disappear whether or not the property stays in your account.

Remove pages from Google Search results

This is the version with stakes. The reliable pattern is a two-step: hide the URL fast with the Removals tool, then make the removal permanent with a signal Google respects on recrawl. Doing only the first step means the page comes back in about 6 months. Doing only the second means waiting days or weeks for Google to recrawl.

Step 1: Hide it fast with the Removals tool

1. Open Indexing → Removals in the left sidebar of the property that contains the URL.
2. Click New request. Choose Temporarily remove URL to hide the page and its cached copy, or Clear cached URL to wipe the snippet and cache while leaving the listing.
3. Enter the URL. Tick Remove all URLs with this prefix to cover a directory or an entire site in one request.
4. Submit and check the status. Approved requests usually take effect within hours. The request list shows anything denied and why.

Step 2: Make the removal permanent

While the curtain is up, change the page's actual state. Any one of these is sufficient:

• Delete the page so it returns a 404 or, better, a 410. Google removes it after recrawling; a 410 tends to clear slightly faster.
• Add a noindex tag or X-Robots-Tag header if the page should stay live for visitors but out of Google. The page must remain crawlable so Google can read the tag.
• Put it behind a login. Googlebot hits the same wall as any logged-out visitor, and the content drops out.

The classic mistake is reaching for robots.txt instead. A Disallow rule blocks crawling, not indexing: the URL can linger in results as a bare link, and Google can no longer fetch the page to see your noindex. Keep the page crawlable until it drops out. Our robots.txt tester shows what your file currently blocks.

Removing pages on sites you don't own

No Search Console property, no Removals tool. You still have two routes:

• The Refresh Outdated Content tool, public and free, for results that no longer match the live page: the page was deleted, or the sensitive content on it was changed. Google re-checks the page and updates or drops the result.
• Legal removal requests for copyright, defamation, doxxing and explicit personal content, via Google's legal request forms. Slower, but the only lever when the site owner won't act.

Remove a user or owner from a property

The third meaning of "remove": the agency you stopped working with, the employee who left. Delegated users are easy; owners are the part people get stuck on.

1. Open Settings → Users and permissions as a verified owner.
2. For a delegated user (Full or Restricted), open the three-dot menu on their row and choose Remove access. It takes effect immediately.
3. For a verified owner, find their token. Ownership comes from verification, not from the user list. Check for their HTML verification file on your server, their meta tag in your homepage source, their DNS TXT record, and any Google Analytics or Tag Manager verification tied to their account.
4. Delete every token they hold. Their ownership lapses once no verification method survives. Miss one, and they quietly keep full access.
5. On a hosted builder, check the builder's own fields too. A verification tag pasted into a header-code box counts as a live token. Ours on Weebly and Wix verification shows where each platform stores it.

When the removal doesn't take

Four failure modes cover nearly every "it didn't work":

• "I removed the property but the site is still on Google." Expected: property removal never touches search results. Use the Removals tool plus a permanent signal, per the section above.
• "The URL came back after a few months." The Removals request expired and the page still returned 200 with no noindex. Fix the page state; the reappearance stops.
• "My removal request was denied." Usually the URL pattern didn't match the property, or the request duplicated an active one. Check the exact URL and protocol against the property type, and submit from the property that actually contains the URL.
• "The page is gone from Google but I never asked." Different problem entirely: check the Page indexing report for a stray noindex, a canonical pointing elsewhere, or a crawl block. Accidental deindexing looks identical to deliberate removal from the outside.

That last case is worth automating away. A stray noindex that ships to production does the Removals tool's job on pages you wanted to keep, and nothing in Search Console emails you about it. CrawlRaven's crawl checks every page's indexability against your indexation data daily, precisely so deliberate removals stay the only kind you have.