How to Collect Client Feedback on a Website Using a URL Capture

A practical review process for agencies that need specific comments, clear revisions, and a decision on the right version.

By Charlie Boudreau8 minute read

Key Takeaways

  • A URL capture gives clients a fixed view of a website page for visual comments.
  • Tell reviewers which page, version, and decisions need their attention.
  • Ask for a separate pin and clear outcome for each requested change.
  • Capture the updated page again after revisions. A previous capture does not update itself.
  • Test interactive behavior on the actual site and request explicit approval after changes.
Two agency colleagues reviewing a captured website page with numbered feedback pins
Editorial illustration of a website review. The screen is not a Jottrly product screenshot.

What Is the Fastest Way to Collect Clear Website Feedback?

Quick answer: Capture the page from its URL, tell the client what to review, and ask them to pin each requested change to the relevant area. Give one person responsibility for the final decision. After revisions, capture the updated page and ask for an explicit approval.

A long email saying “the homepage feels off” makes the team guess which section, version, and outcome the client means. A pinned note such as “Replace this hero button label with ‘Request an Estimate’ so visitors know what happens next” gives the team a location and a specific action. For more examples, see how to give design feedback your team can use.

1. Capture the Page You Want Reviewed

Start with one page and one review goal. In Jottrly, enter the website URL to capture the page for visual review. Name the work so everyone can identify it, such as “Homepage, round 1, November 5.” If you are reviewing several pages, identify each page separately rather than asking the client to report everything in one thread.

Important distinction: The capture is a snapshot of the page at that moment. Reviewers can pin comments to the captured result, but the capture is not an interactive website. Open the actual site to test forms, links, menus, animation, and mobile behavior.

Check the captured result before sending it. A login wall, cookie prompt, unfinished loading state, or blocked staging URL can leave you with the wrong page. If the page cannot be captured, use a suitable screenshot or file upload and note what it represents.

2. Send a Brief That Sets the Review Boundary

Clients give better feedback when they know what decision they are making. Share the review link with a short brief that identifies the page, the version, the deadline, and who will consolidate feedback. Separate visual and copy decisions from technical testing.

Example Client Review Brief

“Please review the captured homepage by Thursday. Focus on the headline, service order, and primary call to action. Pin each requested change to the relevant area and explain what you want visitors to understand or do. Alex will combine stakeholder comments and confirm the final decision. We will test forms and navigation separately on the live site.”

This boundary also helps distinguish a correction from a new request. If extra pages or features enter the conversation, use the approach in managing design revisions without scope creep.

3. Turn Reactions Into Actionable Pins

Ask reviewers to mark the exact area that prompted the comment. One pin should describe one issue. A useful comment states the problem, the requested outcome, and why it matters.

  • Vague: “This section needs work.”
  • Useful: “The pricing cards make the annual amount look like a monthly charge. Label the billing period beside each price.”
  • Vague: “Can we make this pop?”
  • Useful: “The primary button blends into the surrounding cards. Make the next action visually distinct.”

When two stakeholders disagree, reply in the same thread and ask the decision owner to choose a direction. Jottrly’s threaded comments keep the discussion with its annotation. Our list of common client feedback problems covers conflicting requests in more detail.

Put Website Feedback in One Place

Capture a page from its URL, mark the areas that need attention, and keep each discussion attached to the work.

Start for Free

4. Revise, Recapture, and Check the Changes

Work through the notes and resolve individual comments as the requested changes are addressed. Then capture the updated website page so the client reviews what is there now, not the old snapshot. Label the new capture with the page and round. Keep a short change summary beside the review link.

Example: “Round 2: updated the hero button label, reordered the three services, and clarified the pricing period. Please check these changes and flag any remaining issues by Friday.” This gives the client a focused second pass.

Also verify the actual site at relevant screen sizes. A screenshot can show the appearance of one state; it cannot prove a menu opens, a form submits, or the layout works at every width.

5. Get a Clear Decision on the Current Version

A resolved pin means one issue was handled. It does not mean the page is approved. Ask the designated decision maker to review the revised work and confirm the page’s status. Jottrly separates comment resolution from file review status, such as In review, Changes requested, or Approved.

If you need a more formal sequence of review rounds and sign-off, use the client design approval process. Keep the final decision tied to the version that was actually reviewed.

Website Feedback Checklist

  • Capture the correct URL and inspect the result.
  • Name the page and review round.
  • State the decisions needed and set a deadline.
  • Ask for one specific request per pinned comment.
  • Assign a decision owner for conflicting feedback.
  • Test interactive behavior on the actual site.
  • Recapture after changes and summarize what changed.
  • Request explicit approval of the current version.

Start Your Next Website Review

Capture a page from its URL, mark the areas that need attention, and keep each discussion attached to the work.

Start for Free

Frequently Asked Questions

Can I collect feedback on a website without installing a widget?

Yes. With Jottrly, enter a public website URL to capture a page for review. Reviewers comment on that captured page. This does not install a widget on the website or let reviewers interact with the live page inside the capture.

Does the captured page update when the website changes?

No. A capture represents the page at the time it was taken. Capture the updated page again after changes and make clear which version the client should review.

Can clients test menus, forms, or animations in the capture?

A captured page is a visual snapshot. Test menus, forms, animations, and responsive behavior on the actual website separately. Record any findings in the appropriate review.

What if the website is password protected?

Confirm that the URL can be reached by the capture process before planning a review. If access fails, use an approved screenshot or file upload and avoid sharing credentials in review comments.

How should I ask clients for useful website feedback?

State the review goal and deadline, identify the decision maker, and ask clients to pin each requested change to the relevant part of the captured page. Ask for the desired outcome and priority, not only a vague reaction.

Does resolving all comments mean the website is approved?

No. Resolving a comment closes an individual request. Ask the decision maker to review the updated work and record an explicit approval decision separately.