Turning your impact report into web pages people actually read
Weeks of work end up in a PDF at the bottom of the About page. How to give your best stories their own pages, where donors and search engines can find them.
November 12, 2026Last updated November 12, 2026
In 2014, the World Bank looked at its own policy reports and found that nearly a third of them had never been downloaded from its document library. Unread would be one kind of sad. Nobody had even downloaded these. They were written by experts, on subjects that matter, and published by one of the best-known institutions in the world.
Your annual report probably has a smaller audience to begin with. It took a designer six weeks, the program team rewrote their section four times, and it now lives as a PDF linked from the bottom of the About page, between the privacy policy and an old job posting.
The work inside it is good, and it deserves a format people will open. This piece is about moving the best of that report onto your website, where people can actually find it, and what to do differently next year.
A PDF is built for a printer, and your readers are on phones
Most of the people who might read your report will try on a phone. Pew Research Center found that about nine in ten U.S. adults (91%) own a smartphone. Your report was laid out for a letter-size page.
On a phone, a PDF means pinching and zooming across columns made for paper. It’s slow to open. It can’t be shared one story at a time, so nobody sends their friend page fourteen. And a search engine or an AI bot has a harder time knowing that the best story your organization told this year is on page fourteen.
Governments have run into the same thing. The team that runs GOV.UK, the British government’s main website, published its reasons for preferring web pages, starting with the plain fact that “PDFs are not designed to be flexible in their layout.”
What a PDF can’t tell you
Here is a scene we suspect is common. At the spring board meeting, someone asks whether people read the report. The development director says it was downloaded a little over two hundred times. Nobody asks the follow-up question, because nobody knows the answer: how many of those people got past page two?
A PDF mostly keeps that a secret. The GOV.UK team said the same thing about their own documents: “We cannot get as much information from analytics about how people are using PDFs.” A story on its own web page is different. You can see how many people opened it, how they found it, how far they scrolled and whether any of them went on to the donate page.
PDFs are also stubborn once they’re out. GOV.UK noted that “it’s harder to update a PDF” after it’s published. If a number changes or a name is misspelled, a web page takes a minute to fix, while the PDF lives on in a dozen inboxes with the typo intact. Treat the PDF as a snapshot of the year and the web pages as the version you keep current.
Give each story its own page
The strongest parts of an impact report are usually two or three stories and a handful of numbers. Those deserve to live on your site as real pages: a student, a family, a program that worked, each with a photo and a few paragraphs. They can be shared in an email, quoted in a grant, linked from social media and found by someone searching for exactly that kind of work.
Picking which stories make the jump is easier than it sounds. Look for the ones staff already retell at events, the ones a funder asked a follow-up question about, and the ones that show something only your organization does. If a story needs three paragraphs of context before it makes sense, it probably belongs in the PDF only.
Here is a composite of how that can play out. A youth program’s report has a two-page spread about a girl who joined the after-school tutoring at nine and now volunteers there at nineteen. As a page, her story goes into the fall newsletter and gets shared by a teacher in a parents’ group chat. It’s also the first thing a foundation officer finds when she searches the program’s name before a site visit. In the PDF, it sat between a budget table and a list of sponsors.
Keep the PDF too. Funders and boards like something to print and file. It just shouldn’t be the only place your best work exists.
What a good story page looks like
A story page is shorter than people expect. Most of the good ones we’ve seen fit on two or three phone screens. They usually have a few things in common:
- A headline that says what happened, in plain words.
- One real photo, taken by someone who was there.
- Four to six short paragraphs that follow one person or one program.
- A single number, when it helps the story.
- A link to the next step, such as giving, volunteering or reading more.
Write it for someone who has never heard of you. Report language tends to drift toward words like “beneficiaries” and “capacity,” which nobody says out loud. The person in the story has a name, or a first name if they prefer, and a reason they walked through your door.
Before a story goes up, check with the people in it. They agreed to appear in a printed report a few hundred people would see, and a web page can travel much further. Ask how they’d like to be named and shown, keep their answer on file, and ask your own advisors if you’re unsure what your organization’s consent forms cover.
Put the numbers where people already look
A donor deciding whether to give is looking at your homepage or your donate page. Two or three numbers, written plainly, near the donate button, do more than a full page of charts no one reaches. We wrote more about this in before they give, donors google you.
Pick the numbers a stranger would understand without a footnote. “Families who found stable housing this year” is a number. “Program utilization rate” is a meeting. Then make sure the same numbers appear on the story pages and the homepage, so nobody finds two different figures for the same thing.
Make the PDF that remains a better one
Since you’re keeping a PDF, it’s worth making it work harder. Put links inside it that lead to the story pages, so someone who opens it on a phone has an easier way out. Add the report’s web address to the cover, so a printed copy can send people back to the site.
Accessibility matters here as well. GOV.UK warned that “PDFs can often be bad for accessibility” unless they’re made with care. Ask your designer to export it with real text, set the reading order and add descriptions to the images. That way a screen reader can read it aloud in the right order.
Plan it as web pages first
Next time, write the stories for the site and lay out the PDF from them, instead of the other way around. It’s the same work in a different order, and the stories keep working all year instead of for the week the report comes out.
In practice, that changes the calendar a little. Collect the stories and photos in the fall, publish them on the site one at a time over the winter, and share each one in your newsletter as it goes up. By spring, the designer is assembling the PDF from pages that already exist and have already been read.
If you’d like help turning this year’s report into pages people actually read, book a 30-minute call and bring the PDF.
