When you migrate off WordPress, your PDFs and other downloadable files have to be migrated like any other content, because they live in your media library at real URLs, they can rank in search and be linked from other sites, and if their URLs break, those links and rankings are lost. So you move the files to the new site, keep them at the same URLs where you can, and 301-redirect any that must change, exactly as you would for pages. You also update the links that point to them, in your pages and menus, so no download button leads to a 404. PDFs are indexable documents in their own right, so a whitepaper or price list that ranks is worth protecting deliberately, not treating as a loose file. WPBuildAI migrates your files, preserves their URLs or maps them to verified 301s, and fixes the links that point to them, so every download keeps working and any ranking documents hold.

Files are content, with URLs that matter

The key realization is that a downloadable file is not a loose attachment; it is content with an address. Your PDFs, spreadsheets, and other downloads sit in the media library at real URLs, usually under a path like /wp-content/uploads/, and those URLs are what your pages link to, what visitors bookmark, and what other sites reference. So a file is subject to the same rule as a page: preserve its URL or redirect it, or the links break. Treating files as first-class content, rather than something that tags along, is what prevents the quiet loss of downloads in a migration, and it puts them in the same category as your images, which also need their URLs preserved.

PDFs can rank, so they earn URL care

It surprises some people that a PDF is indexable, but Google reads and ranks PDF documents as pages in their own right. A whitepaper, a buyer’s guide, a manual, or a price list can rank for real queries, attract traffic, and earn inbound links, which means it carries SEO value you would not want to throw away. Since traffic and links concentrate on a minority of URLs, as the Ahrefs study shows, a single popular PDF can be a meaningful asset. That is the argument for giving files the same treatment as pages in a careful site move: identify the documents that rank or are linked, and make certain their URLs survive the migration intact.

Keep the same URLs, or redirect them

The mechanics mirror your page migration. Wherever possible, keep each file at the same URL on the new site, so every existing link, internal and external, keeps resolving with no further action. Where a file’s URL must change, 301-redirect the old URL to the new one, so visitors and any link value follow the file to its new home, exactly as a 301 is meant to work. To do this without gaps you need the full list of file URLs, which is why extracting every URL for redirect mapping should include documents, not just pages. Files are easy to forget precisely because they are not pages, so pulling them into the same URL map is what keeps them from slipping through.

Migrating the files is only half the job; the links to them have to point at the right place too. Your pages, menus, and buttons contain links to those downloads, and if they still reference old paths after the rebuild, the download breaks even when the file exists. So updating on-page download links is part of the same pass as fixing broken links generally. Check the obvious places first: a “Download the guide” button, a resources page, a footer link to terms as a PDF. A file that migrated correctly is still useless if the button that should reach it points at a dead URL, so verify the path from the page to the file, not just the file itself.

Respect the public or gated status of each file

Not every file is meant to be public, so preserve each one’s access model. A publicly linked download should keep its public URL and stay reachable. A file that was genuinely gated behind a form or a login should stay gated on the new site, delivered the same way, not accidentally exposed at a public URL. The migration should carry the intent, not just the bytes, so decide per file whether it is public or restricted and rebuild the delivery to match. Getting this wrong in either direction is a real problem: an exposed private document, or a public resource that suddenly asks for a form, so it is worth a deliberate check on anything sensitive.

Steps to handle files and PDFs in a migration

  1. Inventory your files: PDFs, spreadsheets, and other downloads in the media library.
  2. Flag the ones that rank or are linked using Search Console and your analytics.
  3. Migrate the files to the new site, keeping the same URLs where you can.
  4. 301-redirect any file URLs that change, alongside your page redirects.
  5. Update on-page links and buttons so every download resolves.
  6. Preserve public or gated status per file, and test a real download of each key one.

Worked example: protecting a whitepaper that ranked

Consider a B2B site whose flagship whitepaper PDF ranked for a valuable query and had picked up links from industry blogs over the years. Migrating off WordPress, the team treated the PDF as an asset, not an afterthought: they included it in the URL inventory, kept it at the same address on the new site, and confirmed the download button on the landing page pointed at that address. Because the URL never changed, every external link and the ranking itself carried straight over, and visitors clicking the button got the file as before. Had the PDF been left behind or moved without a redirect, the ranking and the backlinks would have evaporated silently, which is exactly the loss the inventory step prevented.

Limitation: some files should be retired, not migrated

It is honest to bound this. Not every old file deserves to move; a superseded price list, an outdated brochure, or a stale document may be better retired than carried forward. For those, decide deliberately: 301 the URL to the current equivalent if it had traffic or links, or let it go if it truly did not matter. Large media libraries also add weight and clutter, and files are already a big share of what sites carry, as Web Almanac 2024 notes, so a migration is a chance to prune as well as preserve. The rule is to migrate the files that matter with their URLs intact, and retire the rest on purpose rather than by accident.

Key points

When you migrate off WordPress, your PDFs and downloads are content that must be migrated deliberately, because they live at real URLs that can rank and be linked, and broken file URLs lose those rankings and links. Keep each file at the same URL where you can, 301-redirect any that must change, and include files in the same URL map as your pages so none is forgotten. Update the on-page links and buttons that point at the files, since a migrated file is useless behind a dead link, and preserve each file’s public or gated status so nothing is exposed or hidden by accident. Retire genuinely obsolete files on purpose rather than letting them break silently. WPBuildAI migrates your files, preserves their URLs or maps them to verified 301s, and fixes the links that point to them, so every download keeps working and any ranking documents hold. Send your web address for a free analysis.

Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.