What is a website wireframe?
Most redesign arguments are really disagreements about hierarchy. A wireframe surfaces them early, when changes are cheap. Skipping the step means discovering the problem after the visual design has been approved and built.
The essentials
Wireframes settle structure and priority before aesthetic debate.
- They should be built mobile-first or at both widths.
- Annotated wireframes communicate requirements better than pictures alone.
How it works in practice
For “What is a website wireframe”, the order matters more than the speed: later steps assume the earlier ones are done.
- Write the page's goal and the one action it must support.
- Sketch mobile and desktop layouts with real content lengths.
- Annotate behaviour: what expands, what links where, what happens on submit.
- Review with a developer before visual design starts.
What to measure
Report the trend for “What is a website wireframe” rather than a single day's value, and segment before concluding.
- Number of structural changes after design review.
- Time from wireframe approval to build.
- Usability test task completion.
Where teams go wrong
These are the failure modes we see most often around “What is a website wireframe”, and why each one costs more than it looks.
- Drawing boxes with no real copy, which hides length problems.
- Designing only the desktop layout.
- Treating the wireframe as a visual design approval.
Where this fits
Part of the Websites and builders section, this answer to “What is a website wireframe” links to the questions readers usually ask next.
Frequently asked questions
What is the difference between a wireframe and a prototype?
Do I need a wireframe for every page?
What tools are used for wireframes?
Sources we checked
These are primary or first-party documents. Where the page describes our own method, it is marked as our experience rather than presented as an official rule.
Something inaccurate or out of date? Tell us and we will correct it.