# An old page should disappear from search. Which removal action fits?

Distinguish an urgent temporary Google Search removal from removing public access, retiring a page and keeping a useful page out of the index.

By AdzUp Editorial | 2026-11-21

## State what must stop happening

An expired offer, an obsolete vacancy and a mistakenly public document are different problems. Before asking an agency to remove a URL, write the intended outcome: should visitors still reach the page, should search engines stop listing it, or should nobody outside an authorised group access its content? That sentence prevents a search setting from being mistaken for an access-control solution.

This decision guide draws on current Google removal and indexing documentation checked on 21 November 2026. It is not a report of a newly released feature. Assign a business owner to approve the outcome and a technical owner to implement it. When exposed material is sensitive, address access immediately through the appropriate security process rather than waiting for a search result to change.



## Use temporary hiding for the right purpose

Google Search Console's Removals tool can temporarily hide a qualifying URL from Google Search for about six months. Google's documentation explicitly distinguishes that temporary action from a permanent solution. Treat an urgent request as one task in a larger incident or publishing checklist, with an owner assigned to the underlying page. Do not close the task merely because the result stops appearing in a spot check.

Before submitting, verify the property, exact URL and intended scope. A request affecting a URL prefix needs particular care because unrelated pages can share the same path. Preserve the approval and explain which search engine the request concerns. A Google Search action is not a universal internet deletion process and does not establish that copies, direct links or other services have disappeared.



## Choose a durable treatment for the page

For a page that remains useful to direct visitors but should not appear in Google Search, a correctly implemented noindex instruction may fit. Google must be able to crawl the resource to discover that instruction; blocking crawling in robots.txt can prevent that. For a retired resource, the removal documentation describes returning an appropriate 404 or 410 response. Restricted information needs actual access controls, not a discoverability preference.

Ask the developer to show the live response, not just the setting inside the CMS. A page can look removed while still returning a normal successful response containing an error message. A downloadable file also needs its own review: removing the link on an HTML page does not remove the file itself. Match the implementation to the approved outcome and verify every relevant destination.



## Follow the paths that visitors still use

Illustrative example: an education provider retires last year's admissions offer. The team inventories its landing page, brochure, navigation links and old advertisement destinations. It decides which information is genuinely obsolete and whether there is a useful current destination for visitors. The reviewer checks that the brochure is not still publicly available at an unchanged file URL after the visible download button has been removed.

This is a hypothetical workflow, not a result from a client campaign. Apply the same method to outdated service locations or recruitment pages. Look beyond the main menu: automated emails, social posts and shared PDFs may still send people to the old URL. Update the links the business controls and make the remaining visitor experience clear, without misleading people into thinking the expired offer is still available.



## Keep a verification and review record

Record the URL, approved objective, implemented treatment, test result and follow-up owner. Confirm direct access behaviour and inspect the relevant indexing instruction or status response. Check that the change did not accidentally apply across an entire service directory. Search appearances can take time to update; keep the distinction between a successful website change and a subsequently observed search change in the handover.

Set a review reminder for any temporary request and retain a rollback plan for an accidental removal. Include future publishing safeguards such as explicit expiry ownership and restricted draft storage. The useful success criterion is specific: the resource behaves as approved and the business has evidence of the change. Neither a temporary hide nor noindex should be presented as a guarantee that confidential information has been erased from everywhere.



## Sources

- [Google Search Console: Removals and SafeSearch reports tool](https://support.google.com/webmasters/answer/9689846?hl=en)
- [Google Search Central: Block Search indexing with noindex](https://developers.google.com/search/docs/crawling-indexing/block-indexing)
