At a glance
A partial report can have complete counts for every discovered PDF while website discovery remains incomplete. It can also contain discovered files whose counts are unknown. Read the document-count outcome and the website-coverage outcome separately; one cannot repair the other.
Each row needs a different explanation and follow-up.
| Discovered file counts | Website discovery | Meaning |
|---|---|---|
| All counted | Recorded scope finished | Completed within that recorded scope |
| All counted | Some requests failed | Counts complete; coverage incomplete |
| Some unknown | Recorded scope finished | Discovery finished; file counts unresolved |
| Some unknown | Attempt interrupted | Both outcomes need follow-up |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Check the discovered-document ledger
Start with the counted and uncounted file totals. If every discovered PDF has a verified count, the report can say All discovered PDFs counted. That is a concrete outcome for a known list of sources, including byte-identical duplicate groups.
If any count remains unknown, open its reason. A transfer limit, missing file, password or parser uncertainty is not zero pages. Keep these rows in the follow-up queue even when the confirmed page total is already useful.
- Compare discovered, counted and uncounted file figures.
- Inspect any uncounted-file explanations.
- Choose the unique or URL-based total for your purpose.
Check why discovery ended
Now read the website scope and crawl end reason. A page that was refused, timed out or skipped by rules might have contained further PDF links. The crawler cannot determine how many documents were behind that gap.
Limits can also stop discovery before it exhausts reachable links. Repeated attempts may contribute repeated failures, and blocked requests are already included in the failed-request count. Neither measure can be converted into a missing-PDF total.
| Coverage issue | What it establishes | What it does not establish |
|---|---|---|
| Blocked web page | A request was refused | How many PDFs it contains |
| Crawl-rule skip | The address was not fetched | A server refusal |
| Time allowance reached | The attempt stopped at its boundary | The size of unseen scope |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Explain the partial result in one useful sentence
Use a statement such as: All 80 discovered PDFs were counted, totaling 600 confirmed unique pages; website coverage remains incomplete because 12 web requests failed. Add the observation date and exact scope. This preserves useful results without claiming exhaustive discovery.
For newer attempts, use the recorded request list to assign website fixes. Historical aggregate-only reports cannot show the exact failed addresses after the event. Reconcile known important URLs or a CMS export before deciding whether another authorized attempt is worthwhile.
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.
- RFC 9309: Robots Exclusion Protocol
How crawl rules work; robots rules are not access authorization.
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.