Google Search Console removals can temporarily hide a URL from Google Search when you control the property. Use this tool for a specific removal need, and pair it with the appropriate change on your website.
Back to the Google Search Console guide
Temporary removal is not a permanent fix
A temporary removal generally lasts about six months. It hides the search result; it does not delete the content from WordPress or make a public file private. For a lasting result, remove the content, require authentication, or apply an appropriate noindex instruction. Robots.txt alone is not a permanent removal method.
Choose the action that matches the problem
| Situation | Website action to investigate |
|---|---|
| A private document became public | Remove public access to the actual file. |
| A page was permanently retired | Remove it, or redirect it to a genuinely relevant replacement. |
| A public utility page should not appear in Search | Consider a crawlable noindex instruction. |
| Hacked content appeared on your domain | Clean the compromise and affected URLs. |
Determine the intended final state before opening the request form. That decision prevents a temporary tool from becoming a substitute for site maintenance.
Submit a carefully scoped request
- Open the correct property and select Removals → Temporary Removals.
- Choose New Request and the temporary removal option.
- Enter the affected URL and review whether the request targets one URL or a prefix.
- Confirm that the scope matches exactly what you intend to hide.
- Review the request status and verify the lasting website change separately.
A prefix request can affect a whole section. Before using one, write down examples of URLs that should and should not be covered. Never use the domain root when you intend to hide only one article or file.
A WordPress media-library example
Suppose an internal PDF was uploaded to WordPress and linked from a public page. Removing the link from that page may leave the PDF accessible at its direct uploads URL. First check the actual file address while signed out.
Identify where the file is stored, remove or protect the public copy, and account for relevant caches. Then address its Google result. A private WordPress page containing a link does not automatically protect a separate media file.
Keep a record of the original URL, where you found it, the website change and the verification result. The important outcome is that an unauthorized visitor can no longer retrieve the private content, not just that one search result disappeared.
Use a different workflow for routine SEO cleanup
Do not use Removals merely because the Page indexing report contains excluded URLs. Old redirects and intentional exclusions may be normal. Hiding a useful page can reduce its visibility without solving the underlying problem.
If a service page moved, check its redirect and update internal links. If a page contains outdated public information, update the page and inspect it with URL Inspection. Choose the workflow based on whether you want the page retained, replaced or removed.
Hacked URLs need cleanup at the source
If unexpected spam pages appear, use the hacked WordPress recovery guide to address the compromise. Temporary hiding cannot repair vulnerable code or stop an attacker from generating more URLs.
See the hacked law firm website case study for an example of a broader recovery project involving technical cleanup.
Frequently asked questions
Can I undo a temporary removal?
Google provides a cancellation option in the request history. Canceling the request does not repair website changes you made separately.
Does this remove a page from the internet?
No. It affects Google Search. The site’s own access controls and content determine whether people can retrieve the page directly.
Can I remove another site’s content here?
This workflow is for a property you control. Google’s separate outdated-content process has a different purpose and does not grant editing access to someone else’s website.
Reference: Google’s Removals documentation.
