To remove a page from Google Search, first decide whether the page should remain available to visitors. Use a crawlable noindex rule if people still need the public URL, remove the page and return an appropriate error status if it is gone, or restrict access if the content should no longer be public. For urgent visibility in Google Search, the Search Console Removals tool can add a temporary block while the lasting change takes effect.
These choices solve different problems. A retired campaign page, an internal document accidentally made public and an old page with a suitable replacement may each need a different response. Start with the intended experience for someone who already has the link, then select the search control.
Decide what should happen to visitors
The table below is a practical starting point for pages you control. Check every affected URL and its public response before treating the job as complete.
| Situation | Action to consider | What to verify |
|---|---|---|
| The page should stay public but leave Google Search | Add a noindex rule and allow Google to crawl it | The public response contains the rule and robots.txt does not block Googlebot |
| The page is permanently gone with no equivalent replacement | Return an appropriate missing-page status, such as 404 or 410 | The URL returns that status rather than a successful page with an error message |
| The content has moved to a genuinely relevant replacement | Redirect the old URL to the replacement | The destination works and gives visitors the information they expected |
| The content should be accessible only to authorized people | Restrict access at the server or application | An unauthenticated visitor cannot retrieve the content |
| The result needs to disappear from Google Search urgently | Consider a Search Console temporary removal alongside a lasting change | The request covers the intended URL and the lasting change is in place |
A redirect is useful when there is a close replacement, such as a service page moved to a new address. Sending every retired page to the home page can leave visitors unable to find the information they expected. If a whole site is moving, use the website migration SEO checklist to plan URL mapping and launch checks.
Use noindex when the page must remain public
A noindex rule tells supporting search engines not to index a page. Google supports the rule in a page's robots meta tag or in an HTTP response header. The header can also be useful for files that do not have an HTML head, such as a PDF. Google must crawl the resource and encounter the rule before it can act on it. See Google's noindex documentation.
For example, a business might keep an old event recap accessible to people with a direct link but decide it no longer belongs in search results. The team can apply noindex to that URL, then check the actual public response rather than relying only on the content management system's setting. Check both the page source and response headers if different systems can add directives: a template, proxy or content delivery layer may change the final response.
Do not block the same page in robots.txt before Google can read noindex. Google's robots.txt guide explains that a blocked URL can still appear in search results when Google discovers it elsewhere. A crawl restriction and an indexing instruction are different controls.
Noindex is not an access restriction. Anyone who can reach a public URL may still view or share it. If a document should be private, remove it from public access or require authentication. Also check whether the same material is available at another address or in a downloadable file. The separate guide to choosing between a PDF and its web page in search covers that publishing decision.
Remove a retired page or send visitors to its replacement
When content is gone and there is no useful replacement, the server should communicate that the requested resource is missing. A 404 response says the resource was not found and does not itself say whether the absence is temporary or permanent. A 410 response indicates that the resource is likely permanently unavailable, according to MDN's 410 reference. Choose the status that reflects the situation; neither should be treated as an instant removal button.
Pay attention to the response status, not just the design of the error page. A friendly page saying an offer has ended can still return a successful status if the application is misconfigured. Test the public URL after deployment, including any final response after redirects. If a relevant replacement exists, check that the old address leads there and that the destination is accessible without an unexpected login or error.
Update internal links that still point to the retired URL. Remove it from the sitemap if it is no longer a page you want indexed. These housekeeping steps help visitors and make the intended site structure easier to maintain, but they are not a substitute for the response or indexing rule at the URL itself. For a product that might return, assess availability separately using the out-of-stock product SEO guide.
Use temporary removal for urgency, then verify the lasting fix
If a result needs to disappear quickly, an owner of the relevant Search Console property can request a temporary removal. Google says a successful block generally lasts about six months and applies to Google Search, not the internet as a whole. The request alone does not permanently remove the URL; see the Search Console Removals tool documentation.
Before submitting a request, copy the URL that appears in the result and decide whether to target that URL or a prefix. A prefix request can affect more pages than intended, so review its scope carefully. Record the request and assign an owner to check the underlying fix. If the page remains public and indexable after the temporary block expires, it can appear again.
For content that should not be public, address access at the source promptly. A search removal does not stop someone with the URL from visiting the page, and it does not remove copies hosted elsewhere. Search Console is useful for managing Google's results, while the website response determines what the site itself serves.
Check the result and avoid common mistakes
Use URL Inspection in Search Console to review Google's information about a specific URL and inspect the live page where available. A live test shows what Google can access during that test; it does not mean the existing search result has already changed. Recrawling and processing take time, so record the check date and revisit the URL rather than promising a removal deadline.
Look beyond the first address on your list. The same content may have separate HTTP and HTTPS addresses, parameter variants, alternate file URLs or copies on another host. Test each relevant version and confirm that redirects, access controls and indexing rules lead to the intended outcome. If an unexpected URL remains visible, investigate its own response and crawl access before repeating a removal request.
Common mistakes include treating robots.txt as a reliable way to remove an indexed URL, putting noindex on a page Google cannot crawl, assuming a temporary removal protects the underlying content, and redirecting unrelated retired pages to a generic destination. Another frequent oversight is checking a CMS preview instead of the public response after caching and delivery layers have applied their changes.
Removal checklist and next step
- List the exact URLs and decide whether each should remain public, move, disappear or require authentication.
- Check for alternate URLs and downloadable copies that contain the same material.
- Apply the selected response, redirect, access restriction or noindex rule at each relevant URL.
- For noindex, confirm that Googlebot can crawl the page and see the rule.
- If urgency warrants it, submit a carefully scoped Search Console removal request and record its owner.
- Update internal links and sitemaps, then test the public response after deployment.
- Recheck Search Console and the affected results later, keeping a record of what was observed and when.
Start with one retired URL. Have the content owner decide what visitors should see, then ask the site team to verify the public response and document the result. Apply the same decision process to the remaining URLs instead of applying one blanket rule to the entire site.
India
UAE
KSA
USA
UK
Canada
Oman
Kuwait
Australia
Thailand