Not a screenshot. Not a PDF export of a screenshot. HopBack loads the actual website, staging password and all, and your client comments on it by clicking the thing they mean. The pin sticks to that element, however the page moves.
A screenshot is one width, one scroll position, one moment. The client marks up the hero and misses that the menu breaks on their phone. They ask why the button "near the top" does not work, and nobody knows which button. Then the site changes and the screenshot is out of date before the email is answered.
Reviewing the live site fixes all of that in one go. The client sees what their customers will see. The pin lands on the element itself. And when you push a fix, they refresh.
Live, staging or a password-protected build. HopBack loads it inside the review with the page fully working.
Your client opens it in any browser. No account, no extension, nothing added to the site.
A numbered carrot pin drops on the exact element. The comment lands in your sidebar the moment it is posted.
Comment mode for pinning, Browse mode for clicking links and navigating. Pins stay where they were left on every page.
A multi-page review keeps its pins as your client moves from the homepage to the contact page and back. Page navigation is fast, and each page's comments are grouped in the sidebar.
Switch the review between desktop, tablet and mobile widths without leaving the page. Responsive bugs get pinned at the width they happen, so "it looks weird on my phone" turns into a pin at 390 pixels.
Add the staging password when you create the HopBack. The site loads normally for your client and they never see the password. Nothing is installed on the site, reviews are never indexed, and HopBack strips your client's analytics and chat widgets from the reviewed page so a review does not show up as traffic.
Many agencies present round one as a flat PNG or PDF concept and add the staging link in round two. HopBack lets both live under the same link, so the client's feedback history follows the project from concept to build.
This is the one that matters most on a live site. HopBack anchors each pin to the element it was placed on, not to a spot on the screen. Add a paragraph above the fold, resize the window, load the page on a different day, and the pin is still on the button it was about. Some feedback tools still annotate a screenshot instead of the page, and several that do pin the element lock each pin to one screen size. HopBack's pins stay on the element at every width.
No. Paste the URL and HopBack loads the site inside the review. No plugin, no script, no browser extension for you or your client.
Yes. If the site has a URL, HopBack can load it. Password-protected staging sites work too.
Yes. Browse mode lets them navigate normally. Comment mode turns clicks into carrot pins. They can switch between the two at any time.
No. Pins are anchored to the element, not to a position on the screen, so they stay put when copy is added, the window is resized, the layout shifts or you switch to a different device width.
Pins stay on the element they were placed on. When you start a new round for the updated site, unresolved comments carry forward and the client can compare rounds side by side.
No. A multi-page review covers as many pages of the site as your client visits.