Empty states are small moments with a big job
Not every important website moment happens on a polished landing page.
Sometimes the important moment is when there is nothing to show.
A search returns no results. A form fails. A portal is empty on first use. An event listing has no upcoming dates.
These are empty states. They are easy to treat as small details, but users notice them when they need help most.
A good empty state turns a dead end into a clear next step.
Empty does not mean broken
A page can be working and still feel broken to the person using it.
If a search shows a blank area, the user may think the search is broken. If an event list has no dates, they may think the organisation is inactive. If a form error is vague, they may give up.
A useful empty state answers three questions:
- What happened?
- Why am I seeing this?
- What can I do next?
That structure is simple. It gives the user a way forward.
Write for the user, not the system
Many empty states are written from the system’s point of view.
They say things like “No items found” or “Invalid input”. Those messages may be true, but they do not help much.
Better copy starts with the user’s goal.
- If they searched, help them search again.
- If a form failed, explain how to fix it.
- If no events are listed, tell them what to do next.
- If a portal is blank, explain what will appear later.
This is still simple copy. It just respects the user’s situation.
Give one useful next action
The best empty states are not just messages. They are guides.
The next action might be:
- clear filters
- try a broader search
- browse all resources
- return to the main page
- contact the team
- sign up for updates
- start a new enquiry
The action should fit the moment. If the user is stuck, the first job is to help them recover, not push a random promotion.
For example, a no-results message in a resource library might offer a broader category. A form error should help the user fix the field, not send them away from the task.
Design the visual state too
Empty states are not only a copy task.
The design needs to make the message easy to notice. It should not feel like an alarm unless something has really gone wrong.
A strong empty state often includes:
- a short heading
- one or two helpful lines
- a clear link or button
- enough space around the message
- an icon or image only if it helps
Spacing matters here. It helps the message feel clear instead of lost. IGNITE’s guide on why white space matters is useful if your team is reviewing how these small interface moments sit on the page.
Error states need the same care
Error states are close cousins of empty states. They appear when the expected path breaks.
A good error message should be calm, clear and useful.
For forms, that means:
- show the error near the field
- explain what needs to change
- keep the user’s entered information
- do not rely only on colour
- avoid blaming the user
This matters because forms often sit at the point where interest becomes action. A small error can stop a useful enquiry.
First-use states can teach gently
Empty states also appear before a user has created anything.
A blank dashboard or account area can feel unfinished. A good first-use state explains what the area is for and what the user should do first.
Keep it short. This is not the place for a long manual.
The aim is to reduce uncertainty, not teach every feature at once.
Audit the moments your team may miss
During a website review, teams often look at the ideal version of each page. The search has results. The event list is full. The form works.
But users also see the less ideal moments.
Check these cases:
- no search results
- empty filtered results
- no upcoming events
- missing optional CMS content
- failed form validation
- expired campaign pages
- blank account screens
- broken downloads or embeds
A simple website audit is a good place to include these checks, because they are easy to miss when the site looks finished.
Small UX moments carry trust
Empty states will not be the hero of a website presentation.
But they are part of the experience people actually have.
When these moments are clear, the site feels more reliable. When they are ignored, even a polished site can feel brittle.
The takeaway is simple: do not leave “nothing” undesigned.