Fixes

How to fix “Discovered - currently not indexed” on Drupal

If Search Console shows “Discovered - currently not indexed” on your Drupal site, you are in the right place. Google knows the URL but has not crawled it yet. This page covers the causes and a step-by-step fix for Drupal. A flexible, module-based CMS. The Metatag, Simple XML Sitemap and Redirect modules provide indexing control.

Updated: 07.11.2026 · 2 min read · Türkçe

Contents
  1. What does this status mean?
  2. Likely causes on Drupal
  3. Step-by-step fix on Drupal
  4. Extra checks for Drupal
  5. After fixing
  6. More information

What does this status mean?

The URL was discovered from your sitemap or a link, but Googlebot has not visited it yet. It usually comes from crawl budget, server load or the page being treated as low priority.

Likely causes on Drupal

  • The site is large and Google cannot get to every URL.
  • The server is slow or throws errors and Googlebot slows down to be polite.
  • Many low-value URLs (filters, parameters) fill the crawl queue.
  • No internal links; an orphan page known only from the sitemap.
  • Drupal note: Install Simple XML Sitemap, pick content types and submit the resulting /sitemap.xml. Leave out types that should not be indexed.

Step-by-step fix on Drupal

  1. In your Drupal admin go to: Configuration > Search and metadata (Metatag, Simple XML Sitemap, Redirect).
  2. Install Simple XML Sitemap, pick content types and submit the resulting /sitemap.xml. Leave out types that should not be indexed.
  3. On the Performance screen enable page and block caching and CSS/JS aggregation; the dynamic page cache lowers server load.
  4. Link to important pages directly from the home page and category pages.
  5. Put only canonical, 200-returning URLs you want indexed in the sitemap.
  6. Take filter and parameter URLs out of crawling with robots.txt or canonicals.
  7. Lower server response time and error rate; watch response time in Search Console crawl stats.
  8. Send priority URLs through an indexing panel and follow progress with URL inspection in Search Console.

Extra checks for Drupal

  • robots.txt: Edit robots.txt in the web root or manage it with the RobotsTxt module. On multisite setups each site needs its own file.
  • canonical and duplicate URLs: The Metatag canonical field uses [current-page:url] by default. Stop view filters and pager parameters from surfacing as separate URLs.

After fixing

In Search Console start "Validate fix" for this status and resubmit the page with URL inspection. First confirm the blocker is gone with the free Free indexability checker tool; for many URLs follow Bulk URL indexing: how to send thousands of pages to Google. Google makes the indexing decision itself and timing ranges from days to weeks.

More information

Frequently asked questions

What is the difference between "Discovered" and "Crawled"?

"Discovered" means Google knows the URL but has not visited; "Crawled" means it visited but did not index. The first is usually about crawl priority, the second about content quality.

Thousands of my pages have this status. What now?

First decide which ones truly need indexing and remove the rest from the sitemap and internal links. Work in priority order instead of forcing every URL at once.

Where are these settings on Drupal?

Configuration > Search and metadata (Metatag, Simple XML Sitemap, Redirect).

Related pages