You captured the homepage, marked the hero, and wrote "this doesn't land." Two days later the copywriter replies asking which line, which audience, and what "land" means. Nothing got rewritten. The problem is not your judgment. It is that the review told the writer a feeling instead of a target.
A positioning audit works when the person reading it can start typing new copy from what you sent. That means each captured section carries the claim being made, why it fails, and enough of the surrounding page that the writer sees what the claim is competing with. Here are three practices that get you there, and what breaks when you skip them.
Capture the claim and its neighbors, not the section in isolation
A hero headline does not stand alone. It is read against the subhead below it, the button next to it, and the image behind it. If you crop tight to just the headline, the copywriter loses the context that decides whether the headline is doing its job or the subhead is quietly carrying the whole message.
So frame the still to include the headline, the subhead, and the primary call to action together. Drop a numbered pin on each element you are going to talk about: pin 1 on the headline, pin 2 on the subhead, pin 3 on the button. Then your comment can say "pin 1 promises speed, pin 2 promises savings, and they are pulling in two directions" and the writer sees exactly what you mean. Because pins are baked into the exported image, the reference survives even when the writer reads the PDF later without the live page open.
The failure mode: you send a crop of one headline with "weak." The writer rewrites the headline in a vacuum, hits publish, and now the new headline contradicts a subhead nobody looked at. Positioning is a system. Capture it as one.
State the claim, then the objection, in that order
The most useful thing you can hand a copywriter is not your rewrite. It is the gap between what the page claims and what a real visitor would push back with. Write the claim in the page's own words, then the objection a skeptical buyer would raise.
For a hero that says "The fastest way to build reports," your comment might read: "Claim: fastest. Objection: fastest compared to what, and who is 'you' here, an analyst or a founder? No proof of fast anywhere above the fold." That gives the writer a target and a constraint. They can rewrite toward a claim they can actually back up, instead of guessing what bothered you.
This is the same discipline as running a positioning audit that ends in something actionable: you are separating the observation from the fix so the person who owns the fix keeps their judgment. Dictating these notes is faster than typing them, and reads more like how you would explain it out loud, which suits a copywriter's ear. Dictation runs on the browser's built-in speech recognition in Chrome and Edge; on Firefox you type instead.
The failure mode: you leave a comment that is only your rewrite. "Change it to 'Reports in five minutes.'" Now the writer either takes it verbatim, in which case why hire a writer, or ignores it, because they do not know what problem your line was solving. Give them the problem, not the answer.
Group proof separately from promise, and mark what is missing
Proof sections (logos, testimonials, stats, case study links) are a different job from the hero. The hero makes a claim. Proof earns it. When you review them in the same breath, feedback blurs. Capture the proof band as its own item and ask one question of it: does this proof support the specific claim the hero made?
Often the answer is that the proof is generic and the claim is specific, or the reverse. A hero promising speed backed by testimonials about friendly support is a mismatch a copywriter can fix in an afternoon, but only if you name it. Use an item for what is present and, just as usefully, a free-floating note item with no screenshot for what is absent: "No pricing signal anywhere above the fold" or "Nothing tells me who this is not for." Absence has no pixels to pin, so give it its own line.
The failure mode: you review only what is on the page and never flag the hole. The writer polishes existing sections and the page still fails to convert, because the missing proof was never the visible problem. What is not there shapes positioning as much as what is.
Send one link the writer opens without an account
Do the whole audit in a browser tab. No install, no extension, no login on the reviewer's side. When you publish, you get a short review link plus a clean read-only page, and the copywriter opens it on any device, comments on individual items, and works down the list. You can also export the whole thing to a PDF or Word doc if the writer prefers to mark it up offline. There is no account step for them to stall on, which is the same reason it works well for feedback that skips onboarding the other person to a tool.
You can run unlimited audits free, no credit card, and the tool asks for your email only when a review is ready so it can send you the link. Reviews you make stay editable for 7 days, then go read-only for you while the shared link keeps working for everyone you sent it to. If you audit pages regularly and want them to stay editable past that window, Pro is $5 a month and reopens any read-only review instantly.
Open a tab, capture the hero and mark the claim, and write the objection next to it. The writer opens the link and starts rewriting.