At a glance
Counted divided by discovered PDF URLs gives counting completion for a known ledger. Discovered minus counted gives uncounted URLs, not missing pages. No whole-website coverage percentage can be established from these figures because undiscovered documents are not in the denominator.
80 counted out of 100 discovered URLs is 80% ledger counting completion. It says nothing numerical about unseen website PDFs.
| Measure | Calculation | Result |
|---|---|---|
| Counting completion | 80 ÷ 100 | 80% of discovered URLs |
| Uncounted URLs | 100 − 80 | 20 |
| Whole-site discovery coverage | Unknown denominator | Not established |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Keep the denominator in the label
Use discovered PDF URL rows and counted PDF URL rows from the same report. Duplicate URLs still belong in this completion denominator because each recorded location has its own retrieval result. Unique-file counts answer a different question.
When there are no discovered URLs, the completion percentage is not available. That is not 100% success or proof that the website has no PDFs. Discovery may not have started, may be blocked or may have found no files in its recorded scope.
- Counted URLs cannot exceed discovered URLs.
- Unknown counts stay unresolved even if confirmed pages are useful.
- A reported web request is not one discovered PDF.
Do not manufacture a website coverage score
Failed requests, rule skips, unreachable portals and allowance stops can leave website discovery incomplete. The number of unseen PDFs behind those gaps is unknown. Adding request counts to the PDF denominator mixes different units.
The formula here is completion = counted / discovered × 100, with a positive denominator. It reports a percentage to one decimal place while retaining the exact URL counts. A 100% result means all recorded candidates were counted, not that every organization document was found.
Present the result with a scope sentence
Write the host, attempt date, discovery sources and crawl outcome beside the result. For example: all 80 discovered PDFs counted; discovery remained incomplete because recorded website requests failed. Use the request list for follow-up when it exists.
If you need a broader completeness check, reconcile public discovery with owner-held CMS records and known essential download URLs. Describe excluded or private scope separately. A useful report is explicit about what its denominator can and cannot represent.
- Use same-attempt PDF URL counts.
- Review uncounted reasons separately.
- Read crawl scope and end reason.
- Report completion together with coverage limitations.
Sources and scope
Methods, worksheets and illustrative examples are DocAccessible editorial contributions. These references support the technical or product details described above. W3C techniques are informative guidance; they are not a certification scheme.
- DocAccessible PDF inventory
The counting workflow, report options and purchase boundary.
- Sitemaps protocol
URL and sitemap-index formats used in public discovery.
Written by the DocAccessible team under our editorial policy. Suggest a correction if a source or product detail needs updating.
See the evidence in a working example
Explore the public sample inventory report to try its table, full-screen view and missing-count reasons. The downloadable counting fixture check records what the local counter returned for seven self-authored inputs, with hashes and explicit limits.