A Sitemap Discovers 1,420 URLs: How Many of the Articles Are Actually Indexed?

A sitemap report in Search Console discovering 1,420 URLs does not mean 1,420 articles have been indexed, nor does it prove that every article in a particular batch is indexed. First distinguish sitemap URLs, individual articles, language versions, and actual indexing states. Then build a list for the target batch to establish how far its articles have been processed.

On October 5, 2026, JVDS Design Studio checked that the actual sitemap of its own website had been synchronized from 571 addresses to 1,420 unique URLs. In a screenshot subsequently supplied by the user, the non-www sitemap showed a successful status and 1,420 discovered URLs. This is evidence of sitemap synchronization and reading, rather than a client growth case or proof that indexing of the entire site is complete.

First Establish What the Number Counts

A sitemap may include articles, products, case studies, listing pages, and language-specific URLs, and may comprise multiple files. A Chinese article and its English version use different URLs, so the address count may naturally exceed the number of individual articles. First establish whether the count covers a single sitemap, the entire sitemap set, or a deduplicated collection. Totals with the same label do not necessarily use the same definition.

Candidate counts in the CMS, the number of URLs in XML actually returned by the server, and platform discovery counts also belong to different stages. The CMS may be updated while the static file remains old; the file may have been generated while the platform has yet to read it again. Checking each stage is more accurate than using one total to explain every state.

A historical check on October 2, 2026 verified the responses of 571 sitemap URLs but did not obtain complete live indexing evidence at that time. That old number describes only the scope of that check. It cannot be compared directly with the later 1,420 to calculate an increase in newly indexed pages. Keep the counting definition and check date alongside the figure.

Map Articles to Their Language-Specific URLs

To check a batch of articles, first collect each article’s identity, title, live Chinese URL, other language URLs that are actually published, and publication date. Drafts that exist only in the CMS do not belong on a list of publicly available pages awaiting indexing. An unfinished language version must not be recorded as published using an anticipated URL.

Check whether these exact addresses appear in the actual sitemap, whether they are duplicated, and whether they use the agreed host, protocol, and path. Do not search by title alone, because content with the same title may have different versions. Finding the Chinese version does not establish that the English version is also in the sitemap.

Also open representative pages to check their body content, language, accessibility, and canonical settings. A normal HTTP response establishes that this request received a result; it does not automatically prove that the body is complete or the page indexed. Record article identity, sitemap registration, actual access, and platform processing separately.

At this stage, you should have a URL list with a clear scope: pages that are public and in the sitemap, pages lacking entry points, language versions not yet published, and pages with anomalies. This is not an indexing conclusion, but it supplies definite objects for subsequent checks.

After a Successful Read, Check Indexing Instead of Reusing Discovery Counts

Confirm the selected Search Console property and exact sitemap address, then record the report status, last read time, and discovery count. A successful platform status means that sitemap processing reached the corresponding state. It does not guarantee that every URL has been crawled, indexed, or shown in search.

Open the page indexing information for the relevant sitemap, review indexed and non-indexed categories and reasons, and check them against the target article list. An overall report is useful for scope and trends but may not list every detail. Its example URLs alone cannot establish a precise indexing rate for a batch of articles.

Use URL Inspection for each important article. The default report reflects the version Google previously processed, so record the crawl time and selected canonical URL. “Test live URL” checks the current page’s accessibility and technical conditions; it is not proof that the page is indexed now. For further investigation, see checks for a page that Google has not indexed.

If the current page now works while the historical report remains unchanged, distinguish the times represented by the evidence before scheduling further observation. If report access is unavailable or a URL has not been checked, explicitly record that evidence has not been obtained. Do not fill the gap with an “indexed” status inferred from sitewide discovery counts.

Keep Supporting Searches and Tools Within Their Own Scope

A site query can help observe results from a particular search, but it is not a complete index inventory. Third-party tools may also have different collection scopes and update times. A field labelled “indexed pages” does not necessarily match the platform’s indexing definition.

When figures differ, record the tool, query conditions, site version, time, and traceable pages. Select important URLs for further verification before immediately requesting a hosting change, an IP change, or bulk content deletion. Explaining where the difference comes from is more useful than choosing a larger number for the report.

Indexing also differs from impressions, clicks, and inquiries. Whether an indexed page appears for a particular query requires search performance records. Whether those impressions produce usable demand requires behavioral and business evidence. The differences between crawling, indexing, and ranking can help the team place a problem at the correct stage.

Use Batch Records to Decide the Next Step

Record each article’s live URL, language, publication status, sitemap check time, current access result, indexing evidence and date, anomaly reason, and next check. One article may have multiple language-specific URLs. Record each URL first, then aggregate as needed, avoiding the addition of URL counts to article counts.

State conclusions separately: registered in the sitemap; accessibility verified; reported as indexed by the platform; a non-indexing reason exists; or evidence not yet obtained. Where only part of a batch can be checked, identify the sample and unchecked scope. A passing sample does not establish that the entire batch passed.

The next step depends on the problem. For missing sitemap URLs, check publication and generation first. For access anomalies, check the page. If a report identifies a restriction, inspect the relevant settings. If a page is accessible but not indexed, continue checking discovery entry points and content. A sitemap entry cannot substitute for an article answering a distinct reader question.

Periodic reports must also retain the same scope. When adding languages, adjusting sitemaps, or changing deduplication, explain the definition change before assessing trends. More URLs do not mean that search has already recognized their value, and fewer URLs alone do not establish an operational decline.

The completion criterion is that the responsible person can point to specific URLs in the target batch and explain what current evidence supports, what remains unknown, and who will check it. Without such a list, 1,420 is merely a number in a sitemap report.

Frequently Asked Questions

Does counting both Chinese and English URLs count the same item twice?

If counting URLs, they are two addresses. If counting individual articles, define a separate grouping rule. State what you are counting before deciding whether duplication exists.

If all sitemap URLs are accessible, can we declare SEO acceptance complete?

That establishes only the scope of the corresponding technical checks. Indexing, ranking, and business outcomes still need their own evidence; access results cannot substitute for it.

Do search results for a few articles prove that the whole batch is indexed?

No. They support only the observation of those URLs in that particular query. Other pages still require checking, and a sitewide total cannot fill in the status of the entire batch.