You deleted a page in your CMS, but its URL still appears in Google. First check what the old address actually returns now. A removed CMS record may still be served from a static file, a cache, a redirect, or a custom “not found” screen with HTTP 200. Google cannot react to the deletion you intended; it must see an appropriate response when it revisits the URL. The right fix depends on whether visitors should find a replacement, a genuine gone page, or a private page.
Follow the old URL, including its redirects
Request the exact URL shown in Search, then inspect the status and final destination. For example, curl -I 'https://example.com/old-path' gives a quick header check, but some sites handle HEAD differently from GET; confirm with a normal GET or your browser's network panel when results disagree. Check http/https, www/non-www, trailing slash, case and meaningful query parameters against your site's routing. Record the response chain, not just the final page title.
If the content truly moved, use a server-side permanent redirect to a close equivalent. A homepage is usually not an equivalent replacement for a discontinued, specific article or product. Google's redirect guidance treats permanent redirects as a strong canonical signal and warns against redirecting many old URLs to an irrelevant destination. If there is no useful substitute, return 404 or 410 and keep a helpful not-found page for visitors. Google's HTTP status guidance says both 404 and 410 signal that the page does not exist; do not promise 410 will remove it within a fixed number of hours.
Check the cases that look deleted but are not
- Soft 404: A missing page shows a “not found” message but returns 200, or many unrelated URLs redirect to the same unhelpful destination. Fix the server behavior instead of relying on the visible message.
- Still needed by members: Protect it with authentication if the content is sensitive.
noindexon a publicly accessible page can remove it from Google results after recrawling, but it does not make the content private. - Blocked by robots.txt: Do not add a
Disallowrule as a substitute for removal. If Google cannot crawl the URL, it may not see the 404/410 ornoindex. Google's removal guidance explicitly cautions against using robots.txt for this purpose. - Old copy elsewhere: Check alternate URL forms, a PDF attachment, translated copies or a cached static route. Treat each live copy by its actual URL and content; one removal request is not a universal content deletion.
When you need the search result hidden promptly
For a verified property you own, Search Console's Removals tool can temporarily block a precise URL or a prefix. A precise request matches that URL, including its parameters and extension; a prefix request can cover more than you intended, so inspect the scope first. Google's help says the request generally lasts about six months and does not prevent crawling or erase content from the web. Make the on-site change as well: remove or update content, require a password, or use noindex when public access remains appropriate. Routine old 404s need not all receive an urgent request.
If you do not own the site, the owner's Search Console Removals tool is not available to you. Google's Refresh Outdated Content tool applies when the external page has disappeared or changed but its old result persists; it is not a way to delete material that is still live on someone else's site. If a live page merely has an outdated title or snippet, update the page and use URL Inspection for a small number of important URLs instead of deleting a valid page.
Finish with a URL inventory, not an indexing trick
Remove truly gone URLs from the sitemap and relevant navigation or related-content links; put the replacement's preferred URL in the sitemap if content moved. Google's sitemap guidance says submissions are hints, not a removal command. In URL Inspection, distinguish the live test from Google's last indexed view: a live 404 and a still-visible result can coexist until recrawling and processing. Keep a short record of the old URL, observed status, chosen destination or removal signal, and the later Search Console result. No fixed crawl count or calendar deadline follows from this check.
The Indexing API's URL_DELETED method does not make it a general deletion channel: Google's API documentation limits supported pages to JobPosting or BroadcastEvent embedded in VideoObject. Ordinary pages use their real response, the site-owner removal tool when urgent, and normal crawling. Guangsuan's technical SEO overview also covers redirects, 404s and sitemap hygiene as part of site maintenance.