How do I share a blog post with a client before it's published?

The simplest method is a Google Doc set to 'Anyone with the link can comment.' For a post already in WordPress, use the built-in Preview link or a plugin like Public Post Preview to generate a shareable URL that doesn't require a login. For clients who want to annotate the post as it will actually look, a proxy-based review link wraps the preview URL in an annotation layer — they see the rendered post and can click the exact element they mean.

Can my client comment on a Google Doc without a Google account?

Your client can view a Google Doc without an account, but leaving a comment requires signing in. If they're not logged in, they can suggest edits in Suggesting mode — but suggested edits and comments behave differently and can cause confusion in the revision history. For clients without Google accounts, a review link on the rendered post is easier: they open the URL and comment as a guest with no login required.

How do I get specific feedback on a blog post instead of vague comments?

The tool forces the specificity. When clients can click the exact sentence and leave a pinned note, they do — because clicking is easier than describing the location. Email replies produce 'the opening feels off.' An inline comment produces 'this first sentence doesn't tell me why I should care.' Alongside the right tool, ask two or three focused questions in your send message: 'Does the intro earn the read?' and 'Is the CTA obvious?' beat an open prompt every time.

How many revision rounds should I expect on a blog post?

One to two rounds when the brief is solid and the client can comment inline. Three or more usually signals a misaligned brief — the post was answering a question the client wasn't asking. A 15-minute call to align on audience, angle, and goal before you write cuts revision rounds more than any tool. Email-based feedback typically runs longer because each vague note requires at least one clarifying exchange before you know what to fix.

How do I collect blog post feedback from multiple stakeholders without losing track?

Send everyone the same link rather than separate files. Multiple people commenting on the same Google Doc — or the same review link — means all feedback is in one place, not scattered across four reply emails with different priorities. Assign comment resolution to yourself, not the stakeholders: you resolve each thread after you've addressed it, and the comment history stays as the record. Sending separate files produces version collisions when two reviewers flag the same paragraph differently.

What is the best tool for getting client feedback on a blog post?

Google Docs with Comment access is the right default when your client already uses Google. A proxy-based review link (like Drafty) is better when the client doesn't have a Google account, when you want them to see the post rendered in your CMS theme rather than as a plain document, or when the feedback needs to stay anchored to specific text through multiple revision rounds without re-sending files.

drafty

How to get feedback on a blog post

Quick answer

To get feedback on a blog post, share a version where your client can comment on the specific paragraph they mean — not reply to your email with 'the bit near the top.' Google Docs with Comment access is the standard method. A shared annotation link works better when your client doesn't have a Google account, or when the post is already in WordPress and you want them to see it rendered, not stripped into a plain document. Either way, ask two or three focused questions in the message you send — 'Does the intro earn the read?' and 'Is the call to action clear?' beat an open 'what do you think?' every time.

Step 1

Share a Google Doc with Comment access

Paste the blog post into a Google Doc, click Share, and set the permission to 'Anyone with the link can comment.' Your client opens it in a browser — no Google account needed to view, but they do need one to leave a comment. The most common mistake is sharing with Viewer access by accident: the client can't leave a note, so they copy a sentence into a reply email and you get feedback disconnected from the actual line. Double-check the permission before you send. One thing that catches most freelance content writers the first time: clients who aren't regular Google Docs users will rewrite the paragraph in a comment — 'Here's how I'd put it: [entire block]' — instead of saying what the underlying problem is. In your message, ask them explicitly to flag what isn't landing and why, not to redraft it. Their instinct is to fix it; your job is to understand the diagnosis.

Step 2

Share a WordPress preview link

If the post lives in WordPress, you can share a preview URL before it's published. In the post editor, click 'Preview' and copy the link from your browser — it shows the post in your theme, not as a plain document. Some WordPress setups require the reviewer to be logged in; if that's a problem, a plugin like Public Post Preview generates a shareable URL that works without a login. The client sees the post exactly as it will look live, which matters for checking that the images sit correctly and the headings read at the right weight. The downside: they can't leave comments directly in a WordPress preview, so they'll still reply by email. You end up back at 'the second paragraph after the first image' — which is exactly the kind of location-by-description that burns a full extra round.

Step 3

Walk through it live on a screen share

A 20-minute call where you read the post aloud and stop at each section beats five email rounds for posts that need real strategic buy-in — a thought leadership piece, a sensitive announcement, anything where the angle matters as much as the words. Share your screen, pull up the post, and read each section without pre-explaining what you were trying to do. Let the client form a first impression before you frame it. Ask 'does the first paragraph earn the read?' before you move on. Take notes in a second doc during the call, or let Zoom transcribe it, then send a bulleted action list after. The failure mode for live blog reviews is letting the client co-write sentences in real time on the call — you lose 40 minutes on an intro and leave without a clear sense of whether the overall angle is right. Keep the call diagnostic; revise after.

Step 4

Share a review link they annotate directly on the post

The most reliable method when the post is in a CMS and your client doesn't want to log into anything: paste the WordPress preview URL or any web-rendered version into a review tool. It wraps the page in an annotation layer and gives you a link the client can open in any browser. They click the exact paragraph, sentence, or heading they mean and leave a pinned note. You see every comment anchored to the specific spot, reply in a thread, and resolve it as you fix each one. No account, no install on their end. The practical difference from email: a client who would write 'the opener feels flat' in an email will instead click the first sentence and type 'this doesn't make me want to keep reading' — because clicking is easier than describing the location. That specificity is the one thing that consistently cuts the revision count.

The faster way

If your client keeps sending blog feedback as a list of impressions — 'tighten the intro', 'the third section is too long' — without pointing at anything specific, paste the post URL or the WordPress preview link into Drafty and send that link instead. They open it in any browser, click the exact sentence or paragraph they mean, and leave a note pinned right there. No account, no install. Every comment lands in one thread, anchored to the passage, and stays on the same link through every revision round. No re-sending files, no reconciling multiple annotated copies with version numbers in the filename.

Open a live demo

Questions

How do I share a blog post with a client before it's published?: The simplest method is a Google Doc set to 'Anyone with the link can comment.' For a post already in WordPress, use the built-in Preview link or a plugin like Public Post Preview to generate a shareable URL that doesn't require a login. For clients who want to annotate the post as it will actually look, a proxy-based review link wraps the preview URL in an annotation layer — they see the rendered post and can click the exact element they mean.
Can my client comment on a Google Doc without a Google account?: Your client can view a Google Doc without an account, but leaving a comment requires signing in. If they're not logged in, they can suggest edits in Suggesting mode — but suggested edits and comments behave differently and can cause confusion in the revision history. For clients without Google accounts, a review link on the rendered post is easier: they open the URL and comment as a guest with no login required.
How do I get specific feedback on a blog post instead of vague comments?: The tool forces the specificity. When clients can click the exact sentence and leave a pinned note, they do — because clicking is easier than describing the location. Email replies produce 'the opening feels off.' An inline comment produces 'this first sentence doesn't tell me why I should care.' Alongside the right tool, ask two or three focused questions in your send message: 'Does the intro earn the read?' and 'Is the CTA obvious?' beat an open prompt every time.
How many revision rounds should I expect on a blog post?: One to two rounds when the brief is solid and the client can comment inline. Three or more usually signals a misaligned brief — the post was answering a question the client wasn't asking. A 15-minute call to align on audience, angle, and goal before you write cuts revision rounds more than any tool. Email-based feedback typically runs longer because each vague note requires at least one clarifying exchange before you know what to fix.
How do I collect blog post feedback from multiple stakeholders without losing track?: Send everyone the same link rather than separate files. Multiple people commenting on the same Google Doc — or the same review link — means all feedback is in one place, not scattered across four reply emails with different priorities. Assign comment resolution to yourself, not the stakeholders: you resolve each thread after you've addressed it, and the comment history stays as the record. Sending separate files produces version collisions when two reviewers flag the same paragraph differently.
What is the best tool for getting client feedback on a blog post?: Google Docs with Comment access is the right default when your client already uses Google. A proxy-based review link (like Drafty) is better when the client doesn't have a Google account, when you want them to see the post rendered in your CMS theme rather than as a plain document, or when the feedback needs to stay anchored to specific text through multiple revision rounds without re-sending files.

Keep exploring

Get feedback on copy Annotate a PDF Design feedback tool Client feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo