The Content Post-Mortem: Tracing a Flop Back to Its Brief

An article goes live in March. By August it sits on page three for its target keyword, collects a few dozen impressions a week for queries nobody planned, and has quietly become a line in a spreadsheet tab called “underperformers.” Someone suggests adding 400 words and an FAQ. Someone else suggests deleting it. Nobody suggests opening the brief.

That is where the answer usually is.

The guides that rank for underperforming content cover the same ground, and they cover it fine: pull pageviews and rankings from your analytics, sort the pieces that once worked from the pieces that never did, then decide what to keep. All of that treats the article as the thing that failed. Our view is that an article which never ranked was usually set up to miss before the writer typed a word, and a post-mortem that stops at the page fixes one URL while the same flaw ships again in next month's briefs.

Which articles get a post-mortem

Only the ones that never performed. A page that ranked for a year and then slid has a different problem (the search results moved, or a competitor published something better) and it needs a refresh brief, which starts from what the page already earned. The post-mortem is for the piece that was flat from week one.

Give it time first. Three months after publishing is a reasonable minimum for a new page on an established site, longer on a young domain, and judging a piece at week four mostly measures how quickly the crawler showed up. If you are reviewing dozens of pages at once, that is an audit, and how to run a content audit covers the inventory side. A post-mortem goes deep on one article, maybe two, and takes about an hour.

Pull three numbers and the query list

You need less data than the analytics tools will offer you. From Search Console: impressions, average position and clicks for the target keyword over the last 90 days. Then export every query the page has shown up for, sorted by impressions. Skip bounce rate and time on page for now. They tell you whether visitors liked the page, and the problem here is that hardly any visitors arrived.

The query list is the most useful document in the whole exercise, because it shows what Google decided your page was about, which is often a long way from what the brief said it was about.

Read the brief before you reread the article

Order matters here. If you reread the article first you will start editing it in your head, and every flaw you spot will feel like the writer's fault. Read the brief cold, as if a new hire wrote it, and then put it next to the query export and the current first page of results for the target keyword.

When the brief is missing

If nobody can find the brief, write that down as the first finding, because a team that cannot produce the document an article was commissioned from has a filing problem that will outlast this one page.

The ways a brief sets up a miss

A never-ranked article usually traces back to one of the failures below. They do not carry equal weight. Our bet is that the first one accounts for most misses on its own.

The intent was wrong. The brief asked for a guide and the results page wanted a list of tools, or it asked for a comparison when searchers wanted a definition and a template to download. You can see this in thirty seconds: look at the format of the top five results and compare it to the format the brief prescribed. If the query export is full of phrasings like “template” or “free” and your page has neither, the brief picked the wrong job. No amount of rewriting the prose fixes a format mismatch. The page needs a new brief, built after a proper SERP analysis.

The research described a results page that no longer exists. Briefs are snapshots. If the competitors listed in the brief have dropped off page one, or a forum thread and a video carousel now take up half the screen, the brief was accurate in January and stale by May. This one is hard to spot unless the brief recorded which URLs it studied, and a surprising number of briefs do not.

There was no angle. The brief summarized what the top results said and asked for the same thing, a little longer. The article delivered exactly that, competently, and Google already had ten of those. Look for a sentence in the brief that says what this page will do that the others do not. If you cannot find one, neither could the writer.

The brief was right and the article drifted. This happens, but less often than editors assume. Check it last, by reading the article against the brief's must-includes and its stated angle. If a late edit removed the one section that answered the query people were actually typing, that is a process gap between final edit and publish, and the pre-publish QA check against the brief exists for exactly that.

Write the verdict as a change to the template

A post-mortem that ends with “rewrite the article” has done half its job. The article gets a new brief, fine. The other half is a one-line change to the brief template or the review step so that the next forty briefs cannot fail the same way, and that line is what makes the hour worth spending.

Each failure maps to a specific change. Wrong intent means the template gets a required field for the dominant result format on page one, filled in by whoever looked at the results, with the date they looked. A stale snapshot means the brief has to list the URLs it studied and when, and anything older than about six weeks at assignment gets rechecked before a writer starts. A missing angle means the reviewer in your brief approval workflow sends back any brief whose angle field restates the keyword. Drift means the final QA pass reopens the brief.

Keep a running list of these verdicts somewhere the whole team reads, with the article, the failure, and the template change next to each other. After six or eight entries the pattern usually becomes embarrassing in a useful way. Our guess is that you will find one failure doing most of the damage, and it will not be the one you would have named on day one. The twelve fields of a good brief are a reasonable checklist for spotting which field keeps coming up empty.

What not to blame

Word count. A page that missed intent at 1,800 words will miss it at 2,600. The same goes for keyword density, a missing FAQ block or a meta description a few characters too long; worth fixing, and almost never the reason a page sat on page three for five months. We have shipped our share of those mechanical mistakes on this site (twenty titles over the length limit in a single September 2026 crawl) and the fix for them is a build check, which is a different conversation from why an article never found its readers.

Where a generator fits

We build a brief generator, so here is how ours helps with this, and where it stops. When you run a keyword through ContentBrief.io, the brief it returns includes a competitor analysis: the pages it read from the top results, each with its URL, title, approximate word count and key topics, plus a target word count set about ten percent above the competitors' average. Save that brief with the assignment. Months later, when the article stalls, it is the dated record of what page one looked like when the decision was made, which turns the stale-snapshot question from a guess into a comparison. Run the same keyword again and put the two competitor lists side by side.

What the tool cannot tell you is whether the angle was any good. That judgment was a person's call at assignment time, and the post-mortem is the moment that person finds out whether they called it right. Then they take what they learned into the next brief, using how to write a content brief as the starting point if the template needs rebuilding from scratch.