[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Remove many URLs from Google Search in bulk

> Submit temporary URL removals in Google Search Console for a whole list of old or sensitive pages, without repeating the form for each URL.

Source: https://cotlet.dev/integrations/google-search-console-api-mcp-server/remove-urls-from-google-in-bulk

After a clean-up, a migration or a leak, a long list of URLs has to leave Google results fast, and the Removals tool takes them through its form one request at a time.

Cotlet does it in your own Google Search Console account with list\_removals and request\_url\_removal, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=google-search-console) [All Google Search Console tools](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Google Search Console do this on its own?

The Search Console API has no methods for removals (checked 16 Oct 2026). Google offers the Removals tool only in the web interface, for owners and full users of the property.

## How you do it in Google Search Console today

1. In Search Console open Removals and choose New request on the Temporary Removals tab.
2. Pick Temporarily remove URL, or Clear snippet in search to only wipe the description until the page is indexed again.
3. Choose Remove this URL only, or Remove all URLs with this prefix, and enter the URL exactly, including extension and casing.
4. Submit, then repeat for every other URL; the request history on the same screen shows the past 6 months.
5. A successful request lasts only about six months, so the page needs a 404 or 410, a password or a noindex tag before it expires.

## How to remove many URLs from Google Search in bulk

Prompt

```
These 30 URLs on example.com are gone or should not show up. Check which ones already have a removal request, then submit a temporary removal for the rest and list what I still need to fix on the site.
```

1. 01  
### Read what is already filed  
list\_removals returns the request history of the property, so URLs that already have a pending or active removal are skipped instead of filed twice.
2. 02  
### Normalize the list  
Google treats each URL variant as its own request, so the agent files the exact URLs you gave and asks before adding other casings or parameter versions.
3. 03  
### Choose single URL or prefix  
A list of unrelated pages is filed one by one with Remove this URL only. A whole folder is filed as a prefix, which hides everything under it, so the agent states how wide the prefix is before sending.
4. 04  
### File the requests  
request\_url\_removal submits each one after your OK. Removals hide pages from results quickly, and Google says requests usually take up to a day and are not guaranteed to be accepted.
5. 05  
### List the permanent fixes  
Because a removal lasts about six months, the agent ends with the URLs that still need a 404, a 410, a password or noindex on your site, and a date to check again.

### What you get back

Example data

```
URLs in your list: 30
Already have a removal: 4
Filed as single URL: 21
Filed as prefix: 1 (/old-promo/, hides everything under it)
Skipped: 4 (not in this property)
Still to fix on the site: all 22 filed requests need a 404, 410, noindex or a password before the removal ends
```

### Other ways to ask

- Clear the cached snippet for these 5 pages whose description is outdated, but keep them in results.
- List every removal request from the last 6 months with its status, so I can see which ones expire soon.
- Remove everything under /staging/ as a prefix and then tell me what is left to block.

## What Google Search Console allows, and what to know first

- Google says you must own the property in Search Console to use the Removals tool.
- A successful temporary removal lasts only about six months; after that the page can show up again unless it returns 404 or 410, is password-protected or has noindex.
- Google says each URL variant, such as different casing or parameters, needs its own request, and anchors are ignored.
- Requests cover the http and https and www and non-www versions of a URL, but not other subdomains such as m.
- Blocking a URL hides it from results but does not stop Google from crawling it, and Google warns against using robots.txt as the blocking mechanism.

request\_url\_removal asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.

Sources: [Search Console Help: Removals tool](https://support.google.com/webmasters/answer/9689846) · [Search Console API: resources and methods](https://developers.google.com/webmaster-tools/v1/api%5Freference%5Findex)

## Call request\_url\_removal from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/google-search-console/url-removal/request \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"property":"sc-domain:example.com","url":"https://example.com/old-promo/spring-sale","type":"temporarily_remove_url","scope":"url_only"}'
```

Example response

```
{
"request_id": "rm_9c21",
"url": "https://example.com/old-promo/spring-sale",
"type": "temporarily_remove_url",
"scope": "url_only",
"status": "pending",
"lasts": "about 6 months"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is google\_search\_console\_write → request\_url\_removal. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md#automations)

## Google Search Console tools this automation uses

__Cotlet Google Search Console tools used to remove many URLs from Google Search in bulk__
| Tool | Parameters |
| --------------------- | -------------------------- |
| list\_removals | property |
| request\_url\_removal | property, url, type, scope |

[All 15 Google Search Console tools with descriptions](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Google Search Console to Cotlet?

Yes. You sign in to Google Search Console yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Google Search Console once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Google Search Console automations

- [Request indexing in Google Search Console in bulk](https://cotlet.dev/integrations/google-search-console-api-mcp-server/request-indexing-in-bulk.md)
- [Export all not-indexed URLs from Google Search Console](https://cotlet.dev/integrations/google-search-console-api-mcp-server/export-not-indexed-urls.md)
- [Add a user to many Search Console properties](https://cotlet.dev/integrations/google-search-console-api-mcp-server/add-user-to-many-properties.md)
- [Google Search Console API and MCP server: every tool](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Google Search Console.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Google Search Console.

[Sign up free](https://cotlet.dev/app/signup?app=google-search-console)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.