Inspect a workshop PDF’s schedule, contact and appendix links
Admin ·
A workshop prospectus points readers to a web schedule, an email address and an appendix inside the same PDF. Compare the three recorded actions without opening their destinations.
Compare the three targets on physical page 1
Select Load example. The two-page prospectus has three link annotations on the first page. The schedule target is https://workshop.test/schedule, and the contact is mailto:desk@workshop.test.
The third row uses a local destination. It points to physical page 2 and uses the Fit viewing mode. The appendix page has no further link annotations.
https://workshop.test/schedule
mailto:desk@workshop.test
Page 2 · FitCheck the kind and any note before interpreting a target
In a saved PDF, compare HTTP links with HTTPS links using the Type column. HTTP records are flagged as unencrypted. Other URI schemes and relative addresses appear as stored.
A local link can refer to a named destination in the PDF. If the name or page cannot be resolved, its row says Unavailable. Unsupported actions are listed by type, with their executable data left out.
Compare the CSV and JSON exports
Save JSON to preserve structured fields, including the physical source page, annotation position, target and local destination page. The report contains the original stored URI text.
Save CSV to compare the same findings in a spreadsheet. The Target is quoted and values that could be interpreted as formulas are protected in this export.
Common questions
Does a URL printed on a document automatically appear in the report?
The workspace reads saved PDF Link annotations. A reader may detect printed URL text separately.
Do page numbers follow the printed labels?
The source and destination columns use physical PDF pages, starting at one. A printed label such as Appendix A can appear on physical page 2.