Noindex PDF Files in 2027 in WordPress
technical seo guideHello my friend. A PDF has no head section for a meta tag, so to noindex PDF files you send an X-Robots-Tag: noindex header with the file instead. Add it on your server for every .pdf, keep the files crawlable, and Google drops them once it revisits.
- use a response header
- keep PDFs crawlable
- test with a header check
GET example.com/wp-content/uploads/price-list.pdf
HTTP/1.1 200 OK
Content-Type: application/pdf
X-Robots-Tag: noindex
// example data. The X-Robots-Tag line is the format shown in Google’s noindex guide. The file path is typical for WordPress uploads.
Why PDFs Need a Different Method
Normal pages carry their noindex rule in a meta tag inside the HTML head. A PDF has no HTML head, so the rule has to travel in the HTTP response header instead.
Google explains both routes. A noindex rule can be set with either a meta tag or an HTTP response header, and it says a response header can be used for non-HTML resources, such as PDFs, video files and image files. The header it names is X-Robots-Tag, with a value of noindex or none.
Say a plumber in Austin uploads a supplier price sheet as a PDF so staff can open it. The link sits in a private email, but the file sits in a public folder. Google can find it anyway, and now customers see wholesale prices in search results.
Why You Might Want to Hide PDFs
PDFs show up in search like any other page. If one is outdated, private, duplicated or thin, you may prefer it stay out.
Common cases are old price lists, internal manuals, copies of web pages saved as PDF, and supplier sheets. My opinion is that a PDF that duplicates a web page can compete with it, which is a reason to hide the PDF. That is experience, not a Google rule.
One warning before anything else. Noindex hides the file from Google only. Google says noindex only hides a page from its results, and that users and other search engines can still reach it. If the file is genuinely confidential, a noindex header is the wrong tool. Use password protection or delete it. Google’s removal guide calls updating or removing the content the most secure way.
How to Noindex PDF Files in 2027 Step by Step
Add one header rule for all PDFs, keep the files crawlable, then test the header and wait for a recrawl. Six steps.
- Find out what your server runs. Many WordPress hosts use Apache, and others use NGINX. Your hosting panel or support team can tell you. The rule differs by server.
- Back up your server config. You are about to edit a file that can take your whole site down if you make a typo. Copy the original first. That is my own safety habit.
- Add the header rule. Google’s robots meta tag guide shows an Apache example that applies the header to .pdf files with
Header set X-Robots-Tag "noindex, nofollow"and says an equivalent NGINX add_header directive exists. Copy the exact snippets from Google’s page. I show my own adapted versions in the box below. - Leave the files crawlable. Google says that if robots.txt blocks crawling, it can’t read the meta tags or headers, and the rules are ignored. Never block the PDFs in robots.txt while relying on the header.
- Test the header. Use a header checker, or your crawler, on one PDF address. You should see X-Robots-Tag: noindex in the response.
- Wait, or ask for a recrawl. Google says it may take months for Googlebot to revisit a page. You can request a recrawl with the URL Inspection tool, and for a faster hide you can use the Removals tool, covered in how to remove a page from Google.
<FilesMatch “[.]pdf$”> Header set X-Robots-Tag “noindex, nofollow” </FilesMatch>
location ~* [.]pdf$ { add_header X-Robots-Tag “noindex, nofollow”; }
// my own adaptation of the pattern in Google’s guide, written without backslashes. I did not test these on your server. Apache needs its headers module enabled, which is my own knowledge, so ask your host.
Which Method Works for PDFs?
Only some of the usual tools can hide a PDF. This table shows which, and why.
| Method | Works for PDFs? | Why |
|---|---|---|
| X-Robots-Tag header | Yes | Google says headers work for non-HTML files such as PDFs |
| Meta robots tag | No | It lives in an HTML head, which a PDF doesn’t have |
| robots.txt block | Not reliably | Google says it won’t read the rules, and the page may still appear |
| Password protection | Yes | Google says it blocks crawlers like Googlebot |
| Delete the file | Yes | Google calls it the most secure way |
// built from Google Search Central’s noindex guide and its “Remove information from Google” page. The meta tag row is my plain-language reading of the same pages.
Common PDF Noindex Mistakes and Fixes
Most failures come from one of these four.
The Usual Slips
- Blocking the PDF folder in robots.txt and expecting noindex to work
- Using a plugin or rule that only affects web pages
- Treating noindex as security for private files
- Never testing the header on a real PDF address
The Better Habit
- Leave PDFs crawlable so Google reads the header
- Add the rule at server level for .pdf files
- Use passwords or delete files that must stay private
- Check the response header on one file first
// the robots.txt and privacy points follow Google’s guidance. The plugin point is my experience.
How to Check the PDFs Are Hidden
Check the header, inspect the URL in Search Console, then search Google for the file after a few weeks.
Run a header check on one PDF and confirm the X-Robots-Tag line. Then use the URL Inspection tool, which Google says you can use to ask for a recrawl. In the Page indexing report, a successful result shows up as “URL marked ‘noindex'”, defined as a page where Google encountered a noindex directive and therefore did not index it. A different status, “Indexed, though blocked by robots.txt”, means your robots.txt is in the way.
Be realistic about timing. Google’s SEO Starter Guide says some changes take effect in a few hours and others take several months. If the PDF links also sit on pages you want fixed, my noindex tag guide covers the HTML side.
What It Costs and How Long It Takes
Adding the rule takes minutes. Choosing the safe method for your server takes a little longer.
My rate is €25 an hour, and as my own estimate a single header rule plus testing is under an hour on most WordPress hosting. Because you are editing server files, I prefer to do it carefully. It falls under my WordPress SEO services. To see what else I do, check my cheap SEO expert page.
PDF Noindex Questions
Short answers to the questions people send me.
How do I noindex a PDF?
Send an X-Robots-Tag: noindex HTTP header with the file. Google says a response header can be used for non-HTML resources such as PDFs, and gives an Apache example for .pdf files.
Can I use a meta robots tag in a PDF?
No. A meta tag belongs in the head of an HTML page, and a PDF doesn’t have one. Use the response header instead.
Should I block my PDFs in robots.txt?
No, not if you want the noindex to work. Google says that if robots.txt blocks crawling, it can’t read the rule, and the page may still appear in results.
Does noindex keep a PDF private?
No. Google says noindex only hides the page from its results, while users and other search engines can still reach it. Use a password or delete the file for real privacy.
How long until the PDF disappears from Google?
It depends on when Google revisits. Google says it may take months for some pages. You can ask for a recrawl in the URL Inspection tool.
Send Me Your URL. I’ll Hide the Right PDFs.
Message me your site address on WhatsApp and I’ll tell you which files I would hide first.
// the first look costs you one message.
Sources and Last Check
- Google Search Central: Block search indexing with noindex (meta tag, X-Robots-Tag, robots.txt warning, timing)
- Google Search Central: Robots meta tag, data-nosnippet and X-Robots-Tag specifications (the .pdf example)
- Google Search Central: Remove information from Google (delete, password, noindex)
- Search Console Help: Page indexing report (noindex and blocked by robots.txt statuses)
- Google Search Central: SEO Starter Guide (changes take hours to months)
// last checked 11 Nov 2026. My Apache and NGINX snippets are adaptations, written without backslashes, and I did not test them on any server. The time estimate is my own.