Web fiction runs on comments. A good one can make an author's day; a specific one can show them exactly what landed. Here is how to leave something better than “update pls.”
The foundation: read before you respond
The most common bad comment is the one that's responding to something the author already addressed. "I don't understand why the character did X" — when the next paragraph explains why. "This plot hole seems obvious" — when it's explained three chapters later. Read the full chapter before commenting. Read the comments that already exist — your question might have been answered. If you're a new reader catching up on a long-running serial, be aware that plot points you're commenting on in chapter 10 may have been discussed to exhaustion by chapter 50.
What makes a good comment
Be specific. "Great chapter!" is better than silence, but not by much. "The way you handled the confrontation in the workshop — the detail about her hands shaking while she kept her voice steady — that's the kind of body language writing that makes characters feel real" gives the author something to learn from. Engage with the story on its own terms. Comment on what the story is trying to do, not what you wish it were trying to do. Criticizing a cozy slice-of-life story for lacking action is like criticizing a romance for having too many feelings. It's not a critique of the execution — it's a preference mismatch.
Name what worked and why. Even if you loved the chapter, identifying the specific elements that worked helps the author understand their strengths. Was it the dialogue? The pacing? A particular character moment? The descriptive prose? Saying what worked is the difference between encouragement and useful feedback. If you're going to criticize, be constructive. "This chapter was boring" is not useful. "The pacing in this chapter felt slower than the last few — the council meeting scenes ran long, and I found myself skimming the procedural details" is actionable.
Platform-specific norms
On AO3: The culture is praise-forward. Unsolicited criticism is generally unwelcome unless the author explicitly asks for it. This isn't oversensitivity — it's a community norm developed in response to years of harassment campaigns against fanfiction writers. Err on the side of encouragement. If you can't say something nice, genuinely consider whether you need to say anything.
On Royal Road: The culture is more critical. Honest reviews with specific criticism are valued. A 3-star review that explains its reasoning is more useful to the community than a 5-star review that doesn't. That said, "this story sucks" is still worthless. Criticism needs substance. On SpaceBattles/SV: The culture is analytical. Pointing out logical inconsistencies, physics errors, or worldbuilding contradictions is normal and expected. This can feel aggressive to newcomers, but it's how the community maintains its standards. Engage substantively — "your spaceship's stated power output doesn't match its described capabilities, here's the math" — and avoid personal attacks.
On Wattpad: The inline comment system encourages short, reactive comments ("OMG," "THIS," "I'm crying"). These are fine for community energy but don't help authors improve. If you want to leave substantive feedback on Wattpad, consider chapter-end comments in addition to inline reactions.
Comments that aren't helpful
"Update soon!" The most common comment on web fiction. Authors know readers want updates. They're writing as fast as they can. This comment adds pressure without adding value. Backseat writing. "You should have made the character do X instead." The story isn't a committee project. Unless the author asked for suggestions, assume they have reasons for their creative decisions.
Spoilers without warnings. On platforms that support spoiler tags, use them. On platforms that don't, warn before spoiling. Not everyone reads at the same pace. Comments on the author, not the work. "You must be [diagnosis/identity] to write this" is invasive. Engage with the fiction, not the person who wrote it.
Why it matters
Comments tell authors that somebody was there and give the next reader a reason to join the conversation. Name the line, choice, joke, or reveal that got you. “I loved this” is kind; “I loved this because…” is a gift.
Now go use this knowledge irresponsibly. When the next search produces five irresistible WIPs on three different sites, drop the supported links into Storywatch so your excellent taste does not have to rely on browser archaeology.