If you have a lot of URLs returning a 410 status code and also marked them with a noindex directive, and you’re seeing consistent noindex records in Google Search Console, here are a few potential reasons and considerations:

Reasons for Persistent Noindex Records in Google Search Console

1. Crawl Lag: Googlebot might take some time to re-crawl the URLs and recognize the 410 status. During this period, the noindex directive might still be recorded.
2. Crawling Frequency: If your site has a low crawl rate, it may take longer for Google to process the changes and update the status in Search Console.
3. Directive Conflict: While the 410 status is definitive, the presence of a noindex tag might still be getting recorded if Googlebot had previously cached these URLs and their directives.
4. Reporting Lag: Google Search Console data can sometimes lag behind actual crawl and indexing activities. This means the noindex records might be older than your current status of the URLs.

Recommendations

1. Monitor Crawl Stats: Check the crawl stats in Google Search Console to see how frequently Googlebot is crawling your site. This will give you an idea of how quickly Google is likely to recognize the changes.
2. Fetch as Google: Use the URL Inspection tool in Google Search Console to fetch and render the 410 URLs. This can prompt Google to update its status on these pages more quickly.
3. Sitemap Update: Ensure your sitemap is updated and does not include the 410 URLs. This helps guide Google to focus on the correct URLs.
4. Check Robots.txt: Make sure you haven’t blocked the crawling of these URLs in your robots.txt file. While unlikely, this could prevent Googlebot from confirming the 410 status.
5. Patience: Sometimes, it just takes a bit of time for Google to fully process the changes, especially with a large number of URLs.

Steps to Verify and Speed Up the Process

1. URL Inspection Tool:
   • Go to Google Search Console.
   • Use the URL Inspection tool to check individual URLs and see how Google is currently processing them.
2. Request Reindexing:
   • For URLs showing as noindex but should be recognized as 410, request reindexing using the URL Inspection tool after confirming their 410 status.
3. Log File Analysis:
   • Review your server log files to see how often Googlebot is hitting these 410 URLs. This can give insight into how quickly Google is processing the changes.
4. Keep Track of Changes:
   • Maintain a record of when URLs were deleted and marked as 410 to correlate with Google Search Console data.

By following these steps and ensuring there are no conflicting signals, Google should eventually clear the noindex records and correctly reflect the 410 status for these URLs. If the issue persists, consider reaching out to Google Search Console support for more detailed assistance.