This is what a complete results report would look like when each of the fields controlling the output is specified and PDF Checker completes the review successfully.
Note the section at the top of the results output, the CHECKER_SUMMARY.
This is a summary list of the items that PDF Checker found when reviewing a PDF document, intended to be machine readable. But you might prefer to use the JSON output format instead.
You could set up a batch process to review a set of PDF documents stored in a server directory automatically, one by one. Then, you could add a step to your batch code that would identify the PDF documents that PDF Checker found with issues or problems, create an input JSON file listing those issues or problems, and send that JSON file list to PDF Optimizer. PDF Optimizer could then optimize each PDF document based on the items found by PDF Checker. Note that for documents that PDF Optimizer can improve, a statement appears, “canBeOptimized,” to make it easy detect documents that are candidates for optimization. The software also provides the size of the PDF source document, and a machine readable value, “sizeInBytes.” This allows you to scan the results to make decisions on document processing based on file size. For example, a PDF document that is only 10 KB probably isn’t worth optimizing.
Note that the metadata for the PDF document is provided at the top of the report. The “Trapped” parameter refers to the prepress workflow when printing in color. Trapping a document governs how the ink will appear on the page; colors are trapped by adjusting the shape of objects as they are printed on the page to avoid gaps from appearing. Trapping can be enabled by some software products that generate PDF documents, such as Adobe InDesign.
PDF Checker will determine if the PDF document claims PDF/A compliance, and provide the type of PDF/A file. If in fact the file is not PDF/A compliant, an error message will appear in the output report.