At a glance
This log records observed website-request outcomes and owner follow-up. Keep refused, missing, timed-out and rule-skipped addresses distinct, and preserve the attempt context. It does not estimate missing PDFs or reconstruct old request addresses that a scan never retained.
A rule skip has no observed response because the address was not fetched.
| Safe address | HTTP code | Outcome | Action |
|---|---|---|---|
| example.org/downloads | 403 | Refused | Check anonymous policy |
| example.org/archive | None | Rule-skipped | Review crawl rules |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Record an observation, not a guess
Use the report’s actual outcome and timestamp when available. If a current browser test differs, record a new observation instead of replacing the past event. A failed web page might have hidden no PDFs or many; its contents remain unknown until inspected.
Keep request kinds separate. A sitemap failure, PDF-count error and blocked website page have different effects on the final report. Blocked requests can be a subset of failures, so adding both counters can double-count the same events.
- Delete the fictional observations before entering a real log.
- Record safe URLs only; never keep cookies, access tokens or response bodies.
- Keep request kind and attempted versus unfetched states distinct.
- Do not add blocked requests to failures when they are already a subset.
- Retests are new evidence; this sheet cannot reconstruct missing historical addresses.
Use safe addresses and fixed reasons
Remove credentials, fragments and private query values before sharing the sheet. Do not attach cookies, raw response bodies or authorization headers. A public-looking path can still contain a sensitive token.
Use fixed descriptions such as refused, missing, timed out or rule-skipped. Assign the website or document owner a concrete action. Review crawl policy and anonymous access through an authorized process rather than trying to bypass a restriction.
Close issues with new evidence
After a correction, record the new test and relevant source revision. Keep unresolved gaps and omitted-history limits beside any summary. The sheet helps reconcile coverage; it does not turn an incomplete inventory into a complete website audit.
Worksheet fields
The records sheet has 10 columns. Keep a stable ID and source evidence when sorting or extending it.
| Column | How to use it |
|---|---|
| Issue ID | Stable identifier for the observation. |
| Attempt | Scan or investigation attempt number. |
| Safe URL | Address with credentials, fragments and private query values removed. |
| Request kind | Page, PDF, sitemap or robots request. |
| HTTP code | Observed response code; blank when there was no response. |
| Outcome | Refused, missing, timed out, rule-skipped or another observed reason. |
| Observation time | Record a timezone with the timestamp, preferably UTC. |
| Owner | Website or document team responsible for follow-up. |
| Action | Specific permitted investigation or correction. |
| Retest evidence | New observation; retain the original outcome. |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
The original worksheet schemas and fictional rows are offered under CC0. You can adapt them without a required backlink. This reuse statement covers the template assets, not the third-party references.
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.
- RFC 9309: Robots Exclusion Protocol
How crawl rules work; robots rules are not access authorization.
- RFC 9110: HTTP Semantics
HTTP response meanings, including redirects, refusals and missing resources.
- 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.