Website feedback: notes on staging and live sites

A website feedback tool for client sites

Clients click the part of the staging or live site they mean and write a note, with no account and no browser extension. Each note lands on the project with the page, the element, a screenshot and the device, ready for your team or Claude Code.

Free for 14 days, no credit card needed.

Website feedback

"The form is broken" is not a bug report

We used BugHerd at Woofocus for years for notes on client sites, and it did that job well. What we kept doing by hand was the rest: copying each note into Asana, asking the client which phone they were on, and chasing them to check the fix.

This is the part of Proofyard we built for that. It works on any staging or live site where you can add a script, and the notes land on the same project as the tasks, the designs and the client. Everything below is checked against the widget and the server code as it is today.

  1. 01

    One script tag, then a review link for the client

    Paste one script tag before </body>, or add it in Google Tag Manager as a Custom HTML tag on All Pages. Then send the client a review link: the site opens with a feedback button for them alone, for 14 days unless you pick another length, up to 90, and you can turn a link off at any time. Visitors without a link see nothing, unless you switch on feedback for anyone on the site. The client clicks the part they mean, writes the note and picks Content, Design, Bug, Question or Other. Your team signs in on the site with Alt+Shift+F.

    A sample client website with a contact form: the feedback card is open on the Send the message button, the client wrote that nothing happens on their phone and picked Bug
  2. 02

    Each note carries what the developer needs

    The page and its title, the element and its text, and a screenshot of the area around the spot. Password, card and one-time code fields are greyed out in the visitor's browser before the screenshot leaves it; add the py-mask class to anything else that should be hidden. The browser, system, screen size and pixel ratio come along, and so do the last console errors and warnings and the requests that failed, without their contents or query strings. Both are on by default and have a switch per site; projects marked as healthcare start with them off.

    A website note open in Proofyard: from Maya at Acme on the live About page, with the element's text, Safari 17 on macOS at 1440x900, one console error and one failed request with status 500
  3. 03

    One board for every note, then back to the client

    Notes land on the project's Feedback board: New, To do, Doing, Test, Done. Filter them, or group by Similar issues, page, category or person; tie a note to a task or split it into its own. Send picked notes to Claude Code, which opens each one over the Proofyard connector, screenshot included, and can move it as far as Test; Done is for a person. When a note is resolved the client sees "Marked as resolved. Please check it." on their site: Looks good closes it, Still wrong opens it again with their words. Export to CSV, Excel, JSON or PDF, and import a BugHerd CSV.

    The Acme project's Feedback board with columns New, To do, Doing, Test and Done, design and website notes in New and Doing, and Open site with feedback and Settings above

The screenshots are from the app with sample data: Acme, Maya and the team are made up.

Where agencies use it

From staging to the week after launch

  1. Staging review before launch

    Send the client a review link to the staging site. They click through and leave notes where they see the problem, each with the page and the device.

  2. Content rounds

    The client marks the wrong phone number or the old price on the page itself, so nobody has to work out which paragraph "the second one" was.

  3. Bugs after launch

    A note from a phone with a console error and a failed request tells the developer more than "the form is broken".

  4. The team's own QA

    Your team signs in on the site with Alt+Shift+F and leaves internal notes; they stay internal unless someone ticks Visible to client.

  5. Fixes by Claude Code

    Send the notes; Claude Code reads them over the connector, makes the change and moves each note to Test for a person to check.

  6. Leaving BugHerd

    Export a CSV from BugHerd and import it on the Feedback board. Notes keep their page, stage and comments, screenshots are copied over, and the same file twice adds nothing.

What it will not do

Where it stops

  • It needs a script on the site. There is no browser extension, so a site you cannot add a tag to cannot take notes.

  • No video or audio notes, and no proofing of PDFs or images.

  • No two-way sync with Jira, Asana or ClickUp: the notes live on the Proofyard project.

  • Claude never writes to the client, approves or marks a note done. A person does.

Questions

Website feedback

What is a website feedback tool?

A small script on the site that lets a client or a tester click the part they mean and leave a note, which arrives with the page, a screenshot and the browser, instead of a screenshot in an email.

Does the client need an account or an extension?

Neither. A review link opens the site with the feedback button for that person. It works for 14 days unless you choose another length, up to 90, and you can turn it off at any time.

Will visitors to a live site see the button?

No. Only people with a review link and your signed-in team see it, unless you switch on feedback for anyone on the site in the project's settings.

Which sites does it work on?

Any site where you can add a script or a Google Tag Manager tag: WordPress, Webflow, Framer, Shopify or your own code.

What about private details in screenshots?

Password, card and one-time code fields are greyed out in the visitor's browser before the screenshot is uploaded. Add the py-mask class to anything else that should be hidden, or py-exclude to leave it out.

Can we export the notes?

Yes, as CSV, Excel, JSON or a PDF with a page for each note, picking the columns, people and dates you want.

Can we bring our BugHerd notes?

Yes. Import BugHerd's CSV export, up to 500 notes a file. You match the people by email before anything is filed, screenshots are copied over and notes already imported are skipped.

How does the client hear back?

Replies marked visible to the client are emailed to them, and their email reply lands back on the note. Replies for the team only never reach them.

Who makes it

Made by Woofocus, a web studio, for its own work first

Woofocus has built and looked after client websites since 2010. We made Proofyard because our own production was spread across a task tool, a feedback tool and long chat threads, and we are moving our studio's work into it now. Any agency can open its own workspace.

Ali Demirci

Ali Demirci

Founder of Woofocus

Ali has designed, built and looked after client websites since 2010 and runs Woofocus, a small web studio. Proofyard is the board he built to run Woofocus's own production after years of carrying work between Asana, BugHerd and chat.

  • 4.99/5rating on Codeable across 219 projects for 74 clientsSource: Codeable profile, October 2026
  • Since 2010building and looking after client websitesSource: woofocus.com
  • ~7,000tasks in our own Asana workspace, the work Proofyard was built to runSource: Woofocus Asana workspace, read 3 October 2026
What clients say about our work

“Communication was always clear and timely, making it easy to stay aligned on progress.”

“Ali delivered on time and worked tirelessly with us to make sure that we were satisfied.”

Try it on your own work

Put it on one client site

Open a workspace, add the script to a staging site and send yourself a review link. Free for 14 days, no credit card needed.

  • 14 days free, no credit card
  • Clients and reviewers are free
  • 3,000 Claude credits a person each month