Tracking website feedback in ClickUp or Notion: what works and what breaks
Plenty of agencies already run their projects in ClickUp or Notion, so client comments on a website end up there too, one task or database row per note. It's a sensible place to track the work. The trouble is what gets lost on the way in: where on the page the comment was, which version the client looked at, and whether they were on a phone. This guide looks at ClickUp website feedback and the Notion equivalent: what each tool offers today, where the gaps are, and how to connect a pinned-comment tool so each task keeps its context. ClickUp and Notion features below were checked on their own help pages on 18 November 2026.
Why agencies track website feedback in ClickUp or Notion
If your team already plans sprints, assigns work and reports to clients from ClickUp or Notion, a second place for feedback feels like overhead. So the project manager reads the client's email, makes one task per note, assigns it to a designer or developer, and the feedback joins the rest of the work. Status, due dates and who's doing what are all in one view, and nobody has to learn a new tool.
That part works well. ClickUp and Notion are good at tracking work. They aren't built for the step before it, which is capturing exactly what the client saw and where. That's where most of the back-and-forth comes from.
What gets lost when a comment becomes a task
A typical task reads "Make the button bigger, see client email" with a screenshot pasted in. The developer opens it two days later and has to work out the rest. These are the details that usually go missing:
| What the developer needs | What usually reaches the task |
|---|---|
| The exact element: which button, on which page | A description in words, or a cropped screenshot with no page address |
| The version the client reviewed | Nothing. The screenshot may be of last week's build, and the page has changed since |
| The device and screen size | Usually missing. "It looks broken" might only happen on the client's phone |
| The client's own words | The project manager's summary, which can drop the reason behind the request |
| The rest of the conversation | Split between the email thread, the task comments and a call nobody wrote up |
| Whether the client agreed it's fixed | The task is closed in ClickUp or Notion, but the client never saw that |
Screenshots are the weakest link. They are accurate the moment they're taken and go out of date with the next deploy, so a task can hold a picture of a problem that's already fixed, or a picture that no longer matches the page at all. And the copying itself takes time: on a 40-comment round, someone spends an hour turning emails into tasks before any work starts.
What ClickUp offers for website feedback
ClickUp has three features that agencies use for feedback. None of them lets a client click on a live website.
- Proofing. You can add, assign and resolve comments on PNG, GIF, JPEG and WEBP images, videos and PDFs attached to a task. It doesn't work on attachments stored in cloud storage, and it's used by people in your Workspace, guests included. It suits design mockups and exported PDFs well. (ClickUp Help: Proofing)
- The Chrome extension. It adds the site you're looking at to a task in one click, and captures screenshots you can draw and write on before posting them into a task. This is how many teams log their own QA notes, but it's an extension your team installs, not something you'd ask a client to set up. (ClickUp Chrome extension)
- Forms. A Form view turns each submission into a task in a List, with answers going into task fields. An upload question can attach files up to 25 MB each, so clients can send their own screenshots. (ClickUp Help: Forms and Form view)
What's missing is commenting on the website itself. A request to annotate live sites from a URL has been on ClickUp's feedback board since October 2023, with about 30 votes and no official reply on the page (feature request). A separate request for proofing links that clients can use without an account dates from September 2020 and has around 60 votes, also with no official reply (feature request).
What Notion offers for website feedback
Notion's tools for this are simpler, and they are really about gathering and tracking rather than commenting on a page.
- Forms. Every question maps to a property in a database, and responses land in a table view called Responses that you can filter, sort and chart. You can open a form to anyone on the web with the link, and every plan can create forms. Conditional logic needs a Business or Enterprise plan. (Notion Help: Forms)
- Web Clipper. A browser extension for Chrome and Safari, plus the share sheet on phones, that saves a web page into a page or database. Clipping into a database adds a URL property with the page address. You can't set other properties while clipping; you add tags and comments afterwards. (Notion Help: Web Clipper)
- Comments on Notion pages. Useful for discussing a task once it exists, but they sit on the Notion page, not on the website.
So a Notion form can ask "Which page?" and "What should change?", but the reviewer has to describe the spot in words, and the form doesn't record their device or what the page looked like when they filled it in.
ClickUp and Notion side by side
| ClickUp | Notion | |
|---|---|---|
| Comment on a live website | No | No |
| Comment on images and PDFs | Yes, with Proofing | Comments on the Notion page, not on a spot in the file |
| Marked-up screenshots | Yes, with the Chrome extension | No built-in tool |
| Form that creates items | Yes, each submission becomes a task | Yes, each response becomes a database row |
| Clients without an account | Can fill in a form; Proofing needs Workspace access | Can fill in a form open to anyone with the link |
| Accepts incoming webhooks | Yes, the Webhook received trigger, Business plan and up | Not directly; use the API, Zapier or Make |
| Import from CSV | Yes, the Spreadsheet importer | Yes, Merge with CSV on a database |
From each tool's help pages, checked 18 November 2026. Sources are linked in the sections above and below.
How to connect a pinned-comment tool so tasks keep their context
The setup that holds up is to split the two jobs. Clients comment on the page in a website feedback tool, where each comment stays pinned to the element with the device and version attached. ClickUp or Notion tracks the work, and every task links back to the comment so the developer can see it in place. Here are the realistic ways to join them, from simplest to most automated. HTMLAnnotate is the example, but the same routes apply to most feedback tools without a native integration.
1. Paste the review link into the task
Make one task per comment, or one task per page with a checklist, and paste the review link into it. It's manual, but the developer opens the link and sees the comment on the actual page, at the right screen size, instead of a stale screenshot. For a round of ten or fifteen comments this is often enough.
2. Export a CSV and import it
HTMLAnnotate exports comments as a CSV on every plan. ClickUp's Spreadsheet importer takes CSV files and maps columns to task fields (ClickUp Help: Spreadsheet importer). In Notion, the database menu has a Merge with CSV option that adds rows to an existing database. It adds new rows rather than updating ones you imported before, so import each round once (guide to Notion CSV import). This suits teams that triage a whole round at the end, and it pairs well with sorting the comments with AI first.
3. Send webhook alerts through Zapier or Make
HTMLAnnotate's Pro and Team plans include Slack and webhook alerts. A webhook alert can go to an automation service, which then creates the task:
- Zapier. The Webhooks by Zapier Catch Hook trigger receives the alert. Then ClickUp's Create Task action makes a task (Zapier: webhooks to ClickUp tasks), or Notion's Create Data Source Item action adds a database row (Zapier: webhooks and Notion). Zapier lists Webhooks by Zapier as a premium app, so check whether your Zapier plan includes it.
- Make. The Custom webhook trigger pairs with ClickUp's Create a Task module (Make: ClickUp) or Notion's Create a Data Source Item module (Make: Notion).
- ClickUp directly. ClickUp has a Webhook received trigger that starts an Automation when an outside app sends a request to a unique URL. It's on the Business plan and above, and an admin has to switch it on first (ClickUp Help: Trigger an Automation from an external app). Check which actions it can run with the incoming data before you rely on it for task creation; Zapier or Make is the more predictable route.
- Notion directly. Notion's API can create a page in a database (Notion API: create a page), but that means writing a small script or service. Notion's own webhook actions go the other way: they send data out of Notion when a database changes, on paid plans (Notion Help: Webhook actions).
Whichever route you pick, send one test comment first and look at what arrives. Map the comment text, the page and the review link into the task, and set the assignee and status in the automation so nobody has to sort new tasks by hand.
4. Route Slack alerts to whoever makes tasks
If you'd rather a person decides what becomes a task, send HTMLAnnotate's Slack alerts to a project channel. The project manager reads each comment as it arrives and creates the task from there. It's slower than a webhook, but it filters out "agreed" replies and questions that don't need a task.
A few rules that keep the two in step
- Keep the conversation in one place. Reply to the client on the comment, not in the task. Use the task for internal notes, estimates and who's doing it. If both places hold half the discussion, nobody has the full picture.
- Link every task back to the review. The link is what saves the developer from guessing. A task without it is back to "see client email".
- Close the loop with the client. When the task is done, resolve the comment too, so the client sees that it was handled. Closing a ClickUp task or ticking a Notion checkbox tells your team, not the client.
- One task list per round. Group tasks by round or version, so fixes for round one don't mix with new requests from round two. Our post on website revision rounds covers how to define a round.
- Agree who turns comments into tasks. One person triages, merges duplicates and flags anything out of scope. The agency client feedback process post has a full setup.
Where HTMLAnnotate fits, and where it doesn't
HTMLAnnotate covers the step ClickUp and Notion skip. You paste a staging or live link, or upload an HTML file or PDF, and share the review link. Clients click any element to comment, with no account or extension. Each comment saves a small screenshot of what the reviewer saw, and, for you only, their browser, device, screen and window size and any page errors. Desktop, tablet and phone comments are kept apart, and new versions go on the same link with earlier versions keeping their comments. That's the location, version and device a task usually loses.
Be clear about the limits before you set it up:
- There is no native ClickUp or Notion integration. Connecting them means a review link, a CSV import, or webhook alerts passed through Zapier, Make or your own code.
- Webhook and Slack alerts are on Pro ($15 a month) and Team ($40 a month for 5 people). CSV export is on every plan, including Free.
- It doesn't review standalone images. For static mockups that already live in ClickUp, Proofing does that job well.
- Pages behind a browser password box or a sign-in form can't be imported, so use a staging or preview link that opens without one.
If you'd rather not build any automation at all, tools with native integrations exist. Marker.io's ClickUp integration keeps statuses, fields and comments in sync both ways, and its Notion integration syncs status from Notion back to Marker.io (ClickUp, Notion). BugHerd connects to ClickUp on its Premium plan and above (BugHerd Help). Both collect feedback through a script or browser extension and cost more; our BugHerd vs Marker.io comparison has the prices. For the review itself, from the request email to the checklist, see the website feedback guide, and plans are on the pricing page.
Questions
Can clients annotate a live website in ClickUp?
Not as of 18 November 2026. ClickUp's Proofing works on images, videos and PDFs attached to tasks. A request for annotating live websites has been open on ClickUp's feedback board since October 2023, with no official reply on the page. You can attach a screenshot of the page and proof that instead, or collect comments in a website feedback tool and link them to the task.
Can Notion collect website feedback?
Notion Forms can collect feedback from anyone on the web with the link, and each response becomes a row in a database. The form can't point at a spot on a page, so reviewers have to describe where the problem is in words. Notion's Web Clipper saves a web page into a database with its address, which helps you gather references but isn't a way for clients to comment.
Does HTMLAnnotate integrate with ClickUp or Notion?
There is no native integration. HTMLAnnotate has CSV export on every plan, and Slack and webhook alerts on Pro and Team. You can pass webhook alerts into ClickUp or Notion through Zapier or Make, import a CSV export, or paste the review link into each task.
Do clients need a ClickUp account to use Proofing?
Proofing works for people inside your ClickUp Workspace, including guests you invite. A request for proofing links that clients can use without an account has been on ClickUp's feedback board since September 2020, and there is no official reply on the page.
Which website feedback tools connect to ClickUp natively?
Marker.io has a ClickUp integration with two-way sync of statuses, fields and comments, and a Notion integration with status sync. BugHerd connects to ClickUp on its Premium plan and above. Both need a script or browser extension to collect feedback, and both cost more than HTMLAnnotate.
Collect client comments on the page itself, with the device and version attached, then link each task back to the review. Reviewers don't need an account.
Start a free review