At a glance
Subtract confirmed unique pages from confirmed pages across URLs to measure repeated page processing in that ledger. Multiply the difference by an editable per-page rate to explore a scenario. This assumes one approved source result can serve all identical-file locations; link updates and review may still require work.
1,000 confirmed URL pages minus 750 unique pages leaves 250 repeated pages, or a hypothetical $1,250 of page processing at $5/page.
| Measure | Calculation | Result |
|---|---|---|
| Repeated pages | 1,000 − 750 | 250 |
| Repeated share of URL pages | 250 ÷ 1,000 | 25% |
| Hypothetical processing amount | 250 × $5 | $1,250 |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Use totals from the same ledger
The URL total and unique total must use the same attempt, confirmed files and identity rule. Mixing an older total with a newer revision can create a misleading difference. Unknown files should be excluded from both bases and retained as a limitation.
DocAccessible exact duplicates are byte-identical groups, not visually similar documents. A re-export with changed bytes may remain a separate source. Near-duplicate consolidation requires an owner review before sharing an output across revisions.
- Enter confirmed URL pages, not the number of URLs.
- Enter confirmed unique pages from the same scope.
- The unique total cannot exceed the URL total under this method.
Separate repeated source work from publishing work
Repeated pages = URL pages − unique pages. The share divides that difference by URL pages when the denominator is positive. The hypothetical amount uses your editable rate; the default is only an illustration.
Even when the source is identical, each page or website location may need a corrected link label, mapped alternative or owner confirmation. Those tasks are not included in the page-only amount. No document deletion or savings decision happens in this tool.
Keep the group and every publication location
Use the inventory ledger to choose one source-work item per confirmed identical-file group. Retain all URLs so the approved output can be published deliberately in the right places. Compare task and context before deciding the same alternative is suitable everywhere.
If the source changes at one location, establish its identity again. A previous duplicate group does not guarantee that future downloads stay identical. The worksheet and count-methodology reference make this decision traceable.
- Confirm the attempt and byte-identity basis.
- Compare both confirmed page totals.
- Use a relevant illustrative rate.
- Review per-location publication work separately.
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.
- Python hashlib documentation
SHA-256 hashing of file bytes.
- DocAccessible PDF inventory
The counting workflow, report options and purchase boundary.
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.