All insightsWeb Design

Check Website Download Links Before and After Replacing a File

Check website downloads after a file replacement: trace entry links, inspect the delivered version, test saving and account for old addresses.

Ivory document above a chrome downward arrow and ZXP document tray, with the headline Name the download. and supporting text Make the next click clear.
Original conceptual illustration, not a client website or measured result.

Replacing a brochure, checklist or service sheet can look like a small website update. Upload the new file, change a link and move on. But the link in a service page, an older resource entry and a customer’s saved bookmark may still lead to different versions.

Once you have decided to offer a download, treat its replacement as a short verification task. Follow the route from the public link to the file actually delivered, then check what happens at the old address. This is about maintaining an existing download, rather than choosing between a PDF and a web page.

Write down what is being replaced

Start a simple change record with the document’s purpose, current public address, approved replacement and person responsible for its contents. Include an identifying detail inside the new file, such as its version label or relevant issue date, when that makes sense for the document.

Keep the internal approval record separate from the customer-facing label. A production filename full of draft numbers may help the team distinguish working copies but tells a visitor little about what the document contains. Decide which file is approved for public use before testing the links.

For a fictional example, imagine a maintenance business replacing its equipment-preparation checklist. The new edition changes one preparation instruction. No real business or measured outcome is represented here. The test needs to establish that visitors receive the approved instruction, not merely that something downloads.

Find the routes people already use

List the pages that link to the document. Include relevant service pages, resource listings and older articles where known. Ask the website maintainer to help search the site’s content or link inventory; checking the most obvious button may miss another reference.

Record each source page and the exact link destination. Keep an old direct address too, particularly if it has appeared in emails or printed materials. You may not be able to discover every external copy, but the addresses you know give you a useful starting set.

Do not describe the inventory as complete unless its scope has been established. “Checked these five pages” is more useful than an unsupported claim that every link on the internet has been fixed. The same restraint applies to a link-checking tool: ask what it searched and what it could not inspect.

Compare the label with the delivered file

Open each recorded page as a visitor would and follow its link. Check the document title, relevant version information and changed instruction inside the file. A working address or successful HTTP response does not establish that the contents are the intended ones.

W3C’s Link Purpose guidance explains that the purpose should be understandable from the link or its programmatically determined context. Prefer a label such as “Equipment-preparation checklist” to a bare “Click here”. If the page states a file format or size, check those details against the replacement too.

In the fictional example, the test record might say: service page checked, checklist opened, new preparation instruction present. Leave the actual result blank until someone performs the check. Do not fill it with the result you expect to see.

Check opening and saving separately

A file can open in a browser or be offered as a download. MDN’s Content-Disposition reference explains the response header used to indicate inline display or attachment behaviour, including a suggested filename. Browser behaviour and the implementation still need checking.

Ask the developer what the link is intended to do, then test that behaviour on the supported desktop and mobile browsers. If the file opens, can the customer find a way to save it? If it downloads, is the saved name understandable? Open the saved copy and confirm that it contains the same approved information.

Avoid assuming that adding the word “Download” forces identical behaviour everywhere. Describe the task accurately and make the implemented behaviour understandable. If the link deliberately opens a new tab, GOV.UK link guidance recommends telling the user; it generally advises avoiding new tabs because they can be disorienting.

Decide what the old address should do

Replacing the link on a page does not automatically resolve visits to the old file address. Discuss that address explicitly with the developer. Should it lead to a directly equivalent replacement, an explanation of the change or a clear notice that the resource is no longer available?

MDN’s HTTP redirection guide describes redirects as a way to preserve existing links when addresses change. That is a mechanism, not a decision about which destination is appropriate. An unrelated homepage does not explain what happened to a particular checklist.

Test the old address after the change and record the final destination. If a redirect is intended, ask the developer to check its configuration and avoid a chain that loops or ends at another missing file. If the old edition must remain as an archive, make its status and relationship to the current edition clear.

Repeat the check after deployment

A preview check is valuable, but it does not establish what the public site serves. After the authorised update, repeat the recorded paths on the public site and open the resulting files. Note the time and environment of the check so later reviewers know what was actually observed.

If an older copy appears, investigate before repeatedly uploading more versions. Ask the developer to distinguish a stale page link, a cached response and an incorrect replacement file. The visible symptom alone does not identify the cause. Keep the previous approved material available internally until the change has been verified under your normal retention process.

Leave a useful handover record

Close the task with the approved file identity, pages checked, old-address behaviour, observed results and unresolved issues. Name who owns future content changes and who manages the website links. Repeat the relevant checks when either changes.

The aim is a small, repeatable maintenance routine. It does not guarantee search rankings, accessibility or more enquiries. It gives the team evidence that the routes checked lead to the document they intended to provide.

To discuss a website project with ZXP, bring an example download and the pages that point to it. Include any old addresses you already know about so the replacement plan starts with the real customer routes.

THE READING LIST

Sources & references

  1. 02
  2. 03
ZXP

A perspective from the ZXP team.
Designed to help you ask better questions and take a clearer next step.

FROM IDEAS TO ACTION

Plan your website project

Bring your website and the customer paths you want to review.

Discuss your website project