Read three live Google Help Center pages, flag where they confuse real users, and propose tighter rewrites a content lead can ship.
We run the Google Help Center, which serves billions of support sessions a year across Search, Gmail, Drive, and Android. Pages accrete over time. A step gets added when a feature ships. A warning gets bolted on after a support spike. After a few years, some of our most-trafficked pages read like changelogs instead of answers.
We want a fresh outside read on three specific pages we'll assign at kickoff. The brief is narrow on purpose: tell us where a normal person gets lost, and propose a rewrite we could actually ship.
Deliverable: a short written audit covering all three pages, plus a rewritten version of one page of your choice. For each page, mark the specific sentences or steps that fail, say why (jargon, wrong order, missing context, buried answer), and suggest a fix. The full rewrite should match the voice of the existing Help Center — direct, second person, no marketing language.
What you get from us: the three URLs, our internal one-page voice guide, an anonymized sample of recent user feedback on each page, and a 20-minute async Loom from a UX writer on our team walking through how we think about a "good" Help page. You do not need to be a writer by training. You need to read carefully and notice when an instruction does not actually answer the question being asked.