Website Proofing for WordPress: Pin Comments on Live Bricks Pages
Website proofing is the review stage where clients mark up a near-final site and approve it before launch. The cleanest way to do it on WordPress is to let reviewers pin comments directly onto the live page — on the actual elements — rather than proof from PDFs, screenshots or a separate app. Designers have proofed print and PDFs this way for years; on the web, proofing the live page is faster because the comment sits exactly where the change is needed.
Here’s how website proofing works and how to run it on a Bricks site.
What is website proofing?
Proofing is the final check before something ships: the client (and your team) review the work, mark exactly what needs changing, and then formally approve it. For websites that means:
- Reviewing the real, rendered page — not a flat mockup or a screenshot.
- Leaving precise, located comments (“this button”, “this spacing”) instead of vague notes.
- Ending with a clear approval so launch isn’t ambiguous.
Print proofing has always been precise and signed-off. Web feedback often isn’t — which is why proofing tools exist.
Why proof on the live page (not screenshots or PDFs)
Proofing from exported screenshots or a PDF re-introduces the exact problem proofing is meant to solve: the comment is detached from the element. The reviewer writes “the third card”, you go find the third card, and you hope you matched it. Proofing the live page keeps each comment pinned to the real element, on the device it was viewed on, with the page state intact. Less interpretation, fewer missed changes.
How to proof a WordPress site built with Bricks
With a Bricks-native proofing tool like Reviso, the flow is:
- Share the page for proofing. Generate a review link — no client login, so reviewers just open it.
- Reviewers pin their markups. They click any element and leave a comment; a screenshot and page context attach automatically. Comments are threaded for back-and-forth.
- You action markups inside the builder. Every pin appears inside the Bricks builder, so you resolve proofing notes where you actually edit.
- Approve to close the proof. When the page passes, the client approves it and you get a timestamped PDF sign-off — your record that the proof was accepted. (More on client sign-off here.)
Because it runs on your own WordPress install, the proofing data stays on your site rather than a third-party cloud.
Proofing vs general feedback
Feedback can happen any time; proofing is the structured, sign-off-bound stage near launch. The tooling overlaps, but proofing specifically needs the approval/record step. The approach above covers both: pinned comments for the markup, and a timestamped approval to close the proof.
FAQ
What is a website proofing tool?
A website proofing tool lets clients and teams review a live web page, mark up exactly what needs changing by pinning comments to elements, and formally approve it before launch. Reviso does this natively for the Bricks builder.
How do I proof a WordPress website with a client?
Share a no-login review link to the live page, have the client pin comments on the elements they want changed, action those inside the builder, and capture an explicit approval. Reviso provides the link, the pinned comments, and a timestamped PDF sign-off.
Can I proof a website without sending PDFs or screenshots?
Yes — proof the live page directly. Pinning comments onto the real, rendered page keeps each note attached to the element, which is more accurate than marking up exported screenshots or PDFs.
Does website proofing include client approval?
It should — approval is what separates proofing from casual feedback. Reviso records a timestamped PDF approval certificate when the client signs off a page.
Proof your next Bricks build the easy way — try the Reviso demo → or install the free plugin.