The usual answer to "how do I get client feedback on a WordPress site" is a plugin. HopBack is the other answer. Paste the staging URL, add the password if there is one, and send the link. Your client clicks the thing they mean and types. No plugin on the site, no account for them, and a sign-off at the end.
A feedback plugin has to be installed on the client's site, kept up to date, and removed before launch. It does not work on a host that locks plugins down, or on a managed staging environment where you cannot install anything, or on a site you are reviewing but do not own yet. It adds its own script to every page, which is one more thing in the waterfall. And it stays with WordPress: the logo, the brochure and the launch video still go round by email.
HopBack loads the WordPress site at its URL inside the review. The site is not touched.
No plugin, no script, no extension. HopBack loads the page at its URL, so it works on any host, any theme and any page builder, including the ones that block third-party scripts.
WP Engine, Kinsta, Flywheel, SiteGround and the rest put staging behind a password. Add it when you create the review. The site loads normally for your client and they never see the password.
The client moves through the site inside the review and the pins stay on the element. Switch to the phone width and the responsive problems get pinned at the width they happen.
Set the rounds you quoted. The client sees "Round 2 of 3" on the review, unresolved comments carry forward, and round four is a conversation about scope rather than a surprise.
Finish review locks the feedback. Approve records a name and a time. When content arrives late or the brief moves, there is a record of what was agreed.
A pin has to be placed by a person looking at the page, so you get the client's own reaction to the specific thing, not a page of AI slop forwarded from an email. Shorter, clearer, and something you can act on the same afternoon.
Most WordPress projects start before there is a WordPress site: a logo, a brand board, a homepage concept as a PDF. Review those on the same link, and by the time the staging site exists the client already knows what to do.
Live, staging or a password-protected build. Add the password if there is one.
Two rounds, due Friday. HopBack sends the reminders.
The client opens it on any device, types a name, and starts clicking.
Push the changes to staging. The same link opens the updated site, with the unresolved comments carried forward.
The client hits Approve. The record stays with the project.
Most agencies land on Studio: reminders, Slack and Teams, video review and 30 active reviews. Start on Starter if it is just you. Annual plans get two months free.
No. Paste the URL and HopBack loads the site inside the review. Nothing is added to the site, and nothing needs removing before launch.
Yes. Add the password when you create the review. HopBack uses it to load the site; your client never sees it. Most managed hosts' staging environments work this way.
Yes. HopBack reviews the rendered page, so the builder does not matter. If the page loads in a browser, it loads in the review.
That is the case HopBack was built for. Because nothing is installed, the host's plugin policy does not apply.
Those put a plugin or a script on the WordPress site, which gives them deeper access to the page and ties them to it. HopBack stays outside the site and adds rounds, a locked record and reviews of non-WordPress work. Our comparisons:
Yes. The link opens in any browser, and the review has a phone width built in so responsive issues can be pinned where they happen.