Niwa View demo
Niwa
niwa@niwachat.comContact
The notebook

Update a PDF menu in WordPress without leaving old links

Replace an outdated PDF menu, check the links customers already use, and review the page changes without leaving old documents in circulation.

An ivory menu on a sage clipboard beside a phone with matching menu lines, a fork and a folded napkin.

You upload the new catering menu, open your website and click Download. Last season’s PDF appears. The new file is in WordPress, but the button still points to the old one.

Updating a PDF in WordPress involves two things: the document customers receive and the links that take them to it. Before changing either, decide whether the existing file address needs to keep working. That matters if the menu has already been shared in emails or printed as a QR code.

Start with the link your customer actually uses

Imagine a catering business in Ohio preparing its fall lunch menu. This is a fictional example. The website has a catering page, a homepage button and a QR code on printed order cards. The owner has approved the new dishes, ordering deadline and delivery area.

Open each route and record the destination. A button labeled Catering menu might lead straight to a PDF, to a WordPress page containing the PDF, or to a separate document service. Those routes need different updates.

Customer’s route What to check
Website menu button Does its saved link open the current PDF or a menu page?
Printed QR code Does the encoded address still reach the intended menu?
Link in an earlier email What happens when someone opens that exact old address?
Previously downloaded PDF This is a separate local copy; a website update cannot rewrite it.

In Media > Library, open the existing PDF’s details and copy its File URL. WordPress’s Media Library documentation distinguishes the direct file URL from the attachment page. Record the direct address, not just the media item’s title.

Save the approved new PDF and a copy of the previous file somewhere you can identify them. Open the new document before uploading it. Check every page, its effective date, the business contact details and any links inside it. A correct website link will still deliver the wrong menu if the exported file is wrong.

Choose a new file address or preserve the existing one

Upload a new file when you can update the links you control. Give it a useful name, such as catering-menu-fall-2026.pdf, then copy the URL WordPress actually assigns. Do not construct the address from memory.

Uploading another file with the same name is not a reliable replacement method. WordPress’s filename handling adds a number when it needs to avoid a collision in the upload directory. A new upload can therefore have a different address while the earlier PDF remains available.

Preserve the file address when existing direct links must keep working. Ask the site maintainer which replacement method the site supports. For example, the developer’s Enable Media Replace documentation describes an option that replaces a file with the same file type while keeping its name. It also describes a separate option that changes the name and updates links. Those are different choices; confirm the resulting URL before using either.

This does not mean every site needs another plugin. Use a method the maintainer has checked for that site’s media storage and backup process. A feature that updates website links cannot edit a PDF someone already downloaded or change the address printed inside a QR code.

Update the page’s file block and other links

For a standard WordPress File block, select the block and choose Replace, then upload the approved PDF or select it from the Media Library. The File block guide explains replacement, copying the file URL, the download button and the optional inline PDF display.

Treat this as a change to that block. Check other buttons, text links and repeated uses separately. A homepage button may store its own destination; a builder widget may need to be edited in its builder. Review the page and save the intended changes.

Use a label that explains the destination, such as Download the fall catering menu (PDF). The W3C guidance on link purpose explains why meaningful link text helps people choose which link to follow. Also provide a clear text link when using an embedded preview, and test it on a phone.

For the Ohio caterer, the nearby page copy needs attention too. If the PDF now lists a different ordering deadline, an unchanged sentence above the button may contradict it. Compare the approved document with the page’s ordering instructions before publishing.

Use Niwa to prepare the page changes

Niwa’s page tools can read a WordPress page’s stored content and prepare a page update, subject to the site’s enabled tools and permissions. Once a person has verified the PDF and its final URL, Niwa can help update the relevant page link and surrounding copy.

Give it the exact page ID, old link, new link and approved wording. For example:

Read the catering page using the page ID I provided. Prepare a change from the old menu URL to the verified new URL below. Use the approved download label and ordering deadline I supply. Preserve the page address, title, contact details and other content. Show the complete proposed page content for review before applying it.

Supply the actual URLs and text with that request. Review the complete proposed content: Niwa’s standard page-content update writes the content field, so a narrow request still needs a careful check of what will be saved. This workflow does not assume that Niwa replaced the PDF file, edited a printed QR code or changed every builder widget.

Keep SEO changes deliberate as well. Replacing a menu does not require renaming the page or rewriting every heading. Our guide to reviewing SEO changes before publication provides a separate review process when those fields also need work.

Verify the document, then retire the old route deliberately

After saving, open the public page while signed out. Follow the download link on desktop and mobile, then inspect the actual PDF. Check the new menu content, not just the filename or a successful page load. Scan a printed QR code and test an old email link if those routes exist.

If the URL is correct but the old document still appears, consider caching. MDN’s HTTP caching guide explains how browsers and shared caches can reuse stored responses. The page and the PDF are separate resources. Ask the maintainer to check the affected file’s caching path, then verify the ordinary public link again.

Do not delete the old upload merely because the new menu works on one page. If you chose a new URL, decide what the old address should do and have the maintainer implement and test that behavior. Otherwise, earlier links may still serve outdated content or stop working.

For future printed materials, our recommendation is to point people to a stable menu page that you maintain, with a clear current download and revision date. That reduces the number of places where a changing file address must be printed. It still needs a real check after each update.

Bring your menu page and one approved change to a Niwa demo. During your Niwa demo, we cover the subscription and AI usage. There is no obligation to buy.

Leave a Reply

Your email address will not be published. Required fields are marked *

Niwa
How can I help?
Chat with Niwa