Landing page checklist: check it as a stranger

The owner of a page has a logged-in browser, cookies from every test, cached images and a memory of what each button does. None of that is available to a stranger who clicked a link a friend sent. The owner scrolls past the cookie banner without reading it, knows where the menu opens, and fills the form with an address they already use. A checklist run from the owner's seat passes items that fail for a stranger. To see what the stranger sees, clear that context and start from the link.

• Address: does the link reach the page directly, with no redirect loop or login wall?
• First screen on a phone: is the product named, and is the main button above the fold?
• Cookie banner: does it cover the button, and does closing it keep the page usable?
• Form: does each error name its field, and does the page keep what the visitor typed?
• Thank-you step: does it say what happens next, and does the email link to the live domain?

Owners tend to test from the homepage. A stranger usually starts from a link: a post, an ad, a message from a friend or a directory listing. That link can carry a redirect, a tracking parameter or a different path into the site. Click it from a fresh session and note every address the browser passes through before it lands. If the link's redirect drops a parameter, the page may show a generic first screen. That is a fault you will never see from the homepage.

Before anyone clicks, a link often appears as a small card in a chat, a feed or a message. The card's title, description and image come from the page's meta tags, and an empty or default value becomes the first impression. Paste the address into a chat with yourself and read the card the way a stranger would. Check that the title names the product, the description says who it is for, and the image is not an old banner. A card that reads Untitled tells a stranger the page is unfinished, even when the page works.

Landing pages change after launch: a new banner, a booking widget, a chat box or a rewritten headline. Each change can cover the action the page exists for, and the owner rarely notices, because they already know where the button is. Run the four steps again after each change, on a fresh session, and compare where the stranger stops with the last run. A checklist kept in a document and run once before launch is how a banner ends up sitting on the button for a month.

Test the site before launch

Landing pages keep changing after launch: a new banner, a booking widget, a chat box, a rewritten headline. Each one can cover the action the page exists for, and the owner rarely sees it, because they know where the button is. Run the same stranger path after every change, on a fresh session, and compare where it stops. Test any page behind a login with a test account, and check it again before a new traffic source starts.