Search results page examples

A search results page helps people find the right item quickly when results come from many content types. Our examples show mixed task, document, file and people results for one query, with highlighted matches and filters for type, owner and date, laid out for web and mobile in eight visual styles, light and dark. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.

DeviceAll Web Mobile

StyleAll Minimal Editorial Brutalist Luxury Playful Corporate Retro Monochrome

Theme

16 examples

Web · minimal

Web · editorial

Web · brutalist

Web · luxury

Web · playful

Web · corporate

Web · retro

Web · monochrome

Mobile · minimal

Mobile · editorial

Mobile · brutalist

Mobile · luxury

Mobile · playful

Mobile · corporate

Mobile · retro

Mobile · monochrome

See it in a flow

Search and open a result

Search results design tips

Highlight the matched words in each result so people can judge relevance without opening anything.
Label each result with its type and location, such as a task in a named project, when different content types appear together.
Keep the query in the search box and show active filters as removable chips, so refining a search never means retyping it.
Design a helpful empty state that suggests spelling fixes, broader filters or related items instead of a bare no-results message.

Questions

How should search results be grouped when there are different content types?

Either group them under type headings or show a single ranked list with clear type labels and a type filter. Grouping suits small result sets with distinct uses, while a ranked list works better when relevance matters more than type.

Which filters should a search results page include?

Start with filters that match how people remember things: content type, owner or author, date and location such as project or folder. Show the most used filters openly and tuck rarer ones behind a More button so the page stays easy to scan.

Should search show results as the user types?

Instant suggestions are helpful for jumping to known items, and a full results page is better for exploring. Many products use both: a quick dropdown while typing and a dedicated page when the person presses Enter. Debounce requests so the interface stays responsive.

Browse by pattern

App screens

Dashboard
Data table
Analytics charts
Login
Sign up
Forgot password
Two-factor code
Welcome
Onboarding step
Permissions request
Home
Feed
List view
Detail view
Kanban board
Calendar
File manager
Search results
Editor toolbar
AI chat assistant
Chat list
Chat thread
Video call
Image viewer
Map view
Video player
Create post
Class schedule
Booking details
Booking confirmed
Product detail
Cart
Checkout
Order confirmation
Settings
Profile
Notifications center
Team members
Roles permissions
Audit log
API keys
Integrations
Billing plans
Invoice
Paywall upgrade
Cancel subscription
Empty state
404 error
Loading skeleton
Success confirmation
AI workspace
AI settings
Version history
Approval queue
Doctor directory
Telehealth visit
Clinic home
Music player
Playlist
Portfolio home
Case study
Security dashboard
Project tracker
Course dashboard
Multi-step form wizard
Bank onboarding
Product scan
Split view (master-detail)
Canvas editor
Floor plan
Voice call
Toast / snackbar with undo
Confirm dialog (destructive)
Side drawer
Command palette
Date range picker
Form validation errors
Sign-in error
Card declined at checkout
Find a pro (home services)
Book a home-service visit
Job tracker
Account email
Order email
Shift scheduler
Leave calendar
Time-off request
Multi-location operations dashboard
Inventory stock
Savings goal
Onboarding carousel

UI components

Tabs
Cards
Pagination
Popover
Tooltip
Dropdown menu
Accordion
Radio buttons
Breadcrumbs
Toggle switch
Stepper
Sidebar navigation
Loading spinner

Website sections

Website templates

Building with an AI coding agent? Every screen here is also in the free Made Good Designs MCP server: ask Claude, Cursor or ChatGPT to search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.