Which questions should your landing page answer? Before buyers get in a flap

Alex · Founder of Magpie AI
Published · 7 min read

In short
Answer the doubts that stop people acting: what it costs, who it's for, how long setup takes, whether they can cancel, whether it works with their tools and whether their data is safe. Put the commonest doubt in a short line by the button, the rest in the sections they belong to, and keep the FAQ for rarer questions from your inbox, sales calls and searches.
Contents
The questions worth answering are the ones that stop someone pressing your button. Nearly always that's what it costs, who it's for, how long it takes to set up, whether they can get out again, whether it works with what they already use and whether it's safe to hand over their data. If your inbox keeps getting the same email, your site is leaving one of those open, and the FAQ at the bottom probably isn't where the answer should live.
The six doubts buyers bring#
Most visitors arrive carrying some version of the same six doubts. The made-up rota app below, for cafés, at shiftly.example, shows each with the kind of line that settles it.
| The doubt | What the visitor is really asking | A line that answers it on shiftly.example |
|---|---|---|
| Price | Can I afford this, and is anything hidden | "£12 a month per café, staff included" |
| Who it's for | Is this made for a business like mine | "For cafés and bakeries with 5 to 40 staff" |
| Setup time | How much of my week does this eat | "Import your staff from a spreadsheet in 10 minutes" |
| Getting out | Am I stuck if it doesn't work | "Monthly, cancel from your account in two clicks" |
| Works with what I use | Will it talk to my till and my payroll | "Sends hours to your payroll and reads your till" |
| Safety | Is my staff's data safe with you | "Data kept in the UK, and you can delete it any time" |
The research backs this list pretty closely. When Aurora Harley at Nielsen Norman Group wrote up what makes a site credible in 2016, one of her four factors was up-front disclosure, being open about everything that touches the customer's experience (base costs, fees, returns, shipping). In the studies behind it, sites that left out basic information "were almost immediately ruled out of consideration", and people went to the ones that were more open. Baymard Institute's 2025 review of software marketing sites found 33% gave no page for a particular industry, and warned that without one "many users may assume a service won't meet their needs". It says integrations are "a critical factor in decision-making" too.
Safety and getting out show up even in shops. In Baymard's checkout surveys of US shoppers, 19% of those who gave up on an order said they didn't trust the site with their card details and 13% didn't like the returns policy. That's retail, so I'd not lean on the figures for a software site, but the doubts carry over.
Answer the biggest doubt next to the button#
Whatever doubt most of your buyers have goes right beside the main button, in a few words. That's the moment they're deciding, and a visitor who has to scroll off to an FAQ to learn whether there's a contract may not scroll back. I've written about the line under the button separately, so I'll only say it should hold one doubt, the commonest, and only what's true (whether a free trial asks for a card is a doubt in its own right).
Everything else belongs in the section a visitor reads when the doubt comes up. Price goes with the plans, and showing the price at all settles more than any FAQ answer about it. Who it's for goes in the headline or the line under it. Integrations go with the features, as named logos or a list a buyer can search, and Baymard's testing found people look for an integrations link in the main navigation, the footer and on the home page. Safety sits near wherever you ask for data.
There's a reason not to leave a big answer behind a link. Raluca Budiu at Nielsen Norman Group described in 2020 how visitors who don't find enough to go on "quickly decide that the page is not worth exploring any longer and simply leave." A link labelled "FAQ" smells of very little, and asks the buyer to bet a click that their question is inside.
What the FAQ is for#
The FAQ is for the long tail, the questions a few buyers ask that the rest don't need in front of them. Refunds for a café that closes, student discounts, what happens to the rota if your Wi-Fi drops. Those are real, but they'd clutter a section.
Two camps disagree about this, and I think both are right about different pages. Susan Farrell at Nielsen Norman Group argued in 2014 that FAQs still earn their place. People reading one "may be judging your products, services, and company prior to purchasing", so the questions have to be real ones. "Questions should echo the real concerns people contact you about," she wrote, in "the vocabulary and phrasing of your visitors". The government content designers go the other way. Sarah Richards at the UK's Government Digital Service wrote in 2013 that "if a question is frequently asked, it means you need that content on your site", structured so nothing needs repeating. Canada's digital team called FAQs "a dumping ground" for whatever a department wanted to push, and kept them in one place only, a short set of answers above the email address on its contact pages. On its general enquiries page, the share of visitors who went on to send an email fell from a high of 46% to an average of 20%.
So a question people ask a lot gets an answer in the page itself, and the FAQ holds the rest. If a big doubt has been pigeonholed down there because it was awkward to fit anywhere else (cancelling is the usual one), I'd move it up.
How to find the questions people really ask#
Read what buyers already send you, before you guess. Four places hold most of it.
- Your support inbox and chat, filtered to people who haven't paid yet. Sort by how often a question comes, and copy their wording, since that's how the next buyer will think it.
- Sales and demo calls. Whatever someone asks in the first five minutes is what your site didn't tell them.
- The searches that bring people to you. Google Search Console's Performance report groups your traffic "by the search query users typed", and a query like "shiftly cancel" or "shiftly payroll" is a question asked straight into the search box.
- Reviews of your rivals, the two and three star ones especially. They tell you which doubts turned out to be justified elsewhere, and so which ones your buyers will bring. Comparing yourself with rivals has more on doing that fairly.
One swallow doesn't make a summer, and one odd email doesn't make a frequently asked question. I'd want to see a doubt come up several times before it gets a line on the page, and I'd count it again after a change, because the questions that keep coming are the ones your answer didn't settle.
Watch for the answers your support team ends up typing again and again. If someone is copying the same paragraph into replies every week, that paragraph is half written already and only needs a place on the page.
FAQ markup won't win you a search result now#
Google narrowed FAQ rich results in August 2023 to "well-known, authoritative government and health websites", and its documentation said in 2026 that the feature would no longer appear in Google Search from 7 May that year. John Mueller's 2023 post says there's "no need to proactively remove" the markup, so leave it if it's there. Just don't write an FAQ for the sake of the snippet. Write it for the person reading, who is weighing whether to trust you.
What Magpie's full report checks#
Our full report has a section called "Questions your page leaves open". It reads the whole page as a buyer of its kind would and lists the questions they'd still have, then checks each one against every section and drops any the page already answers, counting a short line under a button as much as a whole section. It shows four, each with the kind of visitor who'd ask it. Beside it, three likely buyers read the page and say what would stop them and what would win them over, so you can see whether the doubt you think matters is the one they raise.
Questions people ask#
Should the FAQ be on the landing page or a page of its own?#
A handful of questions can sit near the foot of the landing page, where someone who scrolled that far is still weighing it up. Farrell's advice for a long FAQ or long answers was a list of questions leading to their own pages, which is roughly how a help centre works, and I'd keep the two apart. The landing page's few should be about buying. How to export a rota belongs in the help centre.
Does a chat widget do the same job?#
It catches questions, which is useful, but a buyer who has to ask has already had to stop. I'd treat what people type into it as a list of answers your site is missing, and add them to the page, so the next buyer reads the answer without waiting for someone to parrot it back.
Sources
- Nielsen Norman Group, FAQs Still Deliver Great Value (Susan Farrell, 2014) (opens in a new tab)
- Nielsen Norman Group, Trustworthiness in Web Design: 4 Credibility Factors (Aurora Harley, 2016) (opens in a new tab)
- Nielsen Norman Group, Information Scent: How Users Decide Where to Go Next (Raluca Budiu, 2020) (opens in a new tab)
- Baymard Institute, 7 SaaS Website UX Fixes (Sally Collins, 2025) (opens in a new tab)
- Baymard Institute, Cart abandonment rate statistics (opens in a new tab)
- Government Digital Service, FAQs: why we don't have them (Sarah Richards, 2013) (opens in a new tab)
- Canada.ca Experience Office, Avoiding FAQs, with one exception (2020) (opens in a new tab)
- Google Search Central Blog, Changes to HowTo and FAQ rich results (John Mueller, 2023) (opens in a new tab)
- Google Search Central, FAQ (FAQPage) structured data (opens in a new tab)
- Google Search Console Help, Performance report (Search results) (opens in a new tab)

About the author
Alex · Founder of Magpie AI
Alex founded Magpie AI and writes about what turns a landing page's visitors into customers, drawing on what its audits find on real sites, from the first screen to the checkout


