I hit a wall last week that reminded me why some design trends should have died years ago.
I needed to find out how to do something in a piece of software. Properly stumped. And because sometimes you want a direct answer rather than an AI summary, I actually went to Google. Old habits, and all that.
Google did exactly what it should. It found the developer’s website. It even found the specific page with the answer I needed. Result.
Stop Hiding Your Answers: Why Collapsed FAQ Blocks Are Quietly Costing You Business
Except when I clicked through, all I got was a neat column of questions. Every single answer tucked away behind a drop-down. Invisible. Waiting.
So instead of landing on the information and getting on with my day, I spent the next few minutes tapping, scanning, closing, tapping again. One by one. Like some sort of weird treasure hunt I hadn’t signed up for.
The search engine had done its job perfectly. The website then made me do that job all over again.
- That’s not clever design.
- That’s friction.
- And friction costs you money.
The Logic Behind It Sounds Reasonable. It Isn’t.
Designers and developers love the collapsible FAQ. There’s always a justification ready.
“It keeps things tidy.” “It cuts down on scrolling.” “Users only open what they need.”
And yes, I get it. On paper that sounds like common sense. In practice it ignores something rather important – which is how real people actually behave on a website.
When someone lands on your page with a question burning in their head, they’re not reading every word. They’re scanning. Their brain is skipping across text looking for familiar words, phrases, anything that looks relevant.
Hidden content can’t be scanned.
You’ve taken one of the most natural human behaviours and replaced it with a manual process. That’s not design, that’s an obstacle course.
You’re Making Your Visitors Work
Every extra click on a website carries a cost that most business owners don’t think about.
Tap.
Wait.
Read.
Nope.
Back.
Tap again.
Wait again.
Each of those micro-steps costs a little patience. People don’t consciously think “this site is badly designed.” They just feel mildly irritated. And mild irritation, at scale, leads to one thing – they leave.
The brutal truth is this: if visitors have to work to find information, many of them won’t bother. They’ll go somewhere else.
That somewhere else is probably your competitor. Who, hopefully, has the good sense to just show their answers.
It Breaks the Deal You Made With Search
Here’s a problem that doesn’t get discussed nearly enough.
Search engines index the content on your pages. They pull out snippets that match what someone searched for. When that person clicks through, they’re expecting to see that content.
But if all they see is a list of collapsed questions, the connection breaks. The expectation isn’t met. The promise made in the search result isn’t kept.
It’s like a shop with a product displayed in the window, but when you walk in, it’s locked in a back room. Technically it exists. Practically it’s inaccessible. And you’ve already annoyed the customer.
That mismatch sends people away fast. Often before they’ve even read your name properly.
There’s an Accessibility Problem Too
This one matters, and it gets overlooked constantly.
Screen readers don’t always handle dynamic content well. Keyboard navigation through expandable sections can become a real pain. People with cognitive difficulties can struggle with multi-step information retrieval when they came to you with a straightforward question.
Making content visible is almost always more inclusive than hiding it. Simple is better. For everyone.
“But Won’t It Look Like Too Much Text?”
I hear this a lot from business owners. The fear of the long page. The assumption that visible content will feel overwhelming.
Here’s the thing. People don’t read websites the way they read books. They scan. They skim. They pick out the bits that matter to them.
Good typography, sensible spacing, clear headings and a logical structure solve the “too much text” problem far better than hiding content ever will. Whitespace does a lot of heavy lifting. So does breaking content into short sections with clear labels.
Collapsible sections are a workaround for poor layout, not a solution.
When Drop-Downs Actually Make Sense
I’m not saying collapsible content is always wrong. There are situations where it earns its place.
Detailed technical documentation where layered information is genuinely needed. Long specification pages with advanced settings. Content where progressive disclosure actually helps rather than hinders.
But a FAQ section on a business website? Just show the answers. That’s it. No theatre. No tapping. No treasure hunt.
The Bigger Picture
This drop-down FAQ habit is part of a wider problem in modern web design – making decisions based on how something looks rather than how it works.
Sliders that nobody ever clicks. Videos that start playing the moment someone lands on a page. Navigation hidden behind hamburger menus on desktop screens. Animations that slow everything down and help nobody.
All style, very little substance.
A website is not a portfolio piece. It’s a communication tool. If the message is buried, the tool has failed. And a tool that fails costs you customers.
The Rule Is Actually Very Simple
If someone came to your page looking for information, show them the information.
- Don’t hide it behind a click.
- Don’t make them hunt for it.
- Don’t make them work for something you could have just handed to them.
Visible content builds trust. Hidden content builds frustration. And frustrated visitors don’t convert.
If you’re not entirely sure whether your website is helping people or quietly pushing them away, that’s exactly the kind of thing I look at with clients. Sometimes the biggest improvements come from taking things away, not adding more.
Questions I Get Asked About FAQs and Usability (Yes, Really)
Are collapsible FAQs bad for SEO?
Google can generally index content inside collapsed sections, but that doesn’t mean it’s a good idea. When a visitor clicks through from a search result expecting to see specific text, they need to be able to find it immediately. Hiding answers creates a disconnect between what the search engine promised and what the page actually shows, which tends to push people away quickly.
Don’t drop-down FAQs reduce page length and improve the experience?
That’s the theory, but it doesn’t hold up in practice. People don’t read websites top to bottom – they scan. Visible content, broken into clear sections with good headings, is far easier to scan than a list of collapsed questions. A well-structured page with whitespace and clear hierarchy does a much better job than hiding information behind clicks.
Is there ever a good reason to use expandable content?
Yes, in certain situations it makes sense. Deep technical documentation with layers of detail, long specification pages, or content aimed at advanced users who only need specific sections – those are cases where progressive disclosure actually helps. For a standard business FAQ, though, just show the answers. Keep it simple.
What about accessibility? Does it matter for a small business website?
It matters more than most small business owners realise. Screen readers don’t always handle dynamic content cleanly, keyboard navigation through expandable sections can be awkward, and some users simply struggle with multi-step interactions. Showing content visibly costs you nothing and makes your site work better for a wider range of visitors.
My web designer insisted on collapsible FAQs. Should I push back?
Yes. The decision to collapse FAQs is usually made for aesthetic reasons, not usability ones. It’s your website and your customers who’ll be affected. Ask your designer to show you evidence that it improves conversions or user experience, because the research generally points the other way. Clarity and visibility convert better than clever-looking interfaces.
