Review a website
with Feedbucks.

Install and share

Place this tag before the closing </body> on the pages you want reviewed. The script registers the website’s origin and receives a stable installation ID automatically.

<script src="https://feedbucks.io/feedbucks.js" defer></script>

Open a page with ?feedbucks=1 to show the review controls. If the URL already contains a query, append &feedbucks=1. Share that visitor link with reviewers. The default widget stays hidden on an ordinary visit.

Leave feedback

1. Choose Comment, then tap or click the spot you mean. Choose the general-comment option for feedback on the whole page.
2. Select To-do for a change or Discussion for a conversation. Write what you saw and what you’d like to happen.
3. Submit and select the numbered pin to reopen its thread. Visitors can see and reply to open feedback for the review. Their names are optional.

On a phone, the editor sits above the keyboard. Swipe the page outside the editor to lower the keyboard and check the surrounding content. Your draft stays open and the pin follows its spot. Tap the text field to keep typing, or choose Send.

Pins use page elements and sections to find the spot again after a resize. A thread remains in the list when its element is hidden at the current screen width.

Dev mode

Choose Dev mode from the review controls, point at the element, then select it. Inspect the selector, pick a category such as Bug, Design, Copy or Accessibility, and describe the expected change.

For example, select a button that disappears on mobile and write “At phone width, keep this action visible below the price.” The thread carries its element context into the owner inbox. A selector helps locate the original target and can change when the host site is redesigned.

Owner inbox

Open the owner inbox and sign in with your project key, or an approved Google account when enabled. New installations appear in the private operator registry. Installing a public widget alone grants visitor access.

Search by feedback text or location, reply, switch a thread between to-do and discussion, and resolve it once the change is checked. Reopen it from Resolved if it needs more work. Export a CSV or JSON copy before expiry if you need a record of the review.

Attach a Cropped capture

For a bug that is easier to show, use Share link in Cropped after editing your recording or screenshot. Paste its viewer link into the private Cropped field on a new comment or reply. Project owners can open it from that thread in the inbox. Cropped sharing guide

Feedbucks encrypts the attached link and keeps it out of visitor responses, exports, email, and agent handoffs. The media stays in Cropped’s sharing system. Anyone with a copy of an active viewer link can use it under Cropped’s sharing settings. To stop access to the media, turn off the link in Cropped. Keep private links and passwords out of the message itself. The session playground accepts sample text only.

Approvals and handoffs

In the page’s Threads panel, choose Summarize or Send to Claude under Owner tools. A selected pin opens with its request selected. You can also start from the owner inbox and select several requests. The Fieldwork demo keeps its notes in this tab, including when you sign in to continue.

Select up to 12 requests. Free projects can summarize in the browser or copy an editable brief into Claude chat or Claude Code. With a Pro workspace, review the included text and confirm to get Claude’s summary or implementation plan in the inbox. The same choice is available for explicitly selected playground notes after Pro sign-in.

In an owner thread, open Task suggestions & handoff. Edit the title, implementation steps and acceptance checks. Use the Markdown preview to check what you intend to share. You can copy or download the brief for a collaborator or coding agent.

On a Pro project, Generate suggestions uses the configured model service. This sends selected feedback, recent replies and developer annotations. Review the free text for sensitive material first. Suggestions remain drafts until an owner chooses Add approved checklist.

For a connected GitHub repository, Draft GitHub issue opens an editable issue in GitHub. Review the destination and content before submitting. When an operator enables a private issue queue, publishing through that path requires a separate approval for the named destination.

For connected Feedbucks service feedback, a signed-in Pro operator can also choose Assign to Claude Code. Check the destination, edit the brief, then choose Approve and assign coding task. The worker checks the queue twice an hour and can propose public-interface changes in a draft pull request. A person reviews and merges it. Use the manual Claude Code handoff for work in other repositories.

Workspace billing

Reviewers can open a feedback link without an account. New owners can request access for their site. Once approved for a project, sign in with Google to see workspace plans. The Free workflow includes local summaries and editable handoffs for teammates or coding agents.

Cropped is the merchant for paid Feedbucks workspaces. Stripe hosts the card form and the customer billing portal. Check the price, billing interval and terms shown at checkout before confirming. Open the billing portal from the signed-in workspace to manage the subscription.

Try a session in the playground

Use the Fieldwork example site to leave a pin. On phones the example opens as a full page so the composer can follow the keyboard. Follow its Review inbox link in the same tab, reply to your thread, and resolve it. The sample site and its demo inbox share that tab’s session storage. These demo notes stay separate from shared website feedback.

To try the shared service itself, open a real review of the Feedbucks homepage. Feedback submitted there goes to the Feedbucks team’s private inbox.

Privacy and retention

Installation and measurement. Essential registration records the site origin, installation ID and first registration time. Optional load counts, the last measured visit time and its pathname require an affirmative choice. Open Privacy choices on the widget or Feedbucks homepage to change your preference. Global Privacy Control or Do Not Track keeps optional measurement off.

Submitted feedback. A pin includes the page path, location and viewport details needed for the review. Feedbucks drops query strings and fragments from stored page URLs. Reviewers see the open thread and its public author name. Owners can see additional page and device context. Avoid putting credentials or private contact details in the comment text.

Expiry. Shared feedback defaults to 45 days. Each project can choose a retention period from 1 to 90 days. A reply inherits the original thread’s expiry. Expired threads disappear from the API, and a daily cleanup removes expired records. Downloaded exports and provider backups have separate lifetimes.

Launch updates. The optional homepage signup is separate from testing, feedback and analytics. Feedbucks encrypts the submitted address, keeps a consent record and saves a withdrawal receipt in the registering browser. Return to the signup form in that browser to withdraw.