reindexaA percentage can look precise while answering the wrong question. If a tool follows URLs from an exclusion report, its results do not automatically represent the entire website. Before interpreting an indexing ratio, identify which pages enter the calculation and which are left out.
Define the formula and population
Reindexa's content comparison calculates the crawled-but-unindexed share among URLs with valid recent inspections classified as indexed or still crawled but unindexed. The formula is crawled-but-unindexed URLs divided by indexed plus crawled-but-unindexed URLs, multiplied by one hundred.
Pending URLs and other states are excluded from that denominator. Resources and categories excluded from the analysis should not be added back into it. This view uses a seven-day inspection-validity window, so an older observation may stop contributing to the result.
Work through the complete example
Imagine a saved set of 500 URLs. Recent checks show 280 indexed, 120 crawled but unindexed, 40 in other states, and 60 pending or lacking a sufficiently recent observation.
The ratio is 120 divided by 400: 30%. The calculation covers 400 of the 500 saved URLs, or 80%. Report both numbers. “Thirty percent of the whole website is not indexed” would be unsupported: you may not have all website URLs, and the calculation does not include every state.
Keep changing populations visible
If you import 300 URLs tomorrow, a percentage change may reflect the new mix rather than status transitions. When inspections age out of the validity window, the denominator can also change without any page changing its actual status.
For trend analysis, retain a fixed URL cohort and a stable definition. When expanding the set, record the addition date and separate new arrivals from the existing cohort during comparisons.
Avoid universal alarm thresholds
A useful threshold depends on which content should be indexed and how much of it has been inspected. Filter variations and twenty core service pages should not be judged using the same blanket rule. Set priorities around purpose and business impact instead.
Google's Search Console guidance distinguishes exclusion reasons. A custom summary should preserve that underlying distinction. Use the ratio to identify groups worth reviewing, not as an absolute quality score.
Every report should state the formula, saved-set size, coverage and observation date. Then compare blog content with other pages using identical rules.