Donation page website: the ask comes too early

A visitor who arrives from a shared link has no history with your organization. They know a friend posted it, and little else. The page opens on a photo, a bold heading and a Donate button, so the first decision is a payment decision. A reader who wants to know what their gift buys has to scroll past the button to find a paragraph that may be a year old. Some stop at the button. Others scroll, find the paragraph, feel the pull of it, and then see the goal bar say the target was already met. Both groups close the tab.

• Does the first screen say what a gift pays for, in one plain sentence?
• Does the button change to a closed message once the goal is met or the campaign ends?
• Does the page name the organization and the place it works, not only the cause?
• Can a visitor reach the gift form without scrolling past three photos?
• Is the organization's name the same on the button, the form and the payment step?

A shared link lands the visitor on the top of the page, and the top of the page is usually a photo. Under it sits the heading, then the button. The organization's name is often in a small logo in the corner, where a phone screen crops it. The about link, the one that would tell a stranger who runs the place, sits in the menu. So the visitor sees a picture, a sentence about a cause and a button, and has no way yet to tell a real charity from a page someone made in an evening.

The order matters more than the copy. If the what-it-pays-for line appears after the button, many visitors have already decided. You can check the order yourself: open the link on a phone, count the screens before the first sentence about the gift, and write down what you read before you reach the button. If you read nothing about the program before the button, a visitor will not either.

Landing page testing

Campaign status is often kept in three places: a progress widget, a banner near the bottom and the button itself. When someone extends the campaign or changes the end date in one place, the other two stay as they were. The widget can show a cached total, the banner can say the campaign closed, and the button can still take a gift. A visitor who sees Goal reached next to a live Donate button does not know whether to give or to leave, so many do neither.

Read the three together on a phone, after the end date you set. If the total is old, the widget is stale. If the banner says closed and the button works, the status is coming from two different settings. If the button is missing entirely, the cause is the campaign's visibility, not the total. The report gives you the screenshot of the exact state the visitor saw, which is the proof you need when you open the settings.

A visitor who has never heard of the cause checks three things before giving: the name of the organization, what it does day to day, and a way to reach a real person. On a donation page the name has to match in three places: the heading, the Donate button and the payment step. A payment step that shows only the campaign title, or a different name, makes a careful reader stop, because it looks as if the money goes to someone else.

A test can check that those things exist and open. It can tell whether the about link loads and whether the contact address is written out in the text. It cannot judge whether the cause is good, and it cannot check your registration or your tax status. Those belong to your own records and your adviser, not to a page test.

Campaigns get extended, goals get raised, and a new appeal often reuses an old donation page with its old status banner still in place. Each change can leave the progress widget, the banner or the button out of step with the others. Run a visitor from a shared link on a phone after each change, and again on the day a campaign closes.