Why this wireframe works | Footer with page feedback
A common question at the end of each page you want rated
You only learn which pages are hard to use by gathering feedback page by page. “Was this page useful?” sits just above the footer, in the same form on the information pages you want rated. Hide it on pages where it does not fit, such as mid-application, completion and login screens. Answers are tallied together with the page URL and date. The base wireframe is a yes/no choice, but some design examples answer with a three-step rating or with faces. If you change the format, design the reason input and the after-submit message to match.
Yes ends with one press
Asking people who found the page useful to type as well makes them stop answering. Yes shows a thank-you straight away, and the form opens only on No.
What was missing can be chosen from a list
Free text alone takes effort to write and is hard to tally. Options such as “It did not have the information I needed” are listed, with details optional.
It says you do not reply, and where to ask
Questions typed into a feedback form go unanswered. Before sending, the form says you do not reply and that questions go through the contact page.
Problem reports get their own entry point
Reports such as “out of date” or “broken link” need fixing quickly. A separate “Report a problem with this page” link opens the same form with different options.
Common mistakes when building it
Asking people who answered Yes to type too
If people who found the page useful must explain why, they stop answering next time. End Yes with one press and a thank-you.
Receiving personal details
Names and phone numbers typed in end up stored with the feedback. Say near the field not to include personal details.
Not knowing which page the feedback is about
The message alone does not say which page it concerns. Record the page URL and time with each response.
Nothing changes after sending
If nothing happens, people cannot tell whether it went through and press again. Replace the panel with a thank-you message.
No one reads the feedback
Feedback changes nothing unless someone reads it and fixes the page. Decide who checks it, when and how before adding it.
Frequently asked questions
How is it different from the FAQ with answer feedback?
The FAQ with answer feedback asks whether each FAQ answer solved the problem. The page feedback footer sits above the footer and asks the same question about the whole page, in a common form, on the pages chosen for rating.
What options should No offer?
Keep to options that point to a fix. “It did not have the information I needed”, “It was hard to understand”, “It is out of date or wrong” and “Something else” — about four — are easy to work with.
How should the share of Yes answers be used?
Look at it together with the reasons for No. Start fixing busy pages where No keeps coming up.
Will it attract spam?
Limiting how often someone can send, keeping free text optional and blocking links are common measures. Saying that you do not reply also cuts down on promotional posts.













