Keep the same public path when the new PDF replaces the old one for the same purpose. If the old edition must remain available, give the new edition its own URL and update the page that introduces it.
Find the URL behind the button
Open the download from your public website and copy the final address. Compare it with the link on a printed QR code or an email you already sent. A page titled “Our Menu” may link to a PDF on your domain, a file in a website builder, or a document hosted by someone else. Each needs a different update.
For a static site, find the file that your build actually publishes. For example, a source file under public/files/ may be served at /files/menu.pdf. Confirm the output path and capitalization before overwriting anything. If the file is hosted externally, use that provider’s supported replacement method or update links you control.
Decide whether to reuse or version the address
For a current menu, an address such as /files/menu.pdf can stay stable. Replace the file at that exact path, keep a dated internal copy, and put the effective date in the PDF so customers can recognize the current version.
For documents people may need to cite by edition, use dated filenames and link to the current edition from a normal web page. If you must retire an old public file and the new one genuinely replaces it, consider a permanent redirect. Check old links to specific PDF pages as well, since pagination can change between editions.
Review the document before sending it live
- Export the approved PDF and check the dates, prices, phone numbers, and links in the actual exported file.
- Open the PDF on a phone. Check that the text is readable and selectable where practical. Keep essential details on a normal HTML page when customers need to find them quickly.
- Check that the export contains only information meant for the public. Review comments, attachments, and visible metadata before publishing.
- Save the previous approved version and the exact public URL. If you use GitHub and Cloudflare Pages, preview the change using the website update workflow.
Test the exact link your customers already have
After deployment, open the old shared URL from a fresh browser session. Confirm it loads the expected PDF and that the visible date or changed text matches the approved copy. Open it from the download button and scan any printed QR code that should still work. If the PDF opens correctly in a fresh session but appears outdated in a regular tab, check the browser’s saved copy and the cache headers your host sends.
Cloudflare Pages documents how static files use an ETag for revalidation. Custom headers or another cache can change what visitors receive. Check which deployment served the file and which cache rules apply before renaming a working URL to solve a stale-copy issue.
Write down who owns the next change
Record the approved PDF, the exact URL, who can publish it, and how to restore the previous version. For a first DIY website, the BUILD • PUBLISH • OWN IT guide covers the broader GitHub and Cloudflare publishing workflow.
Sources and further reading
Need help managing website updates?
Share the current PDF link, the replacement file or approval status, and any printed materials that use the old address.