Your visitors have nothing to install. They open the widget from your page, pin comments to what they are looking at and press Send to site owner. You read the result in your admin area, next to a copy of the page they saw.
This page runs the widget. Both controls below are the snippets from step 2, unchanged: open it with either one, click anything on the page to pin a comment, then press Send to site owner.
Put this tag on every page where you want feedback, before </body>:
<script type="module" src="https://website-feedback-tool.com/wft/embed.js"></script>
On its own it draws nothing: no button, no pins, no change to your layout. The widget appears only when something on the page asks for it, which is the next step.
<a href="#wft">Leave feedback</a>
The script opens the widget whenever the address ends in #wft, so this needs no
JavaScript of your own and suits a footer. It also means you can send someone straight to
https://your-site.example/pricing#wft. If a router on your site reads the hash,
it sees #wft too, and with a <base href> on the page the link
leads to that address instead of staying here. Use the button in either case.
<button type="button" onclick="WFT.open()">Leave feedback</button>
WFT.open() opens the widget from anything your code does: a button, a menu item,
a condition of your own. WFT.close() hides it, and whatever the visitor had
drafted is still there at the next opening.
window.WFT, the script leaves it alone and only
the #wft link opens the widget.onclick. Make the same
call from a script of your own, or use the link.Both are ordinary elements. Change the wording, move them and style them as you like; the widget cares only about the hash or the call.
Everything sent through the widget is stored as visible to the site owner, but it is listed for nobody until you prove the site is yours. Without this step the admin area will not let you in to your site.
/wft.json file on your domain that lists your team's Google
accounts.The site admin docs describe the file and the options for not publishing your colleagues' addresses. Each review opens at its own link, where your team can reply to a comment and mark it resolved. The widget shows the visitor no link to it, so a reply stays on the review and does not reach them.
script-src and connect-src must allow
https://website-feedback-tool.com, or the widget will not load or will fail
to send. With 'strict-dynamic' the host is ignored, so the tag needs your
nonce as well. style-src must allow inline styles, or the widget works
unstyled. require-trusted-types-for 'script' stops it from sending at
all, and the visitor is not told why..рф:
the admin area cannot claim it yet.
Under an ordinary ending such as .com, type a domain with
non-Latin letters in its xn-- form.staging.example.com needs its own publicly reachable
wft.json and appears as its own site in the admin area.
www.example.com and example.com count as one.