Should This Be a PDF or a Web Page?
Put what visitors need to read, find or act on in a web page. Offer a PDF when the file itself has a job, like a printable worksheet. Here is how to choose, link and test both.
Wild Logic / LearnPut information people need to read, find or act on in a web page. Offer a PDF when the file itself has a job, such as a worksheet people will print or a diagram they need to keep at a fixed size. A single web page can do both: explain the essentials, then link to the download.
Start with what the visitor came to do
If someone wants to check hours, choose a service or request a quote, put that information where they can use it without opening a file. A web page can adapt to a narrow screen, and you can put the next action beside the information that explains it.
GOV.UK tells its own publishers to use HTML wherever possible and notes that PDFs tend to be harder for people to find, use and keep up to date (GOV.UK guidance on publishing accessible documents). That guidance is written for UK government departments, but the same reasoning helps a small business deciding how to publish a menu or service guide.
Example: Picture a catering company that posts its current menu, ordering deadline and inquiry link on a web page, and offers a separate printable menu for event planners. When the deadline changes, the team updates the page first and then checks whether the printable copy needs the same edit.
If you are still deciding which pages your site needs, start with what pages a small-business website actually needs.
Give every download a clear purpose
A PDF makes sense when the reader wants a copy to keep or print and the layout carries useful information. A one-page equipment checklist or a printable venue map can justify a download. Link to it with a description of what it contains and mark the file type, such as “Download the equipment checklist (PDF).” Put the important instructions on the web page as well if people need them to act.
Keep the editable source file and give someone responsibility for updating it. If you offer a page and a download with the same details, write down which one gets edited first.
When you replace a file, test the download link from the page. Then check the links on your own site that point to the old file, such as menus, footers, service pages and older posts, and update them to the new download if needed. Remove or replace the old copy wherever you control it.
Test the file people will actually open
Start with a structured source document. Use real heading styles and descriptive link text, and if your software has a built-in accessibility checker, run it before you export. Then export a tagged PDF when your tool supports it.
In the exported file, check the reading order and tab through any links or form fields. W3C's technique on PDF reading and tab order explains that assistive technology follows the file's tags rather than how the page looks, so a two-column layout that looks right can be read straight across both columns. These checks catch common problems, but passing them is not the same as confirming the file meets an accessibility standard. Try the file on a phone, and in print if it is meant to be printed.
Google lists PDF among the file types it can index, so a PDF can show up in search results. Being indexable does not mean it will appear, and it is no reason to bury the key information inside the download. Use the page to answer the visitor's question and make the next step easy to find.
Pick one file to improve first
Choose the download customers open before they call, book or buy. Put its most useful information on the page, keep the file if people need a copy, then open both from your phone. Check that they agree and that you can take the next step from the page. Add the download to the checks you run after a new website goes live.
Evidence
Sources
- Publishing accessible documentsGOV.UK · Retrieved
- PDF3: Ensuring correct tab and reading order in PDF documentsW3C Web Accessibility Initiative · Retrieved
- File types indexable by GoogleGoogle Search Central · Retrieved
A useful next step
Check the rest of your site too
Run the launch and first-week checks on the pages that link to your downloads.
See the post-launch checklist