A customer asks you to honour a price from an old brochure. Your website shows the current offer, but Google has sent them straight to a PDF you uploaded two years ago.
Start by opening the exact file URL. If it still serves the old document, changing the website page that links to it will not solve the whole problem. Decide whether that file should remain public, lead to a replacement, or disappear. Then check both the download and the search result.
Why an old PDF can still appear in Google
A PDF can be a search result in its own right. Google lists Adobe PDF among its supported indexable file types. A brochure does not need an accompanying website page to be eligible for indexing.
Think of the page and the download as two separate addresses. A redesigned services page might link to a new brochure while an earlier upload remains available at its original address. Someone following an old email, saved bookmark or search result can still reach that earlier file.
The commercial question is simple: would you be comfortable with a prospective customer using this document today? Check prices, scope, eligibility, contact details and the route to making an enquiry.
Find the actual document before changing anything
Copy the destination URL from the result and open it in a private browser window. Establish whether it is the old PDF, a newer file with an outdated search description, or a website page containing a download link.
Use a search such as site:yourdomain.co.uk filetype:pdf to look for further documents. Google’s file-type guidance explains the filetype: operator. Treat this as a discovery aid, rather than a complete inventory.
For each problem file, record:
- The full address, including any parameters, and where it is hosted.
- What information is wrong and whether the file should still be available.
- The approved replacement, if one exists.
- Known links from your website, campaign emails and sales materials.
- Who owns the content and who can change the file response.
Prioritise documents that could mislead a buying decision. An obsolete price list needs attention before a harmless historical company brochure. Do not delete every PDF simply because it appears in search.
Choose the right outcome for each PDF
Remove a file that has no useful public purpose
If the document is obsolete and there is no appropriate replacement, remove the public file and make its address return a genuine 404 Not Found or 410 Gone response.
Google’s current HTTP status guidance confirms that indexed URLs returning these client-error responses are removed from its index over time. A branded error page that still returns a successful response is a different situation; check the status, not just the appearance.
Keep any business archive somewhere suitable before removing the public copy. Ask the developer to test the old URL directly. Seeing the download disappear from a page is insufficient evidence that the file has gone.
Send visitors to a genuine replacement
If a new brochure serves the same purpose, a permanent redirect can give people following the old link a useful destination. Google’s status guidance identifies 301 and 308 as permanent redirects and strong signals for processing the target URL.
Choose the destination around the customer’s task. A current brochure may be right for someone expecting a printable specification. A maintained service page may be better where prices and options change frequently.
Test that the destination answers the original need. Avoid redirecting unrelated historical documents to the homepage as a blanket clean-up. Ask for a direct route to the replacement and check that the replacement itself works on a phone.
Keep the download available but exclude it from search
A current document may be useful to website visitors without needing its own search listing. For a PDF, Google’s noindex guidance supports an HTTP response header such as X-Robots-Tag: noindex.
The header must be delivered with the PDF response. A noindex setting on the page containing the download link does not establish what happens to the separate file.
Google must be able to crawl the resource to read the instruction. Blocking the same address in robots.txt can stop it seeing the header. Adding noindex is also not an immediate removal: Google needs to revisit the file.
Ask for evidence from the public download URL, including any external hosting or delivery layer, rather than a screenshot of a CMS setting.
Prefer an equivalent HTML page in search
If the same useful content exists as a web page and a PDF, consider which version best serves a search visitor. A web page can provide a clearer route to related services and an enquiry; the PDF can remain a downloadable alternative.
Google’s canonical URL guidance supports a Link HTTP response header with rel="canonical" for non-HTML documents, including PDFs. This can signal your preferred equivalent page.
Canonicalisation applies to duplicate or very similar content. It is a preference signal, not a guaranteed removal mechanism. An old price list and a substantially different current services page are not automatically equivalent. Decide whether to replace or remove the old file instead.
Give your developer the precise PDF-to-page mapping, and make sure the chosen page contains the information customers need.
Use temporary removal when the result needs urgent attention
For a property you own in Search Console, Google’s Removals tool can temporarily hide a URL from Google Search for about six months. It does not remove the file from your website or prevent someone opening a saved link.
Use it alongside a lasting decision about the document. Before submitting a request, check the exact address and whether you are removing one URL or everything beginning with a prefix. A broad uploads-directory request could include current documents you want customers to find.
Record the request and review its status. A temporary search block is an interim measure, not evidence that the underlying content has been corrected.
Private documents need access control
If a PDF should be available only to approved recipients, make access restriction a separate requirement. Google explains in its content-control guidance that noindex content can still be visited through a direct link. It recommends password protection for confidential or private content.
Test the actual file address while signed out. A login requirement on a surrounding page is not sufficient evidence that the download itself is protected. Ask the developer to demonstrate the intended recipient journey and the response an unauthorised visitor receives.
Give your developer a small, testable brief
For a WordPress website, distinguish the page or media record you edit from the URL that delivers the PDF bytes. Ask which server, storage service or delivery layer controls that response. The right implementation depends on that answer.
Specify the outcome per file: removal, replacement redirect, public download with noindex, equivalent-page canonical, or restricted access. Keep these decisions separate. Applying one rule to every PDF can remove useful technical documents from search or leave unsuitable material public.
Request a short before-and-after record showing the old URL, its response status, relevant headers and final destination. Include a working current document in the checks so a broad configuration change does not go unnoticed.
Check the customer journey after the repair
Accept the work against the chosen outcome:
- Removed: the old public URL no longer delivers the obsolete file and returns the agreed response.
- Replaced: the old URL leads to the correct current document or page.
- Excluded: the PDF remains downloadable and its response carries the agreed noindex header.
- Consolidated: the canonical header points to the correct equivalent page.
- Restricted: a signed-out visitor cannot retrieve the protected document.
Then follow the route from a current service page on a phone. Check that the download opens, the offer matches, and the contact link works. Recheck Google separately as it processes the change; a correct live response and an updated search result are distinct checks.
Make the next brochure update easier
Assign each public document an owner and a review date. Keep a simple register of its URL, purpose, approved version and retirement plan. When replacing it, review website links and reusable CRM email templates together.
For frequently changing information, consider a maintained web page as the main customer reference, with a PDF where downloading genuinely helps. Agree whether a document URL should always deliver the current edition or preserve a clearly identified historical edition.
BuzzBoost’s SEO services cover the wider question of what customers find and where those visits lead. If outdated downloads are creating confusion, talk to BuzzBoost about reviewing the files, choosing the right outcomes and verifying the repair.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
