I handed my content marketing to agents. 6 months later organic traffic is 34x.

The underrated finding here is that the agents were never the failure point. Same pipeline, same agents, and the only change that moved the numbers was what you pointed them at.

That matches what we see operating agent systems for a living: the generation layer commoditizes fast, and the judgment layer - what to aim at, when to stop, what counts as good - is where the leverage stays. "Cover the top 10 and land at position 11" is exactly the kind of spec error a pipeline will happily execute a thousand times.

Also respect for publishing the 53% dead rate. Most people only post the hockey stick.

34x organic traffic solo? That's insane. The fact that you didn't write a single article yourself and still pulled this off shows how much the game has changed. Most people are still debating whether AI content works — you've got proof. What's your quality control step look like at 200 articles/day?

Really appreciate the transparency here. Real breakdowns and honest reflections are super valuable for the community.

This is the part most teams miss: "I've never done outreach and I've never run a link building campaign. Adding a blog was the whole intervention." But the blog isn't the intervention - the deletion discipline is. Most setups publish forever and accumulate a dead weight of pages that all share the wrong signals with Google. You're deleting 53% in April, then 35%, then 25% - that's the tuning loop that made the 34x work. Without deletion as a measurement-driven decision, volume just becomes noise that confuses the algorithm about what your site actually is.

The point about checking search intent before creating a page is really important. For smaller tools, targeting a very specific query can sometimes be more practical than competing for broad keywords. For example, someone searching for a way to combine names already has a clear intent, so a focused this resource can be a relevant solution. Do you think adding a search-intent check before publishing would reduce the number of pages that end up with zero impressions?

Nice

the deletion pipeline might be the most underrated part of this whole setup. everyone obsesses over publishing volume but the dead-to-live ratio is what actually matters for site health. curious whether the 28-day threshold was something you arrived at empirically or more of a gut call

Building on the retarget-queue point above - I think the fix is to stop treating it as a per-article decision and score it before it ever reaches you, using the variable you already proved in your own data. Only 11% of dead pages had an adjacent 100-2,000 keyword, and your best band is 50-100 searches at 68% top-10, so the agents can attach to every queued article the best adjacent keyword under roughly a 500-search ceiling plus the median position your existing pages hold in that band. Anything with no adjacent keyword under the ceiling never reaches your desk at all; it goes straight to the 56-day noindex path, which is where it was heading anyway. Then cluster what's left by topic so you're issuing twenty cluster verdicts a week instead of scrolling 2,418 URLs - you keep the judgement call, you just stop paying the per-item cost of it. The deletion loop is the genuinely underrated half of this write-up, by the way: the ratio of dead to live pages is the thing a spam classifier can actually measure, and most people copying agent pipelines only ever add. Two things I'd like to know: are the zero-impression articles concentrated in particular topics or spread evenly across the 23,000? And since ad revenue tracked clicks almost 1:1 through 34x, have you seen RPM soften as you push further down the tail, or does a 50-searches-a-month query monetise about as well as a 2,000 one?

The deletion piece is the one most people skip, and your numbers show why it matters. If you only ever add, dead pages dilute the signal. The 56-day noindex pipeline running automatically is the bit I'd steal first.

The thing about the retarget queue — 2,418 articles waiting for a decision — that's the constraint I'd focus on. Right now it's the only part of the operation that still scales with your time, which makes it the only real bottleneck left.

What's the typical search volume range for topics in the retarget queue? If most are just slightly off on keyword tier, a templated reclassification rule might clear it without adding human judgment to each one.

The volume-band table is the most useful thing I've read on this in a while. One data point from a much smaller site: our template pages sat at positions 26–52 for searches like "italian restaurant website design", and moving down in volume wouldn't have helped, because the top 10 were galleries and inspiration posts, not tools. People wanted ideas, not a builder. (Disclosure: I'm building Mythex, an AI app builder; that's our Search Console.)

So a question on the pipeline: before writing, does it check what kind of page ranks (articles vs product pages vs galleries)? Your 11% adjacent-keyword finding makes me wonder whether some of the 1,412 dead pages were a page-type mismatch rather than a size problem.

Your own 1.9 pages per person says more about the retarget queue than any keyword metric. An audience that never browses can't be walked around with internal links or another article, so the retarget that has a chance is aimed at the URL that already gets the click: take a query where you're sitting 11-20 and answer it on the page that's already ranking instead of spawning a new one. That also shrinks the 2,418, because the pages worth touching are the ones Search Console already shows one position away from a query with demand. I see the same shape in long-tail sessions: people arrive with exactly one question and leave the moment it's answered.

The scale is impressive, but the retarget queue sounds like a routing problem more than a writing problem.

I’d group the 2,418 pages using signals you already collect—topic cluster, keyword tier, article age, index status, first-query impressions, and SERP volatility. Review a small sample from each group, then give that group one route: target a reachable long-tail variant, consolidate into a stronger existing page, or retire it.

That keeps the final call human, while turning thousands of page-by-page decisions into a handful of repeatable policies. I’d also track whether each retargeted group earns impressions or clicks after 28–56 days, otherwise the queue will refill without teaching the system anything.

The deletion schedule is the part I want to steal. I am at the opposite end of the authority spectrum and it applies even harder there.

DA 3, ten referring domains all scrapers, four visits a month. Every page at zero impressions is actively diluting the crawl budget that might get one good page seen. You can afford a 1,601-page cull when thousands of others pull clicks. I would be cutting from maybe 40 pages, so the discipline has to start before publication.

Your April-to-June zero-impression drop, 53 to 25 percent, by moving the keyword tier down is the cleanest experiment I have seen on targeting versus quality. Same pipeline, same agents, same domain. Only variable is which queries you aimed at. That falsifies the objection that AI content is penalised, because the content did not change.

Does your 28-day retarget script check whether the page was crawled, or just whether it got impressions? Never fetched is a different problem from fetched-indexed-and-ignored.

The retarget queue is the interesting question, and there is a second axis you can sort it on that costs nothing to compute.

First split the 2,418 by impressions, because two different defects are sitting in one bucket. Zero impressions is a targeting miss and your existing tiering already fixes it. Impressions with zero clicks is a title and intent problem, and retargeting the keyword will not touch it.

Then sort the rest by whether the answer can be inlined. We measured this on two sites this month. One carried 87,400 Copilot citations over 90 days and zero sessions attributable to an AI source, because every top cited page was a review or a pricing comparison, which an answer engine reads out in full and the reader is finished. The pages that turned a citation into a visit were the ones whose value cannot be carried inside the answer: setup guides, live comparisons, anything with a tool or an input on the page.

So for 2,418 articles, rank by how inlineable the answer is and work the non-inlineable ones first. An inlineable page sitting at zero will still be at zero after you retarget it, because the click was never available to win. That also reads on your own numbers: 12.4 pages per person down to 1.9 is what one-answer-per-page looks like, and it is fine while ads are the monetisation, but it means every page has to earn its click on the way in rather than from the page next to it.

Caveat: two sites, neither publishing at your volume, so it is a lead and not a law.

The other thing your post surfaces and does not measure is the inbound. Link exchange requests from listed companies arriving daily, after years of none, is a channel you have opened and are not instrumenting. If you want a free read on the channels the blog is now earning attention on, contentmation.com/score runs a pass with no login. At your scale it will tell you nothing new about search, which is most of your traffic, so it is only worth the minute for the rest.

I'm testing And copy pasted my agent to see if it works. for my b2b

Two things stood out. First, "the tier you aim at decides the rank you get" is a cleaner way of saying what most SEOs learn the hard way: scaling output without tiering is just burning index budget. Your April to June pivot, from 53% zero-impression pages to actually ranking, is a great case study in that.

Second, the link exchange requests from listed companies feel like the real moat forming. The 34x traffic is the headline, but inbound interest from much bigger companies means the library is becoming a reference asset that compounds on its own. I'd track that inbound-request rate as its own KPI - it's a leading indicator that the content has crossed from "indexed" to "authoritative."

This is the measurement visibility problem at scale - you handed off the work but now have to measure what the system is actually doing. The 34x traffic number is powerful because it's observable, but most teams using agents for content never set up the instrumentation to catch what worked. Measuring agent outputs backwards from actual user behavior is the only way to know if you're running agents or they're running you.

The deletion system may be the most valuable part of this, but I’d keep a small control group before trusting the 28/56-day rules completely.

Leave perhaps 5–10% of zero-impression pages untouched for another 60 or 90 days, grouped by keyword tier and index status. Then you can see how many would have surfaced naturally versus how many remained dead.

Without that holdout, pruning and growth happen together, so it is difficult to separate the value of deletion from the improved keyword targeting. It would also tell you whether different tiers deserve different expiry windows.

The 2,418-page retarget queue is more interesting than the 34x traffic. How do you decide which pages deserve another target versus deletion?