Page Feedback Up/Down

Page Feedback adds a one-click thumbs up / thumbs down to any page, with an optional comment, so visitors can tell you whether a page helped them and why.

Responses are collected on one admin page under Content, and available through a REST endpoint, so a content team can read them directly and a reporting or automation tool such as Power BI, Excel, or Zapier can pull them on a schedule.

Features

• Plug and play: one block, no field to add per content type, no per-entity configuration.
• Thumbs up / thumbs down widget, keyboard operable and announced to screen readers.
• Reword the question, the label above each comment box and the notice under them, per block, or leave them empty to keep the shipped wording.
• An optional comment on every vote. Voting down makes the comment required, so a low score always comes with a reason.
• One admin page under Content listing every response: page, vote, comment, date, newest first.
• Delete entries one at a time or in bulk.
• Export the full feedback list to CSV directly from the admin page.
• A REST endpoint for pulling the same data into Power BI, Excel, or a reporting pipeline.

Use Page Feedback when your analytics don't tell you enough, and you need a direct answer to "did this page do its job." It's built for content and communications teams, especially in universities and government departments, who need to show that decisions about a site are based on what visitors actually say, not just on traffic numbers.

Post-Installation

After enabling the module, place the Page Feedback block through the standard Block Layout UI (Structure > Block layout). There is no other configuration step: no field to add to a content type, no settings per entity. The block detects the entity behind the page it is placed on and attaches each response to it automatically.

The block settings carry four optional fields for the wording: the question, the label above each of the two comment boxes, and the notice under them. Leave a field empty and the shipped wording is used, so a site can reword the widget, or place two blocks with different questions, without touching any code.

Responses appear right away on the Feedback page under Content. Two permissions control access: View page feedback lets someone browse and filter the collected responses without being able to change anything, while Administer page feedback grants full access, including deletion and CSV export, and is flagged as a restricted permission so it isn't handed out by default. The same permissions gate the REST endpoint.

Additional Requirements

Page Feedback has no contributed module dependencies beyond Drupal core.

Recommended modules/libraries

Honeypot pairs well with Page Feedback on high-traffic anonymous forms, adding a second layer of bot protection alongside the module's own safeguards against repeat voting.

Similar projects

A few other projects address related needs:

• Rate provides a general-purpose voting and rating framework for nodes, comments, and other entities, with widgets like stars, thumbs, and emotions. It is a strong choice for general voting. Page Feedback focuses narrowly on a single "was this page helpful" flow, with a built-in comment field and a dedicated admin review screen out of the box.
• Feedback collects short text messages from visitors but does not track a helpful / not helpful signal and has no REST endpoint for reporting.
• Simple Feedback offers a lightweight yes/no widget without a comment field, an admin review screen, or an API.

Supporting this Module

Page Feedback is free and will stay free. Coming soon: an optional, separately hosted AI service. Feed it thousands of votes and comments, and it hands back a report you can actually use: sentiment, recurring themes, trends over time, in plain English instead of a spreadsheet. It runs apart from the module, and using it is entirely your choice. Watch santerref.com for details.

Community Documentation

Documentation and a demo site are in progress. Links will be added here once available.