Everything the extension does, and what ends up in a shared review or an exported file.
Website Feedback Tool is a Chrome extension for visual feedback. You click on a page to leave comment pins, then share a link. Whoever opens the link sees a frozen copy of the page with your pins on it — no extension, no account, no setup on their side.
The extension only ever activates on the tab you point it at, and only when you ask it to.
The ? button at the top of the popup opens Help: links to these docs, the AI-agent guide, keyboard shortcuts, and a list of tips about features you may not have found yet.
In annotation mode, hovering highlights the element under the cursor. Click it, type your note, press Enter. A numbered pin appears and stays anchored to that element — it follows the element when the page scrolls, resizes, or reflows.
Press and drag to draw a rectangle instead of a single point. Useful when the problem is a region — a broken layout block, a group of items — rather than one element. Drags under 10 px count as clicks, so a shaky hand won't create stray boxes.
Alt + A pauses annotation without discarding anything, so you can click a link, open a menu, or scroll a widget that annotation mode would otherwise intercept. Press it again to resume.
Save & Share captures a snapshot of the page — markup, styles, images, canvas and video frames as they are at that moment — uploads it, copies the link to your clipboard and opens it in a new tab. Your original page is left clean: pins are cleared and annotation mode switches off.
Whoever opens the link can:
The Visible to site owner checkbox under Save & Share decides whether the site's staff see this review in their admin area.
wft.json.localhost, an IP address, a local
file) is never listed in an admin area, because no site can claim that address. Its
Site owner row still shows what you chose when sharing.Forgot something? Open your review link, open the extension popup and click Add comments. The review page switches into annotation mode: click or drag to add comments as usual. They are numbered after the ones already there, so with three published comments your first new one is 4. Then click Save to review. The page reloads with the new comments in it, and the link stays the same, so everyone you sent it to sees them too. Replies and Resolve work on them straight away.
The clock icon in the popup header opens Your reviews — everything you have shared, newest first, with the page title, comment count and age. Click one to reopen it.
Hover an entry and click ✕, then confirm. The snapshot is deleted from the server immediately and the link stops working for everyone.
Deletion works through a secret token stored in your browser when the review was created — that's what proves the review is yours, since there are no accounts. Consequences worth knowing:
Export comments as JSON in the popup downloads the comments as a file — available both while annotating and while viewing a shared review.
The file is meant for whoever fixes the page. Every comment carries the CSS selector of the element it's about, what that element is, its computed styles, the CSS rules that match it, and its ancestor chain — enough to open devtools and go straight to the fix. Page and viewport dimensions travel along, because a coordinate on its own means nothing on someone else's screen.
Typical uses: attaching to a bug ticket, feeding an AI assistant, or scripting a report.
Files are named wft-comments-<host>-<date>.json. Exporting from a
review takes the styles as they were when the snapshot was captured, not as the live site
looks today.
The point of the selector, computed styles and matched CSS rules in each comment is that an agent doesn't need to open the browser to act on the feedback — it can go straight to the source file. Drop the exported file into your repo (or point the agent at its path) and ask it to work through the list:
I exported feedback comments from a website review tool as wft-comments-example.com-2026-09-27.json.
For each comment in the file:
1. Skip it if target.found is false (note it instead — the element is gone).
2. Use target.selector and target.element to find the matching markup/component in this repo.
3. Use target.matchedRules[].source to find the stylesheet, and target.matchedRules[].selector
to find the rule to edit — target.styles is the computed result, not what to copy in.
4. Apply the fix described in the comment's "text".
Report back which comments you fixed, which you couldn't map to a file, and which were skipped.
Two things make this reliable: check formatVersion first — an agent built
against this doc should refuse to guess on a version it doesn't recognise — and treat
target.found: false as a hard stop for that comment, not something to
work around from lastKnownRect alone.
The export above is a file you hand over. The other route is to let the agent fetch the review itself, and answer it. The MCP server exposes four tools:
get_review takes a share link (or the bare review id) and returns
the review as JSON — page URL and title, capture time, viewport, and the numbered
comments with their CSS selectors, each with its status (open or resolved) and
its replies.reply_to_comment posts a reply to one comment, named by its pin
number or id, and can mark it resolved in the same call.set_comment_status resolves or reopens a comment without a
reply.page_snapshot_instructions goes the other way: it tells an agent
that drives a browser how to make a review itself. See below.
page_snapshot_instructions means you can ask for a review instead of
making one: "snapshot this page and comment on what looks wrong". It needs an agent that controls a browser,
through chrome-devtools MCP, Playwright MCP or its own code. The tool captures
nothing itself. It returns the steps and the code to run in the page, and the agent
comes back with a share link. Since the browser is the agent's, the capture can be of
a page behind a login or on localhost, though images and fonts stay links to the
original, so a reader who cannot reach them will not see them. Like any review, the
copy is stored on our server and anyone with the link can read it. Pages with a strict
Content Security Policy can block the code, and the steps say what to do then; the
browser extension is not affected by it.
The server is remote: it runs inside Website Feedback Tool at
https://website-feedback-tool.com/mcp. There is nothing to install or
run and no keys to set, so you connect it by URL. Claude Code:
claude mcp add --transport http website-feedback-tool https://website-feedback-tool.com/mcp
Codex, in ~/.codex/config.toml:
[mcp_servers.website-feedback-tool]
url = "https://website-feedback-tool.com/mcp"
Any other client that speaks streamable HTTP:
{
"mcpServers": {
"website-feedback-tool": {
"type": "http",
"url": "https://website-feedback-tool.com/mcp"
}
}
}
A Claude plugin with the same URL and a fix-review skill, which tells the
model what to do with a review, is available on request; see the
AI agents page.
The MCP payload carries a deliberate subset of the file export's
target detail, and marks itself as one: producer: "server" and
targetDetail: "none". Computed styles, matched CSS rules and the
ancestor chain are missing — not withheld, but unbuildable. The extension resolves
every comment against a live DOM; the server has no layout engine and would have to
invent them. For an agent working inside your source that is usually no loss: the
CSS is right there, unminified.
It adds what the file export does not have: each comment's status
(open or resolved) and its replies, the same
replies and statuses the review page shows. If they cannot be read, the comments still
come back, with a discussion_error saying why.
Replies and status changes appear on the review page for everyone holding the link. Unless told how to sign, the agent uses your name when it knows it, and otherwise signs them AI assistant.
token_urlsafe, and anyone holding the link
can already read every comment, reply and resolve by opening it. The tools do the
same in a shape a model can act on and grant no new access — but a share link is a
bearer token, and it lets the agent write as well as read, publicly and under any
name it is given. Hand it to an agent you would hand the link to.
Side-by-side guidance on choosing between the file and the server is on the AI agents page.
Current version: formatVersion: 1. Check this field before parsing — it is
bumped whenever the shape changes incompatibly.
| Field | Type | Meaning |
|---|---|---|
tool | string | Always "Website Feedback Tool" — lets a consumer recognise the file. |
formatVersion | number | Schema version. |
exportedAt | string | ISO-8601 UTC time the file was produced. |
page | object | The page the comments are about. |
environment | object | Browser and screen facts: ua, platform, language, screen, viewport, dpr, colorDepth. May be null. |
commentCount | number | Length of comments. |
comments | array | Comments in the order they are numbered on the page. |
page| Field | Type | Meaning |
|---|---|---|
url | string | Address of the annotated page — for an export made from a review, the original page, not the review link. |
title | string | Page title at capture time. |
capturedAt | string | ISO-8601. From a review, this is when the snapshot was taken, which may be long before exportedAt. |
layout.viewport | object | {width, height} of the visible area, CSS pixels. |
layout.document | object | {width, height} of the full scrollable page. |
layout.scroll | object | {x, y} scroll offset — relates page coordinates to viewport ones. |
layout.devicePixelRatio | number | 2 on a typical HiDPI screen. |
comments[]| Field | Type | Meaning |
|---|---|---|
number | number | 1-based — the number drawn on the pin. |
id | string | Internal id. Useful for de-duplication inside one file, nothing more. |
text | string | What the reviewer wrote. It's user input — escape it before rendering as HTML. |
type | string | "point" (a pin) or "rect" (a dragged region). |
position | object | {x, y} page coordinates of the pin; for a region, its top-left corner. |
size | object | {width, height} — regions only. |
target | object | What the comment is about. See below. |
comments[].targetResolved when the export runs, against the DOM in front of you. From a review page that DOM is the captured page, so the styles are the ones the reviewer saw.
| Field | Type | Meaning |
|---|---|---|
found | boolean | Whether the element was located. If false, the block carries reason, plus selector and lastKnownRect where known. |
reason | string | "not-in-dom" — the element is gone; "area-selection" — a region whose centre couldn't be hit-tested; "no-selector". |
lastKnownRect | object | Geometry recorded when the comment was made, for elements that have since disappeared. |
resolvedBy | string | "selector", or "area-center" when the element was found by hit-testing the centre of a region. |
selector | string | CSS selector for the element — paste it into devtools. |
element | object | tag, id, classes, attributes, text, truncated html. |
rect | object | page and viewport coordinates plus width/height. |
pointInElement | object | {x, y} as fractions 0..1 of the element's box — the one part of the geometry that doesn't depend on screen size. Absent for regions. |
styles | object | Computed values grouped as layout, box, typography, visual. |
matchedRules | array | The authored CSS rules matching the element: selector, css, optional media, and source. |
ancestors | array | Up to 3 parents with display, position, overflow, transform, zIndex, size. |
scrollContainer | object | Selector of the nearest scrollable ancestor, when the comment sits inside one. |
pinnedToViewport | boolean | Present when the element was fixed or sticky at the time the comment was made. |
truncated: true.{
"tool": "Website Feedback Tool",
"formatVersion": 1,
"exportedAt": "2026-08-20T09:20:00.000Z",
"page": {
"url": "https://example.com/pricing",
"title": "Pricing — Example",
"capturedAt": "2026-08-20T09:15:00.000Z",
"layout": {
"viewport": { "width": 1280, "height": 720 },
"document": { "width": 1280, "height": 4200 },
"scroll": { "x": 0, "y": 900 },
"devicePixelRatio": 1
}
},
"commentCount": 1,
"comments": [
{
"number": 1,
"id": "m9x2k1a",
"text": "The button doesn't respond on mobile",
"type": "point",
"position": { "x": 412, "y": 1180 },
"target": {
"found": true,
"resolvedBy": "selector",
"selector": "#pricing > div > button",
"element": {
"tag": "button",
"classes": ["cta"],
"attributes": { "data-testid": "buy", "aria-label": "Buy Pro" },
"text": "Buy now"
},
"rect": {
"page": { "x": 412, "y": 1180 },
"viewport": { "x": 412, "y": 280 },
"width": 132, "height": 44
},
"styles": {
"layout": { "display": "inline-block", "position": "static" },
"box": { "padding": "12px 20px", "boxSizing": "border-box" },
"visual": { "backgroundColor": "rgb(91, 91, 214)", "pointerEvents": "auto" }
},
"matchedRules": [
{
"selector": ".pricing-card .cta",
"css": "background: #5B5BD6; color: #fff; padding: 12px 20px;",
"source": "https://example.com/assets/app.css"
},
{
"selector": ".pricing-card .cta",
"media": "(max-width: 600px)",
"css": "padding: 8px 12px;",
"source": "https://example.com/assets/app.css"
}
],
"ancestors": [
{ "selector": "#pricing", "tag": "section",
"styles": { "display": "block", "overflow": "hidden" } }
],
"pointInElement": { "x": 0.5, "y": 0.41 }
}
}
]
}
| What | Limit |
|---|---|
| Shared review lifetime | 90 days, then permanently deleted |
| Locally stored comments | 30 days per page, cleaned up automatically |
| Review history in the popup | Last 100 shares |
| Snapshot size | 50 MB per review |
| Sharing rate | 5 snapshots per minute, 30 per hour |
| Comment text | 10 000 characters per comment |
| Comments added to a review later | 500 comments per review in total; 10 saves per minute, 100 per hour (a save of more than 50 comments counts as several) |
| Replies | 4000 characters each, names up to 80; 1000 replies and status changes per review; 20 posts (replies or status changes) per minute, 200 per hour, per IP address |
| Total storage | 10 GB; above it new snapshots are refused until old ones expire |
| Accounts | None — nothing to sign up for |
What is stored and for how long is spelled out in the Privacy Policy.
Chrome doesn't allow extensions on its own pages (chrome://, the Web Store,
other extensions' pages). Try a regular site.
For file:// pages, turn on Allow access to file URLs in the
extension's settings, then reload the page. The popup links you straight there.
Sharing is limited to 5 snapshots a minute and 30 an hour, which keeps one script from filling the server. Your comments stay on the page — wait the stated time and press Try again.
The snapshot couldn't be uploaded. Your comments are not lost — Try again keeps them. If it persists, save the page via File → Save as MHTML and send that instead.
Snapshots freeze the DOM and strip scripts, so anything that only exists while JavaScript is running — a carousel mid-animation, a lazily loaded image below the fold — is captured as it was at that moment. Scroll the whole page before sharing to give lazy content a chance to load.
Pins anchor to elements, not coordinates. If the site itself changed since you commented, an
anchor may no longer exist; in a JSON export those comments come back as
found: false with the geometry last recorded for them.
Either it expired after 90 days, or it was deleted from the review history. There's no way to restore it — take a fresh snapshot.
Share links are unlisted, so a review reaches only the people you send it to. If you own a site, you can also browse the reviews left on it that their authors chose to share with you (the Visible to site owner checkbox): open /admin and sign in with Google.
Reviews get there a second way. Add the feedback widget to your site and visitors can send you reviews without installing anything. Those have no checkbox: everything sent through the widget is listed for the host it was sent from.
Your site decides who gets in, not us. Publish a file at /wft.json on the
domain, listing the Google account emails that may read its reviews:
{
"employees": [
"owner@example.com",
"designer@example.com"
]
}
It must answer over HTTPS at https://your-domain/wft.json (the
www. host works too), as plain JSON, without a redirect. Then type your domain
on the admin page — we fetch the file, check your email against it, and remember your choice
for next time.
Add or remove an address and access follows within a few minutes. There is nothing to approve on our side, and no seats to manage. Since only someone who can publish files on the domain can edit that list, controlling the domain is what proves the team — so keep the file under the same review as the rest of your site.
Without publishing your team's addresses. That file is public, which is a
poor place for a list of work emails. Two other keys say the same thing without them:
employee_hashes holds {"salt": "…", "sha256": ["…"]} — a salted
SHA-256 of each address instead of the address itself — and employee_domains
holds your Google Workspace domain, so anyone whose account that domain administers gets in
and the file never needs editing when the team changes (access then follows the Google
account, and a removal takes up to a day rather than minutes, since Google only tells us at
sign-in). Any combination of the three works; a person gets in if any of them matches.
Hashes keep your addresses out of scrapers and search indexes, but an address is short
enough to guess, so treat them as protection against bulk collection rather than as a
secret. The exact format and hash command are in
docs/wft-json.md.
Above the list, a Statistics card sums those reviews up: reviews and comments
in the last 7, 30 and 90 days, the ten most reviewed pages (one page even when its URLs differ
by www., query string or a trailing slash), replies in the last 30 days and how
many comments are resolved, and a bar per week of how many reviews came in. It counts only
reviews shared with the owner, so a private review never shows up in the numbers either.
It is read-only for now — the admin area lists and opens reviews, and cannot delete them. Deleting stays with whoever created a review in the extension (see Review history & deleting). Whoever sends a review through the widget has no way to delete it: it stays until it expires, unless they ask us to remove it.
Coming next on this page: trends — spotting when feedback volume changes — and recurring themes across reviews, plus assigning reviews inside a team and a notification when new feedback arrives.
Full setup reference, including a troubleshooting table: docs/wft-json.md.