In your stack
The least technical client you have can still leave exact feedback
WordPress clients are the least technical people you will ever ship to. Writhink hands them one URL that opens the site they already recognise, lets them click the thing that is wrong, and lets them type. Nothing gets installed on your end either — this works from outside wp-admin entirely.
No credit card. Your client doesn’t need an account.
01
The client you actually have
The restaurant owner. The office manager at a two-partner law firm. The school secretary who inherited the website from someone who left in 2019. These people are not going to install a tool, remember a password, or hunt for the comment button in an app they have never opened. They will photograph their own screen with a phone and email you the picture with the subject line "changes".
Every account you ask them to create is a place the review stops. The invitation lands in a spam folder. The password gets reset twice. They open it on a different laptop and cannot find the button. None of that is a failing on their part; it is friction you introduced in order to collect twenty sentences.
The review link takes all of it out. One URL, one question — what should we call you — and then the page they already know, with a pin wherever they click. On your side the same round arrives as structured data: which page, which element, what viewport width, what device class, and a screenshot of the exact spot.
02
What dropping the account actually removes
This matters more with this client base than with any other, so it is worth being specific about what disappears — and about the one thing it costs.
- No invitation email, so there is nothing to lose in a spam folder or forward to the wrong colleague.
- No password, so no reset request three days later at the exact hour you needed the sign-off.
- No email verification step, which is where non-technical reviewers stall most often.
- Nothing to install on any device, because it is a web page and behaves like one.
- It works the same on a phone, which is where a good half of these clients will do the whole review.
- The cost, so you can plan around it: identity is a display name plus a token in their browser. If they switch from laptop to phone they can still read and add comments, but the ones left on the laptop are no longer theirs to edit from the phone.
03
Elementor, Divi, Gutenberg, and where the pin lands
Your client comments on the rendered front end, the site as a visitor sees it. The pin anchors to the element in the browser, which in builder output is usually a text node sitting several wrappers deep inside generated class names. It is precise about what they were looking at and says nothing at all about which control in the builder changes it.
That gap is narrower than it sounds, because most WordPress client feedback is content rather than layout: this text is wrong, this is the old photo, this button should say Book a table, this section should not appear on mobile. The page URL, the screenshot and the words on screen put you in the right template within seconds.
Where the builder does matter is finding the string afterwards. Gutenberg keeps its blocks in the post content, so what your client pinned is where you would expect it to be. Divi's layout is shortcodes in the post content too. Elementor stores the page as JSON in post meta, which is why a search-and-replace across posts comes back empty for a heading that is sitting right there on the page — open it in the editor instead of hunting in the database.
For layout requests — move this column, tighten this spacing — you still open the builder and find the section yourself. What changed is that you are working from one line with a picture attached rather than from a photograph of a monitor.
04
Two WordPress setups a review link cannot reach
| Where the site is | What to do | Why |
|---|---|---|
| A local install — LocalWP, DDEV, MAMP, wp-env | Pin it yourself with the Chrome extension, or open a temporary tunnel | localhost is reachable by your machine and nothing else, so there is no URL to hand anyone. LocalWP's Live Link and ddev share both put a temporary public address in front of the site and a review link works against one of those, but the address dies when you stop the site — fine for a same-day round, not for a week of review. |
| Host staging behind HTTP basic auth, the default on several managed hosts | Lift the auth for the review window, or pin it yourself with the extension | A shared link arrives at the browser's password prompt and stops there. Your own browser is already through it, which is exactly why the extension can comment on pages a link cannot reach. The extension needs a Writhink account, so it is a route for you and your team rather than for the client. |
Worth deciding at the start of the project rather than on the afternoon you need sign-off: if the person commenting has to be an account-free client, they need a URL they can open.
05
Running a round with a non-technical client
- Step 1
Put the site somewhere they can open
A staging subdomain with no password is the smooth path. Keep whatever noindex rule you normally put on staging — nothing about the review changes that.
- Step 2
Add the pages that matter, not all of them
Home, services, contact, and one live example of each template. The pages are served through Writhink's proxy so pins attach to elements rather than to coordinates on an image.
- Step 3
Send the link with a single sentence
"Click the thing you want changed and type what you want." That is the entire training, and it is the reason this survives contact with clients who will not learn a tool.
- Step 4
Let it arrive however it arrives
They can pin, attach up to five files of 10 MB each — which is how you finally get the high-resolution logo — reply in a public thread, and edit or delete their own comments when they change their mind, which they will.
- Step 5
Turn twenty scattered lines into a work list
A round from this client base is mostly copy and content, in no order, with the same complaint made three times in different words. It comes back deduplicated, grouped by page and element, prioritised, each line carrying its screenshot, and the ones that were never clear enough marked unclear instead of interpreted for you.
06
After launch, the script tag
For a round of review, nothing touches the site at all. If you want feedback available permanently instead — the client spotting a typo six months after handover — there is the embeddable widget, which is one script tag.
Put it where you already put script tags: the theme footer through wp_footer, a code snippets plugin, or your builder's custom code field. Remove it the same way. There is nothing to install in wp-admin — no plugin, no Gutenberg block, no Elementor widget — and that is not a paywalled feature being held back, it simply does not exist.
It carries a Powered by Writhink badge.
Before you count on it
The embeddable widget carries a “Powered by Writhink” badge. The white-label add-on that removes it is announced but not purchasable during the beta, so today the badge stays.
Writhink is in open beta: everything described here is available and free, no credit card. Paid plans are announced but not purchasable yet. The one limit that applies today is five AI prompt generations a month per organization.
FAQ
Questions people actually ask
- Does it work with Elementor, Divi or the block editor?
- It works on the page those builders output, which is where your client is looking. Comments come back with the page URL, the element, the viewport width, the device class and a screenshot. Writhink has no awareness of the builder itself, so you make the change in the builder as usual — and with Elementor, remember the text lives in post meta rather than in the post content.
- Do I have to install anything on the client's WordPress?
- No. The review link works from outside the site: you paste the URL and the page is served through Writhink's proxy so comments can be pinned to elements. The widget's script tag is the only thing that ever touches the install, and adding it is entirely optional.
- Can the client comment from a phone?
- Yes, and plenty will. The link opens in a mobile browser and pins work there. The viewport width and device class are recorded with each comment, so a layout problem that only exists on a narrow screen is labelled as one. What is not recorded is which phone or which browser, so a bug specific to one handset still needs a conversation.
- The pages needing review sit behind a customer login — a membership area, a WooCommerce account page.
- Then a review link will not get your client there, and the extension route needs a Writhink account. That combination has no clean answer today. Review those pages yourself with the extension and send the client a summary, or build a test account view you are willing to make reachable.
- How does the feedback reach whoever implements it?
- Generate the prompt and paste it into ChatGPT, Claude Code or Cursor; export the list and work down it; or point an MCP-capable assistant at the Writhink MCP server so it reads the feedback itself, with your account's permissions and nothing beyond them.
Start
Send one link. Get feedback you can build from.
Your clients comment right on the page — no account, no screenshots, no voice notes. Writhink sorts the comments and writes the prompt for your AI.