Skip to content

Google removed a URL temporarily. How do you keep it out?

Use Search Console's temporary removals tool with the right permanent fix for a deleted file, a private page, or useful content that must leave Search.

By Crawlito · 5 min read

In short

  • A successful temporary removal generally hides a URL from Google Search for about six months.
  • The lasting fix depends on whether visitors should still be able to open the document.
  • URL variants, asset links, and unintended prefix matches deserve separate checks.
On this page

A temporary removal in Search Console gives you time to change what your server serves. To keep a URL out after that period, remove the content, protect it with authentication, or apply an index exclusion that Google can read. Pick the change based on who still needs to open the document. Google’s Removals tool instructions

Start with the address a person can still open

Suppose a retired conference brochure appears in Search. The result might link directly to a PDF on the media host even though the page linking to it was deleted last week. Open the copied result in a clean browser and save the final address. Check which document you actually received. A success status, a branded error screen, a redirect to a newer brochure, and a login challenge each tell you something different about the present state.

Write down the addresses that distribute the same material. Include the CMS attachment URL, direct asset link, and alternate public host if they exist. A request concerning the landing page cannot change the access policy at the asset host. Links in newsletters may also bypass the website entirely. Focus first on the copies your organization controls, where you can observe the response and change its behavior.

For sensitive material, arrange the access change immediately. Anyone with the URL can still try the server while the removal is processing. Keep private filenames and document text out of shared screenshots. An incident owner can retain an access-controlled record of the exact addresses and give developers sanitized routes for regression tests. The guide to login and paywall behavior helps distinguish an access requirement from a search preference.

Choose the lasting state for each copy

What people still needChange at the sourceWhat to test from a fresh session
Nobody needs the old resourceRemove it and return a genuine 404 or 410The old address returns that status and does not stream the document
Only authorized staff need itEnforce authentication on the document and its assetsAn anonymous request cannot retrieve the protected content
Anyone with the link can read it, but it should leave SearchPublish a supported noindex directive and allow the crawler to fetch itThe public response contains the directive on the target URL

A published memo might still be needed by people who received an email link. Putting a noindex meta tag in the HTML can suit that requirement. A PDF cannot contain an HTML head that sets that directive for its HTTP response. The server delivering the PDF can send an X-Robots-Tag header instead. Test the file directly, including redirects. Applying the header to its download landing page does a different job. See how PDF documents are discovered and Google’s robots directives reference.

A site owner may reach for a robots.txt disallow as soon as a private-looking address appears. That prevents a cooperating crawler from obtaining instructions on the blocked resource and leaves the public URL usable by people. In the public-but-excluded case, the fetch is the way Google discovers the directive. In the private case, the server must make the access decision for every caller.

Submit the narrowest removal that covers the incident

Check the selected Search Console property and the action described on the confirmation screen. Google distinguishes temporarily removing a URL from clearing the search snippet. A stale snippet on a still-useful page calls for a different decision from hiding the result itself. When the author has corrected the page and wants it to keep showing, discuss the snippet option before requesting a wider removal.

A prefix can cover many addresses. Before submitting one, compare it with a small list of real URLs that must remain visible, including neighboring paths with similar names. If a whole directory represents the old event, write down its boundary and the exceptions. If only one brochure is involved, submit precisely the URL or variants that the documented matching rules require. Someone reviewing the incident later should be able to see which result you meant to hide.

Record the request date, the request type, the state reported by Search Console, and the date of the permanent site change separately. Google's help describes a successful block as lasting about six months. An active temporary removal can make a search screenshot look satisfactory while the file continues to be public and indexable. The durable test lives at the serving URL.

Verify the origin and the search result independently

For a public file intended to carry an exclusion header, this request saves the headers across redirects and discards the content. Inspect the final response. For a deleted page, also inspect a harmless portion of the returned page to rule out a generic home-screen fallback.

bash
curl -sSL -D response-headers.txt -o /dev/null https://example.com/media/retired-brochure.pdf

Run the check anonymously. An administrator's working session can make a secure staff file look public. Conversely, a cached browser tab can display material after the server has stopped serving it. For a retired resource, review the old link from another referring page and check the public sitemap. A route still listed there can reveal an active publishing job that will recreate the file after your manual edit.

Set a follow-up tied to the next normal release or content import. Test the same addresses after that process has run. The soft 404 guide explains why visually deleting an article while returning HTTP success can yield misleading results. Keep one known-good public neighbor in the test set to catch a broader-than-intended rule. The desired outcome includes people still being able to find the material that was supposed to stay.

Test whether an old file can come back under a new URL

A frequent publishing pattern creates a fresh media URL each time an editor replaces a document. The old brochure then disappears from the visible page while the original file still exists at its first address. Search a sample of previously sent public links, compare the file mapping in the media library, and ask the storage owner which versions the public host can still serve. Add each confirmed public copy to the incident record.

After the correction, try the direct file link with a fresh request and follow the current download action from the maintained page. These are two separate customer journeys. The retired URL should match the chosen removal policy and the live download should still deliver the intended replacement. Add a harmless control file from the same directory to the test. It catches an access rule that inadvertently hid the organization's entire public media library while fixing a single brochure.

Frequently asked questions

Does a Google removal delete the file from the web?

The tool affects Google Search. Check the origin, asset host, and any copies under your control to determine whether people can retrieve the file.

Can I hide only the description while leaving the result?

Search Console offers a distinct action to clear the snippet until Google crawls the page again. Review the action description and correct the source content that produced the snippet.

What if my request expires and the result returns?

Retest the exact returned URL and its variants. Check whether the permanent response or index directive survived the latest deployment and whether Google could read it.

Inspect a public replacement

When an old public guide has a successor, check the replacement page to confirm that its content and index signals are readable. Keep confidential URLs in your own access tests.

Filed under Access and robots.txt. Topics: google, noindex, search-console