Skip to main content

BETANow in public beta.Public betaBeta

日本語Español

FOOT-007 Published · Updated

Footer with page feedback

Just above the footer sits "Was this page useful?" with Yes and No, and only a No opens a short form asking what was missing.

FigmaThis part is included in our free, editable Figma file: 235 website UI patterns across 32 parts, 2 designs each Open in Figma Community ↗ (opens in a new tab)

Wireframe (desktop) | Footer with page feedback

Footer with page feedback UI design (desktop wireframe)

Wireframe (mobile) | Footer with page feedback

Footer with page feedback UI design (mobile wireframe)

What changes on mobile

  1. Two full-width buttons: Yes and No sit side by side at equal widths so they are easy to tell apart and tap.
  2. Problem report below the question: The screen is too narrow to fit it on the question line, so it sits under the buttons.
  3. Full-width send button: After choosing reasons and typing, the send button spans the width so it is easy to tap.

Before you choose this pattern | Footer with page feedback

Good fit

  • You have many guidance or procedure pages and want to know which are hard to use
  • You want feedback on improving pages, separate from enquiries
  • Someone will read the feedback and fix the pages
  • Local government, school and hospital sites, help and FAQ pages

Poor fit

  • You want people to move on to a consultation or sign-up at the end of the page (the footer with CTA works better)
  • You want to ask about each FAQ answer separately (the FAQ with answer feedback works better)

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.

Related pages

Share this pattern

Send this page to your team or your design partner.

Was this pattern useful?

Written by

Yuta Okano

ENVY DESIGN Inc.

CEO / Director / Designer

14 years in the web industry. Has worked on more than 500 web projects, from corporate and recruiting sites to e-commerce. Focuses on information architecture, direction and design, from planning websites to improving them. In recent years he has focused on AIO (AI optimization) and GEO, helping sites get cited by generative AI search such as ChatGPT, Perplexity and Google AI Overviews.

Review and revision history

  1. Published AvatarYuta Okano Pattern published