⟨ BLOGPLAYBOOKSSEO & CONTENT

Steal their content calendar → Asana

Reverse-engineer a competitor's publishing cadence and topics, find the gaps you can win, and load a month of counter-content tasks into Asana.

PlaybookWeb ResearchKeyword IntelligenceAsanaRUN BY THE CONTENT AGENT →

The problem this solves

Your competitor's content strategy is published in plain sight - every post, its topic, its timing, and eventually its rankings. Almost nobody reads it systematically. Teams glance at a rival blog twice a year, feel vaguely behind, and go back to their own calendar. The intelligence that would actually change decisions - what cadence they sustain, which topic clusters they are investing in, where their coverage is thin or aging - stays locked in a feed nobody has time to study.

Reading it properly is real work: crawling months of posts, mapping topics to the queries they target, checking what actually ranks, and separating their wins from their filler. Then comes the harder question of what you should do about it - which gaps are winnable, which of their strongholds to avoid, and what a month of counter-programming looks like. That analysis rarely survives contact with a busy week, so the competitor's roadmap keeps compounding unchallenged.

How the mission runs

  1. Crawl their publishing history. Web Research pulls the competitor's blog feed and recent archive: what they published, when, and how the topics cluster. Their cadence and editorial priorities emerge from the data - which themes get weekly investment and which were tried once and abandoned.
  2. Map topics to rankings. Keyword Intelligence connects their posts to the queries they target and how those bets are paying off. This separates the strategy that works from the content that merely exists, so your counter-plan responds to their wins rather than their volume.
  3. Find the winnable gaps. The agent identifies where demand exists and their coverage is thin, outdated, or absent - and where your existing authority gives you a realistic shot. Each gap comes with the evidence: the queries, the demand, and the state of their competing page if one exists.
  4. Draft the counter-calendar. The gaps become a month of planned content: titles, target queries, angles, and a suggested publishing order that puts the highest-leverage pieces first. It is a plan built to exploit specific weaknesses rather than to mirror their output.
  5. Load the tasks into Asana. Every planned piece lands in Asana as a task carrying its target query, angle, and the competitive evidence behind it. Your writers pick up tasks with the strategic context attached, and the month runs as normal project work.

The prompt

This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.

⟨ THE MISSION PROMPT · PASTE AND RUN ⟩

Reverse-engineer competitor.com's publishing cadence and topics from their blog feed and rankings, find the gaps we can win, and load a month of counter-content tasks into Asana.

What comes back

A month of counter-content loaded into Asana: one task per planned piece, each with a title, target query, angle, and the competitive reasoning that justifies it - plus a summary of the competitor's cadence, topic clusters, and where their strategy is strong versus exposed. Your team starts Monday with a plan grounded in their actual behavior instead of assumptions about it.

Make it yours

  • Run it against three competitors at once and build the calendar from the gaps none of them cover - the spaces the whole category is ignoring.
  • Focus on their decay: target only topics where their once-ranking posts have aged, so your fresh coverage attacks weakened positions.
  • Repeat monthly and track deltas: each run reports what they shipped since last time and how the gap map moved.

Frequently asked questions

Is this just copying their calendar?

It is the opposite move. The mission maps what they cover so your month targets what they missed, under-served, or let decay. Where they are strong, the plan generally routes around rather than head-on, unless your authority makes a direct challenge winnable.

Does the analysis use anything private?

No. Everything comes from public surfaces: their published posts, feeds, and the rankings visible to anyone. The advantage comes from reading that public record systematically and turning it into tasks, which is work most teams never make time for.

What if my team wants to change the plan?

The plan arrives as ordinary Asana tasks your team owns completely. Reorder, reassign, delete, or rewrite angles as editorial judgment dictates. Each task carries its evidence, so overruling a recommendation is an informed call, and the next run learns from what you kept.

Go deeper

⟨ RUN IT INSTEAD OF READING IT ⟩

This mission runs minutes after signup.

Open a workspace, paste the prompt, and the Content Agent carries it end to end on your plan's monthly credits - evidence attached.

⟨ RELATED PLAYBOOKS ⟩