A PDF download has no HTML head in which to place a canonical link element. If it duplicates a preferred HTML guide, declare the PDF’s canonical through its HTTP response instead. First compare the content, then check the response that actually delivers the file.
Confirm that the PDF and HTML represent the same guide
For this fictional field-notes guide, the owner wants the HTML edition to represent two substantially equivalent versions.
| Resource | Example URL | Content to compare |
|---|---|---|
| Preferred HTML guide | https://example.com/field-notes/ |
Observation steps and recording table |
| Printable PDF | https://example.com/downloads/field-notes.pdf |
The same steps and table in a print layout |
Open both versions and compare their main instructions. If the PDF is a different report or contains important material missing from the HTML page, revisit the proposed relationship. A shared title alone cannot establish equivalent content.
Distinguish the HTML line from a PDF response header
Open the Meta Tag Generator. Enter Field Notes Guide in Page title and https://example.com/field-notes/ in Canonical URL. Leave the optional social-tags checkbox off, select Generate Meta Tags, and find this line:
<link rel="canonical" href="https://example.com/field-notes/">
That is HTML output for a page head. The current tool does not produce an HTTP header or attach one to a PDF. Keep the HTML edition’s existing canonical provider consistent with the intended HTML address.
Google supports a canonical Link response header for non-HTML documents such as PDFs, for web search results. See its HTTP canonical guidance.
Configure the header on the PDF response
The following is a manually prepared response excerpt for the example PDF. It is not generator output.
HTTP/1.1 200 OK
Content-Type: application/pdf
Link: <https://example.com/field-notes/>; rel="canonical"
The target URL goes inside angle brackets; rel="canonical" follows a semicolon. This is HTTP header syntax, as described in the MDN Link header reference and RFC 8288.
Use the server, application or storage configuration that serves this particular PDF. Scope the rule to the intended file or reviewed document mapping. Preserve unrelated headers, and check that another layer does not add a conflicting canonical target.
Adding the HTML line to the PDF’s visible text or to an HTML download wrapper does not establish this response header. Likewise, an HTML page setting may not affect a file delivered directly by storage or a CDN.
Verify a fresh PDF request and its target
- Open browser developer tools and request the PDF directly. In Network, select the request delivering the actual document, rather than an HTML viewer or download page.
- Record the requested address and any redirect destination. Inspect the final file response for its status,
Content-TypeandLinkvalue. - Confirm that the response carries your intended canonical target. Download and open the PDF to check that delivery still works.
- Open the target HTML guide directly and confirm that it contains the expected instructions and table.
- Check another PDF affected by the same configuration, so an overbroad rule does not silently assign it the field-notes target.
Keep the response evidence with the content comparison. A declared canonical is a preference, so it does not guarantee Google’s selection or redirect someone downloading the PDF. For an ordinary duplicate HTML URL with campaign parameters, follow the separate tracking-parameter canonical workflow.