Google Search Console is one of the most important technical tools available to website owners, administrators, developers, publishers, and SEO professionals. However, some of its reports can easily be misunderstood.

One particularly common misunderstanding occurs in:

Google Search Console → Indexing → Sitemaps

After submitting an XML sitemap, Search Console may display information such as:

• Sitemap URL
• Type
• Submitted date
• Last read date
• Status
• Discovered pages
• Discovered videos

A website administrator may see, for example:

Status: Success
Discovered pages: 1,894

It is very tempting to conclude:

“Google has indexed 1,894 pages of my website.”

That conclusion is not necessarily correct.

The number shown under Discovered pages represents URLs Google discovered through that sitemap. It is not a direct count of URLs currently indexed and eligible to appear in Google Search.

Understanding this distinction is extremely important when auditing a website's SEO and indexing health.

1. What Is an XML Sitemap?

An XML sitemap is a machine-readable file that provides search engines with a list of URLs that the website owner wants search engines to discover.

A typical sitemap might be available at:

https://example.com/sitemap.xml

A simplified sitemap could contain:

<?xml version="1.0" encoding="UTF-8"?>

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

<url>
    <loc>https://example.com/</loc>
</url>

<url>
    <loc>https://example.com/article.php?id=101</loc>
</url>

<url>
    <loc>https://example.com/article.php?id=102</loc>
</url>

</urlset>

The sitemap essentially tells Google:

“These are URLs on my website that I would like you to discover and consider crawling.”

It does not command Google to index every URL.

2. What Does “Submitted Sitemap” Mean?

When you add a sitemap through Google Search Console, it appears under:

Indexing → Sitemaps → Submitted sitemaps

For example:

Sitemap	Type	Status	Discovered Pages
sitemap.xml	Sitemap	Success	1,894

This means Google successfully processed the sitemap and discovered approximately 1,894 page URLs from it.

It does not automatically mean all 1,894 pages are indexed.

3. What Does “Status: Success” Mean?

A Success status is generally positive.

It indicates that Google was able to retrieve and process the sitemap successfully.

It generally tells you that there is no major sitemap-level problem preventing Google from processing the file.

However:

Sitemap Success ≠ All URLs Indexed

These are separate concepts.

A sitemap could contain thousands of URLs and show Success, while only a portion of those URLs are currently indexed.

4. What Does “Discovered Pages” Mean?

This is the most important concept.

Suppose Search Console shows:

Discovered pages: 1,894

This means Google has identified approximately 1,894 page URLs through that sitemap.

Think of it as:

URLs declared/discovered through sitemap → 1,894

rather than:

URLs confirmed in Google's index → 1,894

Those URLs must still go through Google's normal crawling, canonicalization, quality assessment, and indexing systems.

5. Discovery, Crawling and Indexing Are Different Stages

A useful simplified model is:

Sitemap → Discovery → Crawl → Processing → Canonical Selection → Indexing → Search Results

These stages should not be treated as identical.

Stage 1 – Discovery

Google learns that a URL exists.

Sources can include:

• XML sitemaps
• Internal links
• External backlinks
• Previously crawled URLs
• Redirects
• Canonical references
• Other discovery mechanisms

Stage 2 – Crawling

Googlebot requests the URL from the web server.

For example:

GET /article.php?id=101

The server may return:

HTTP/1.1 200 OK

But receiving HTTP 200 still doesn't guarantee indexing.

Stage 3 – Processing

Google processes information from the page, potentially including:

• HTML
• Main content
• Links
• metadata
• canonical directives
• robots directives
• structured data
• duplication signals

Stage 4 – Canonicalization

Google determines which URL should represent a piece of content when multiple URLs are substantially similar.

For example:

example.com/article.php?id=100

and

example.com/article.php?id=100&utm_source=newsletter

may lead Google to select one canonical URL.

Stage 5 – Indexing

If Google decides that the page is suitable for indexing, the selected canonical URL may be stored in Google's search index.

Only at this stage should we describe the URL as indexed.

6. Discovered Pages vs Indexed Pages

The distinction can be summarized as follows:

Metric	Meaning
Sitemap submitted	Sitemap has been provided to Google
Sitemap Success	Google could process the sitemap
Discovered pages	URLs Google found through the sitemap
Crawled page	Googlebot retrieved the URL
Indexed page	Google selected/stored the page for its search index
Search impression	The indexed page appeared in a user's search results

Therefore:

Discovered ≠ Crawled ≠ Indexed ≠ Ranking

These are different stages.

7. Example: Sitemap Contains 1,894 URLs

Suppose your website's sitemap report shows:

Discovered pages: 1,894

This tells us that Google has successfully discovered approximately 1,894 URLs from the sitemap.

It does not tell us how many of those URLs are indexed.

For illustration only, the situation could theoretically be:

Status	URLs
Sitemap discovered	1,894
Indexed	1,600
Not indexed	294

Or it might be:

Status	URLs
Sitemap discovered	1,894
Indexed	1,850
Not indexed	44

The actual indexed number must be obtained from the relevant Search Console indexing reports rather than inferred from the sitemap's discovered-page count.

8. How to Check the Actual Number of Indexed Pages

Open Google Search Console and select the correct property.

Navigate to:

Indexing → Pages

Look for the Page indexing report.

Depending on the current Search Console interface, you should see information separating pages that are indexed from pages that are not indexed.

This is much more useful for determining your actual indexing situation than the sitemap's Discovered pages figure.

9. How to Calculate Your Approximate Indexing Percentage

If you know:

• Sitemap URLs = 1,894
• Indexed URLs = 1,700

you can calculate:

Indexing percentage = Indexed URLs ÷ Sitemap URLs × 100

Therefore:

1,700 ÷ 1,894 × 100 ≈ 89.76%

This can be useful as an operational metric.

However, do not treat 100% as an automatic requirement.

Some sitemap URLs may have changed recently, and Search Console datasets can also update at different times.

More importantly, your sitemap itself should normally contain only canonical, indexable URLs that you genuinely want Google to index.

10. Why Might Sitemap Pages Not Be Indexed?

There are many possible reasons.

Common examples include:

Discovered – currently not indexed

Google knows the URL exists but has not yet crawled or indexed it.

Crawled – currently not indexed

Google has crawled the page but has not currently included it in the index.

Duplicate content

Google may consider another URL to be the preferred canonical version.

Alternate page with proper canonical tag

The URL may intentionally point to another canonical URL.

Excluded by noindex

The HTML may contain:

<meta name="robots" content="noindex">

This tells compliant search engines not to index the page.

Redirect

The URL may redirect elsewhere.

For example:

old-page.php → new-page.php

The old redirecting URL normally should not be expected to appear as a separately indexed content page.

Not found

The server may return:

404 Not Found

Gone

A deliberately removed URL may return:

410 Gone

Server problems

Google may encounter:

500 Internal Server Error

502 Bad Gateway

503 Service Unavailable

or other server-side failures.

11. Is “Discovered – Currently Not Indexed” Always a Problem?

No.

A small number of such URLs can occur naturally.

Google may discover URLs before crawling them.

This is particularly common when:

• many pages are added quickly,
• the site is relatively new,
• internal linking is weak,
• content is very similar across many pages,
• Google has not prioritized crawling those URLs yet.

If a large percentage of your important articles remain in this state for a long period, further investigation is appropriate.

12. What Does “Crawled – Currently Not Indexed” Mean?

This deserves special attention.

It generally indicates that Google visited the URL but the page is not currently indexed.

Possible contributing factors can include:

• insufficiently useful content,
• duplication,
• near-duplicate articles,
• weak differentiation,
• canonicalization,
• temporary indexing decisions,
• other quality or technical signals.

Do not automatically assume it is a penalty.

Instead, inspect representative affected URLs.

13. Why a Large Knowledgebase Needs Strong Content Quality

A technical knowledgebase may contain hundreds or thousands of articles.

Simply generating more URLs does not guarantee better SEO performance.

Google needs useful pages that satisfy distinct user needs.

For a technical knowledgebase, good articles should ideally provide substantial value through elements such as:

• clear problem definition,
• symptoms,
• causes,
• diagnostic steps,
• commands,
• configuration examples,
• screenshots where useful,
• solutions,
• warnings,
• alternatives,
• FAQs,
• related articles,
• accurate titles,
• descriptive headings,
• meaningful internal links.

Two articles covering effectively the same question with only minor wording changes may compete with or duplicate one another.

14. Sitemap Count vs Website Article Count

Another common question is:

“My database has 1,873 articles, but Search Console says the sitemap has 1,894 discovered pages. Is that wrong?”

Not necessarily.

A sitemap can contain more than just article pages.

For example, it may contain:

• homepage
• category pages
• static pages
• article pages
• support pages
• other canonical content pages

Therefore:

Number of articles ≠ Number of sitemap URLs

This is perfectly normal if the additional URLs are intentional, canonical and indexable.

15. Audit What Your Sitemap Actually Contains

Website administrators should periodically open:

https://example.com/sitemap.xml

and inspect the URLs.

Ask:

Does every URL in this sitemap deserve to appear in Google Search?

Ideally, sitemap entries should generally be:

• valid,
• canonical,
• indexable,
• accessible,
• returning an appropriate successful response,
• useful search landing pages.

Avoid filling the sitemap with unnecessary URLs such as:

• admin pages,
• login pages,
• internal search-result URLs,
• tracking URLs,
• duplicate parameters,
• broken URLs,
• redirected URLs,
• deliberately noindex pages.

16. Why “Last Read” Is Important

The sitemap report includes a Last read field.

This indicates when Google last retrieved/processed the sitemap.

A recent date is generally a useful sign that Google is continuing to access it.

However, do not interpret a recent Last read date as:

“Google recrawled every page on that date.”

Google reading the sitemap and Google crawling every URL listed inside it are different activities.

17. Do You Need to Resubmit the Sitemap Every Time You Publish an Article?

Usually, no.

If the sitemap URL remains the same and the sitemap dynamically updates when new content is published, Google can periodically revisit it.

For example:

https://example.com/sitemap.xml

may automatically contain newly published article URLs.

You normally don't need to remove and resubmit the sitemap every time you add an article.

18. Should You Delete and Resubmit a Successful Sitemap?

Usually not.

If Search Console shows:

Status: Success

there is generally no reason to repeatedly delete and resubmit it simply because some pages have not yet been indexed.

Instead, investigate the indexing status of the affected URLs.

Repeated sitemap submission does not force Google to index pages.

19. Use URL Inspection for Individual Pages

For an important article, use:

Google Search Console → URL Inspection

Enter the full URL.

Google may provide information about whether the URL is indexed and the canonical/indexing information associated with it.

This is particularly useful when a specific page isn't appearing in Google.

20. What Is “Test Live URL”?

URL Inspection can also provide a Test Live URL function.

This performs a live check against the current version of the page.

It is useful after changes such as:

• removing a noindex directive,
• correcting robots rules,
• repairing a server error,
• fixing page availability,
• modifying canonical configuration,
• repairing important page resources.

However, a successful live test still does not guarantee that Google will index the page.

It primarily helps verify whether Google can currently access/process the page and whether certain live-test conditions are satisfied.

21. When Should “Request Indexing” Be Used?

Request Indexing can be useful for individual important URLs after:

• publishing important new content,
• significantly updating an existing page,
• removing accidental noindex,
• repairing technical problems,
• restoring a previously unavailable page.

It should not be considered a substitute for good:

• sitemap configuration,
• internal linking,
• crawlability,
• content quality,
• canonicalization.

22. Internal Linking Is Critical

An XML sitemap should not be the only way Google discovers your articles.

Important pages should also be reachable through normal HTML links.

For example:

Homepage → Category → Article

or:

Article A → Related Article B

Good internal linking helps users and search engines understand the structure and relationships between your content.

For a large knowledgebase, consider:

• category navigation,
• related articles,
• breadcrumbs,
• topic hubs,
• popular articles,
• recently updated articles,
• contextual links within articles.

23. Check HTTP Status Codes

Important sitemap URLs intended for indexing should normally return:

HTTP 200 OK

Administrators can check using:

curl -I "https://example.com/article.php?id=123"

A healthy response may begin:

HTTP/1.1 200 OK
Content-Type: text/html

If the URL instead returns 404, 410, 500 or an unintended redirect, investigate why it remains in the sitemap.

24. Check Canonical Tags

An article may contain:

<link rel="canonical" href="https://example.com/article.php?id=123">

The canonical should accurately represent the preferred URL for that content.

Incorrect canonical configuration can cause unexpected indexing behavior.

For example, if hundreds of articles accidentally specify the homepage as canonical, Google may not treat those article URLs as independent canonical pages.

25. Check Robots Meta Directives

For pages intended for indexing, verify that they do not accidentally contain:

<meta name="robots" content="noindex">

A normal indexable configuration might use:

<meta name="robots" content="index, follow">

Note that explicitly specifying index, follow is generally unnecessary because indexing/following are default behaviors when no conflicting directive exists.

26. Check robots.txt

A typical robots.txt might contain:

User-agent: *
Allow: /

Sitemap: https://example.com/sitemap.xml

But robots.txt should be configured according to the actual structure and security requirements of the website.

Be careful not to accidentally block important content directories.

27. Remove Dead URLs from Dynamic Sitemaps

If an article has been permanently deleted and intentionally returns:

410 Gone

it generally should also be removed from the active sitemap.

Otherwise you are effectively telling Google:

“Please discover this URL.”

while your server simultaneously says:

“This resource is permanently gone.”

Keeping sitemaps clean reduces conflicting signals.

28. Do Not Put Redirected URLs in the Sitemap

Suppose:

article-old.php → article-new.php

The sitemap should normally contain the final canonical destination:

article-new.php

rather than the obsolete redirecting URL.

29. Sitemap Quality Checklist

Periodically verify that sitemap URLs:

• return the intended response,
• are not broken,
• are not unnecessary redirects,
• are not noindex,
• are not blocked from crawling unintentionally,
• use correct canonical URLs,
• contain useful content,
• are internally linked,
• are intended to appear in search.

A sitemap should represent the website's preferred indexable URL set.

30. A Practical Google Search Console Monitoring Routine

For an actively maintained website, a useful workflow is:

Step 1 – Check Sitemaps

Go to:

Indexing → Sitemaps

Check:

• Success/error status
• Last read
• Discovered pages

Step 2 – Check Page Indexing

Go to:

Indexing → Pages

Review:

• indexed URLs,
• not-indexed URLs,
• major exclusion reasons.

Step 3 – Investigate Large Exclusion Groups

Pay particular attention to important content appearing under statuses such as:

• Crawled – currently not indexed
• Discovered – currently not indexed
• Duplicate
• Not found
• Server error
• Blocked
• Excluded by noindex

Step 4 – Inspect Representative URLs

Don't immediately try to fix thousands of URLs.

Select a few examples from each major category and determine the common cause.

Step 5 – Correct the Root Cause

Examples:

• accidental noindex → remove it,
• obsolete URL → remove from sitemap,
• duplicate content → consolidate appropriately,
• incorrect canonical → correct canonical,
• server errors → repair server/application,
• thin article → substantially improve usefulness where appropriate.

Step 6 – Recheck Later

Search Console reports are not necessarily real-time.

Allow Google's systems time to recrawl and update their reporting.

31. Is a Sitemap with “Success” a Good Sign?

Yes.

A successful sitemap is an important foundation.

It means Google can process the sitemap.

But sitemap success answers:

“Can Google process my sitemap?”

It does not answer:

“Did Google index every URL?”

Those are different questions.

32. The Four Numbers Website Owners Should Monitor

For a content-heavy website, it is useful to monitor four separate figures:

1. Total published content

How many legitimate pages/articles exist?

2. Sitemap URLs

How many preferred URLs are declared to Google?

3. Indexed pages

How many pages are currently indexed?

4. Search performance

How many pages actually receive:

• impressions,
• clicks,
• useful search visibility?

The ultimate objective is not simply:

More indexed pages

It is:

More high-quality pages indexed and receiving relevant search traffic.

33. Discovered Does Not Mean Ranking

Even an indexed URL may receive no search traffic.

The progression can be understood as:

Discovered → Crawled → Indexed → Eligible → Ranked → Impression → Click

A page can therefore be:

• discovered but not indexed,
• indexed but rarely shown,
• shown but rarely clicked,
• highly ranked and frequently clicked.

SEO requires analysis beyond the sitemap.

34. Why This Distinction Matters for Large Websites

Suppose a publisher sees:

Discovered pages: 1,894

and assumes all pages are indexed.

They may overlook a situation where hundreds of important articles are excluded.

Conversely, someone might see hundreds of “Not indexed” URLs and assume there is a serious problem even though many are intentional redirects, duplicates or obsolete URLs.

Correct interpretation prevents unnecessary changes.

35. Recommended Technical Workflow

For administrators managing hundreds or thousands of pages:

Website database

↓

Generate canonical indexable URLs

↓

Generate XML sitemap

↓

Submit sitemap to Search Console

↓

Google discovers URLs

↓

Google crawls URLs

↓

Google evaluates canonical/indexing signals

↓

Page indexing report

↓

URL Inspection for exceptions

↓

Search Performance report

This gives a much more complete picture of SEO health.

Frequently Asked Questions (FAQ)

1. Does “Discovered pages: 1,894” mean Google indexed 1,894 pages?

No. It means Google discovered approximately 1,894 page URLs through that sitemap. It does not directly confirm that all 1,894 URLs are indexed.

2. Where can I see how many pages Google has indexed?

Use the Page indexing report under Google Search Console → Indexing → Pages.

3. What does Sitemap Status “Success” mean?

It means Google was able to retrieve and process the sitemap successfully. It does not guarantee indexing of every URL.

4. Is sitemap submission enough for indexing?

No. Sitemap submission helps discovery. Google still decides whether and when individual URLs are crawled and indexed.

5. Can Google discover pages that aren't in my sitemap?

Yes. Google can discover URLs through internal links, external links and other mechanisms.

6. Can Google index a page that isn't listed in my sitemap?

Yes. A sitemap is not the only discovery mechanism.

7. Should every published article be in the sitemap?

Generally, canonical public articles that you want Google to index should be included.

8. Should noindex pages appear in the sitemap?

Normally, no. If you intentionally don't want a page indexed, including it in a sitemap intended for indexable URLs sends inconsistent signals.

9. Should 404 pages remain in the sitemap?

No. Broken/deleted URLs should generally be removed from the active sitemap.

10. Should 410 Gone URLs remain in the sitemap?

Normally no. Once a URL has intentionally been removed, the sitemap should generally stop advertising it as a URL intended for indexing.

11. Should redirected URLs appear in the sitemap?

Normally the sitemap should contain the final preferred canonical URL rather than obsolete redirecting URLs.

12. What does “Last read” mean?

It indicates when Google last retrieved/processed the sitemap. It does not mean Google crawled every URL on that date.

13. Do I need to resubmit my sitemap whenever I publish an article?

Normally not if your existing sitemap automatically updates and remains accessible.

14. Will resubmitting a sitemap force indexing?

No.

15. What is “Discovered – currently not indexed”?

Google knows the URL exists but it is not currently indexed, and it may not yet have been crawled.

16. What is “Crawled – currently not indexed”?

Google crawled the page but it is not currently included in the index.

17. Does “Crawled – currently not indexed” mean my site has a penalty?

Not necessarily. There can be many technical, canonicalization and quality-related reasons.

18. Does HTTP 200 guarantee indexing?

No. HTTP 200 only indicates that the server successfully returned a response. Google still makes a separate indexing decision.

19. Can duplicate content affect indexing?

Yes. Google may select one URL as canonical and not index other substantially duplicate versions independently.

20. Can an incorrect canonical tag cause indexing problems?

Yes. Incorrect canonicalization can cause Google to prefer a different URL.

21. Can noindex prevent indexing?

Yes. A valid noindex directive tells search engines not to index the page.

22. Can robots.txt affect crawling?

Yes. robots.txt can prevent Googlebot from crawling URLs covered by disallow rules.

23. What is URL Inspection?

URL Inspection is a Search Console tool for examining Google's information about a particular URL.

24. What is Test Live URL?

It performs a live test of the current page and helps identify whether Google can currently access/process it under the conditions evaluated by the test.

25. Does Test Live URL guarantee indexing?

No.

26. Does Request Indexing guarantee indexing?

No. It requests processing but Google still decides whether the page will be indexed.

27. Should category pages be included in the sitemap?

They can be if they are useful, canonical, indexable pages intended to appear in search.

28. Should internal search pages be indexed?

Usually internal search-result pages are poor sitemap candidates and are often intentionally kept out of search indexes.

29. Why can the sitemap URL count be higher than the article count?

Because the sitemap may also contain the homepage, category pages, static pages and other indexable URLs.

30. Is 100% sitemap indexing necessary?

Not necessarily. The important issue is whether your valuable canonical content is being indexed appropriately and whether your sitemap itself contains only URLs that deserve indexing.

Conclusion

The most important lesson when reading Google Search Console's Sitemaps report is:

“Discovered pages” is not the same as “Indexed pages.”

If Search Console reports:

Sitemap Status: Success
Discovered pages: 1,894

the correct interpretation is:

Google successfully processed the sitemap and discovered approximately 1,894 page URLs from it.

It is incorrect to automatically conclude:

“Google has indexed 1,894 pages.”

To determine actual indexing health, combine:

Sitemaps report + Page indexing report + URL Inspection + Search Performance

For a large knowledgebase, this distinction becomes particularly important because thousands of URLs may exist in different states of discovery, crawling, canonicalization and indexing.

A technically healthy SEO strategy therefore focuses not merely on submitting more URLs, but on ensuring that the sitemap contains canonical, accessible, useful and genuinely index-worthy pages.

#tags

#GoogleSearchConsole #GoogleSearch #GoogleIndexing #GoogleSEO #TechnicalSEO #SearchConsole #Sitemap #XMLSitemap #SitemapXML #GoogleSitemap #IndexedPages #DiscoveredPages #PageIndexing #GoogleBot #GoogleCrawler #WebsiteIndexing #SEO #SEOTips #SEOGuide #SEOAudit #TechnicalSEOAudit #SearchEngineOptimization #WebsiteSEO #IndexCoverage #URLInspection #TestLiveURL #RequestIndexing #Crawlability #Indexability #GoogleCrawling #GoogleIndex #SitemapSEO #SearchConsoleGuide #SearchConsoleTips #GoogleSearchTips #WebsiteOptimization #CanonicalURL #CanonicalTag #RobotsTxt #NoIndex #HTTPStatus #404Error #410Gone #ServerError #CrawlBudget #ContentQuality #InternalLinking #KnowledgeBaseSEO #WebsiteAdministrator #Webmaster