LEYUN · SITE SPEC & COMPONENT LIBRARY独立站技术规范手册

PDF Metadata Rules: Title, Author, Subject and Keywords

Section:PDF PAGE SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「PDF Metadata Rules: Title, Author, Subject and Keywords」 in PDF PAGE SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Sites that want PDF content to be indexed by search engines
  • Documents with real search value, such as selection guides and application manuals
  • Sites that want AI retrieval to cite content inside PDFs
  • Template sites that generate documents in bulk and need one consistent convention
Template / code snippethtml
<!-- PDF 生成时的元信息设置 -->
<!-- 命令行示例(以常见工具链为例) -->
<!--
qpdf --linearize \
      --update-from-data="" \
      --object-streams=generate \
      input.pdf output.pdf

exiftool -overwrite_original \
  -Title="${modelCode} Datasheet" \
  -Author="${companyName}" \
  -Subject="Technical specifications for ${modelCode}" \
  -Keywords="${keywords}" \
  -Creator="${companyName} Technical Department" \
  -Producer="${companyName}" \
  -CreationDate="${isoDate}" \
  -ModDate="${isoDate}" \
  -PDFVersion="1.7" \
  input.pdf
-->

<!-- 页面上的对应声明(与 PDF 元信息保持一致) -->
<section class="pdf-meta">
  <h2>About this document</h2>
  <dl>
    <div><dt>Title</dt><dd>${modelCode} Datasheet</dd></div>
    <div><dt>Author</dt><dd>${companyName}</dd></div>
    <div><dt>Subject</dt>
      <dd>Technical specifications, dimensions and applicable
          standards for ${modelCode}</dd></div>
    <div><dt>Language</dt><dd>${languageName}</dd></div>
    <div><dt>Revision</dt><dd>${revision} (${updateDate})</dd></div>
  </dl>
</section>
Fields and parameters
Field / parameterTypeDescription and values
TitleTextModel code plus document type, no marketing wording
AuthorTextCompany name or technical department
SubjectTextObjective description of the content scope
KeywordsTextModel code, key parameters, applicable industries
Creator / ProducerTextIdentifies the producing tool or organisation
CreationDate / ModDateDateISO 8601 format
PDF versionEnum1.7 offers good compatibility
Document languageTextMatches the language of the content

SEO and structured-data notes

SEO and structured-data checkpoints
No marketing wording in the TitleTitles such as "Best Quality Datasheet" carry no discriminative value in retrieval
Use the company name as AuthorIndividual names hinder consistent management of corporate documents and make search result presentation uneven
Subject describes the scopeSubject is supporting information for judging whether a document applies
Keywords should be searchable termsModel code + parameters + industry, consistent with the keyword approach used on the page
Dates in ISO formatNon-standard date formats parse inconsistently across tools
State the same information on the pageA second declaration outside the PDF metadata covers differences between crawling tools

Compliance risk notes

  • Metadata must not contain false information
  • Unauthorised brand or customer information must not be embedded in metadata
  • Author must not use a fictitious individual name
  • Dates must reflect when the document was actually produced
  • Keywords must not be stuffed with unrelated terms

Do not reuse this template verbatim in regulated contexts; verify local regulations and platform rules before going live.

Modification example

<!-- Modification example: keep metadata and the page declaration consistent -->
<!-- Target PDF metadata -->
Title    : MODEL-A Datasheet
Author   : ${companyName}
Subject  : Technical specifications, dimensions and applicable
           standards for MODEL-A
Keywords : MODEL-A datasheet, hydraulic press specifications,
           working stroke, rated pressure, ${applicableStandards}
Creator  : ${companyName} Technical Department
Producer : ${companyName}
ModDate  : 2026-05-12

<!-- State the same information on the page -->
<section class="pdf-meta">
  <h2>About this document</h2>
  <dl>
    <div><dt>Title</dt><dd>MODEL-A Datasheet</dd></div>
    <div><dt>Author</dt><dd>${companyName}</dd></div>
    <div><dt>Subject</dt>
      <dd>Technical specifications, dimensions and applicable
          standards for MODEL-A</dd></div>
    <div><dt>Language</dt><dd>English</dd></div>
    <div><dt>Revision</dt><dd>3 (2026-05-12)</dd></div>
  </dl>
</section>

<!-- What consistency buys:
     1. the embedded PDF metadata is read by file-level retrieval tools
     2. the page declaration is read by web retrieval tools
     3. when the two agree, there is no case of
        "the file says one thing and the page says another",
        a detail that raises doubt during procurement due diligence -->

FAQ

Does PDF metadata affect ranking?
The effect is limited, but it affects being found and being cited. A PDF is an independent retrievable asset, and complete metadata means it can be classified correctly.
Which fields matter most?
Title and Subject. Author and Keywords play a supporting role.
Is metadata useful on scanned files?
You can still set it, but the body text of a scan is not searchable, so the overall indexing value stays limited.
How is consistency maintained in bulk generation?
Inject the values through template variables; do not fill them in by hand one file at a time.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.

Note: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.