Landing Page Headlines Built From a Visitor's First Question
Most landing pages open with what the founder wants to say. Visitors arrive with something else in mind: a single question about whether this page is relevant to them. When the opening lines answer a different question than the one the visitor is asking, people leave within seconds, even when the product is a good fit. This article looks at a specific angle that is easy to overlook: starting from the first question a visitor brings, then building the headline, subhead, and first screen around that answer. The approach works for any founder launching a personal brand site, whether it lives on a subdomain or a custom domain, and it does not depend on any particular tool or feature set.
Why the first question matters more than the pitch
A visitor who lands on a page from a link, a post, or a referral has usually asked themselves one quick question: is this for me? That question is narrower than what a founder means to communicate. The founder may want to describe a product, a philosophy, and a history. The visitor wants to know whether the page covers the problem they were thinking about when they clicked.
Before writing anything, list the three or four situations that would send someone to your page. A consultant may be found by someone searching for help with a specific deliverable. A creator may be shared by a friend with a particular interest. Each situation produces a different first question, and your headline should answer the one most common for your audience, not the one you find most interesting to write about.
Turning a question into a headline and subhead
Write the visitor's first question in plain words, as a stranger would phrase it. Then draft a headline that answers it directly within the first ten words. Avoid generic claims such as expert, passionate, or innovative unless you can show what they mean. A headline should name the thing the visitor cares about, the audience it serves, and the next step, without asking them to infer any of the three.
The subhead expands the answer with one concrete detail. If the headline says a freelance designer builds brand pages for small studios, the subhead might explain the format of the work or the typical starting point. Keep it to a single sentence. If you need two sentences to explain the answer, the headline is probably answering a question that is too broad.
A checklist for the first screen
Once you have a draft headline, run through these checks before publishing. First, read only the headline and subhead aloud, then ask a friend who does not know your work to say what the page offers. If their answer differs meaningfully from your intent, the copy needs revision. Second, confirm that every claim on the first screen is something you can actually deliver or demonstrate. Do not describe features, service levels, guarantees, or results that you have not confirmed exist in the platform or in your own practice. Third, make sure the single call to action matches the question you answered. If the headline promises a way to start working together, the button should not ask for an unrelated commitment.
Fourth, check the page on a narrow phone screen, since many visitors arrive on mobile and the headline is often cut off at the fold. Fifth, write down the one action you want visitors to take and remove any other prominent link that competes with it on the first screen. These checks are simple, and they catch the majority of problems that cause early exits.
Testing the angle with real visitors over time
A headline built from the visitor's first question is a hypothesis, not a finished result. Set a reminder to revisit it after a few weeks of traffic. Look at whether people are scrolling, whether they click the primary action, and whether they arrive through the sources you expected. If your page receives visitors who ask a different first question than you planned for, that is useful information: it suggests a second audience that may need its own page or a different headline.
Keep a short log of each revision, the question you believed the page answered, and what you observed afterward. Over time this log becomes more useful than any single piece of advice, because it reflects your actual audience rather than assumptions about what founders in general should do. The goal is not a perfect headline but a page that matches the reason people came.