Beyond Me-Too: Writing Content That Isn't Just an Echo

Say you're writing a piece on remote onboarding. The generic version opens with a stat about turnover, lists five best practices (assign a buddy, front-load documentation, schedule regular check-ins, set 30-60-90 day goals, gather feedback), and closes by reminding readers that culture matters. Every sentence is true. Every sentence also appears, in some form, on the ten pages that already rank for the term. A reader who finishes it knows exactly as much as they did before they clicked.

Now take the same topic and add one real constraint: a three-person team onboarding a new hire across four time zones, with no overlap in working hours for the first two days. Suddenly the advice has to change. "Schedule regular check-ins" stops being usable, because there's no shared hour to schedule them in. The piece has to solve for asynchronous handoffs, written context instead of live walkthroughs, and a first week built around documents the new hire can act on alone. That's a piece with a spine. The first one is an echo. Avoiding me too content is the difference between them, and it's rarely about better writing. It's about whether the draft carries something the field didn't already have.

The problem with averaged content

Here's what makes averaged content so easy to produce, and so easy to miss.

Averaged content is what you get when the cheapest way to write something is to read what already ranks and recombine it. An average of existing inputs can never exceed them. When a whole field writes this way, everyone converges on the same subtopics, the same stock examples, and conclusions hedged down to nothing memorable.

Google's own guidance for creating helpful content lists a specific set of self-assessment questions, including whether the content provides "substantial value when compared to other pages in search results" and whether a reader would feel they'd had a satisfying experience after reading it. Those aren't rhetorical questions. They're the exact ones Google's guidance tells site owners to ask before publishing, and averaged content fails the first one by definition, because it's built by reading those other pages rather than adding to them. Google, Search Central guidance

The trap is dangerous because averaged content passes every check you'd normally run. It's accurate. It's readable. It covers the subtopics a competitor covered, in the order a competitor covered them.

The only thing it fails is the one check that actually matters: whether it adds anything. That failure stays invisible for as long as you're only comparing your draft against the field instead of asking what it contributes beyond it. This is the same territory Google's E-E-A-T guidance points at when it asks whether content reflects firsthand experience rather than a rewrite of other people's experience. An averaged draft, by construction, has none.

There's a related risk sitting underneath this one. Google has said its systems can demote sections of a site that read as "independent or starkly different" from the site's main theme, which cuts the other way too. Content that reads as interchangeable with everyone else's doesn't just fail to stand out. It can read as filler even to the site that published it. Search Engine Land, 2024

Combine that with a search landscape now surfacing "Highly Cited" badges for original reporting, and the incentive to add something real gets sharper, not softer. Google, Search blog

A weak draft beside a strong one

The onboarding example is worth writing out in full, because the difference is easier to feel than to describe in the abstract. This one came from a live client brief, a three-person operations team hiring a remote contractor across a four-hour overlap window at best, where the standard advice simply didn't work.

Remote onboarding works best when you set clear expectations from day one. Assign a buddy to help the new hire navigate company culture, schedule regular check-ins during the first few weeks, and make sure documentation is easy to find. Culture matters just as much as process, so don't overlook the human side of onboarding.

Nothing there is wrong. It's also indistinguishable from a dozen other paragraphs written on the same topic this year, because none of the advice depends on anything specific to this hire, this team, or this constraint. Swap "remote onboarding" for "hybrid onboarding" and the paragraph barely needs editing.

With a four-hour overlap window at best, live check-ins are a luxury, not a default. Build the first week around a single written brief the new hire can act on without you: what the team owns, who to ask about what, and three tasks with enough context to start solo. Save the live time for one call, at the end of week one, to unblock anything the brief didn't cover.

This version came out of an actual scheduling conflict, not a summary of other people's advice. The client's operations lead had already tried the "regular check-ins" approach with a previous hire and watched the first week stall because nobody was awake at the same time to unblock questions. That detail, drawn straight from the SME conversation, is what makes the second paragraph impossible to lift and reuse for a different team without rewriting most of it.

A separate engagement, a fifteen-person support team hiring across three offices, hit a different version of the same problem. The generic advice there was "gather feedback in week one," which sounds fine until you notice the new hire in that case had no manager in their own time zone to give it to. The fix wasn't a check-in cadence. It was a named async reviewer, someone in the new hire's own working hours, with authority to approve the first week's tasks without waiting on the manager to wake up. Two different constraints, two pieces of advice that neither generic draft would have produced, because neither constraint shows up in a summary of what other pages already say.

That's where differentiation actually lives: firsthand experience, original data, a synthesis nobody else assembled, a defensible opinion, or specificity in a spot where the field has settled for vague. Adding one of those doesn't mean reinventing the topic. It means finding the true thing the averaged version was missing and putting it on the page. Content research and differentiation covers where those inputs come from, and finding content gaps covers how to locate the openings worth filling before you start writing.

Four checks that expose the echo

A draft that's genuinely differentiated survives four practical tests, each catching the echo from a different angle. These map onto the ordinary stages of a content workflow: the first belongs in editing, the second and third in the outline or brief, the fourth in research, before a word gets written.

1. The subtraction test. Go through the draft and delete every sentence a reader could get from the existing top results: restated consensus, stock examples, anything true but available everywhere. In the weak onboarding paragraph above, that deletes almost the whole thing, "set clear expectations," "assign a buddy," "culture matters," none of it survives. In the strong version, the four-hour overlap window and the single written brief survive, because nobody else's draft has that constraint. If what's left contains a real number, a specific detail, or a claim that's actually yours, the piece has a spine. If almost nothing survives, no amount of polishing the prose fixes it, because rewording a deleted sentence just reproduces it under new phrasing. The only fix is adding a real input.

2. The byline-swap test. Replace your name with a competitor's and reread the piece. If nothing feels wrong, no claim only you could make, no detail that betrays firsthand knowledge, then the piece could belong to anyone. Applied to the onboarding example: the weak version could carry any consultant's byline. The strong version carries the specific texture of a specific engagement, which makes it harder to imagine coming from someone who wasn't in that scheduling conversation.

3. The so-what's-new test. Read as your most informed reader, the one already past the basics, and check each section for a genuine "I didn't know that." An onboarding specialist reading "assign a buddy" learns nothing. The same reader hitting "save the live time for one call, at the end of week one" gets a decision they can actually copy. Sections that pass are where the piece earns its length; sections that fail are context at best.

4. The copyability test. Could a competitor reproduce this exact piece from the same sources you used? If yes, your raw material was the same as everyone else's, and the averaging trap already has you. CMI's 2025 B2B benchmarks found that content teams lean hardest on case studies, original research, and data visualizations precisely because those formats are harder to copy from a shared set of sources than a generic explainer is. CMI, 2025 B2B benchmarks The same report found 47% of B2B marketers cite repurposing as a real challenge, a fair proxy for how much time gets spent recombining the same base material into slightly different shapes.

All four checks depend on having something to check against besides the competition's pages. In practice that means a brief that records the client's actual constraint before writing starts, an SME interview transcript you can quote from directly, or first-party data from the engagement itself, a support ticket count, a scheduling log, an actual conversion number. Skip that collection step and there's nothing for the subtraction test to find, because the draft was never going to contain anything the top ten didn't already have.

Uncopyable material is also, increasingly, the material AI answer engines choose to cite. HubSpot reported a 56% jump in citations from AI answer engines after building content around distinct, source-worthy claims rather than generic coverage, a case worth reading alongside generative engine optimization if AI visibility is part of the goal. HubSpot, 2025 AEO case study