After multiple crawls, 404 pages are still in the SearchG2 collection
.NET default behavior for custom errors is a 302, not a 404. As a result G2 will keep the file in the index. It must have a 404 response code in order to remove. The changes are below
First make sure the 404 error handling is using ResponseRewrite:
<customErrors mode="On" redirectMode="ResponseRewrite">
<error statusCode="404" redirect="404.aspx" />
Then make sure the page itself is setting the 404 error:
<script runat="server" language="c#">
protected void Page_Load(object sender, EventArgs e)
Response.StatusCode = 404;
Peer-to-peer support and answers on developing CMS templates, modifying privacy scripts or building integrations.
Find answers and ask questions on content management, personalization and targeting.
Find answers and ask questions on WCAG and SEO quality management.
Find answers and ask questions on consent and monitoring solutions.