Skip to main content
Ask Pi (via keyword-research-planning) to read the tagged keyword inventory and produce the month’s plan: which keywords to build, in what order, and why. Order it BOFU-first and winnable-first, surfacing the softest-cliff, highest-intent keywords as the first wave, plus quick wins already ranking pos ~10–30 and deferred keywords now due. The report is written to Pi memory under /reports/ and surfaces as a section of the third-week monthly review. It only works because the cycle was tagged first.
Order the month BOFU-first, winnable-first. The report should surface the cliff-softest, highest-intent keywords as the first wave. See Part 1 §1.3 BOFU-first and the signal hierarchy (volume is last).
keyword-research-planning reads the inventory (labels, tags, priorities, SERP positions, and rank changes over time), so the report can also flag quick wins (already ranking pos ~10-30, where a dedicated page pushes to page one) and deferred keywords that are now due.

​
What the report should answer

  • What’s tagged for this cycle, grouped into clusters (head term to long-tail supporters)?
  • What’s the first wave (softest cliff, highest intent, or already in striking distance)?
  • Any quick wins already ranking that just need a dedicated page?
  • Any keywords deferred from last cycle that are now due?
  • Anything blocked (product/feature not live yet) that stays parked?
The report is a forward-looking before/after positions report, and it lives as a standard section of the monthly review rather than as a standalone artifact. It shows every keyword’s position before and after (LLM queries can go in too) plus the plan for the coming cycle. It’s written to Pi memory under /reports/ and surfaces in the third-week monthly review. Per keyword, the report carries: priority, intent label, relevance label, source, optional parent/child clustering, annotations (the plan for the keyword and which blog or landing page it maps to this month), related landing pages with their pillar, related blog posts with their template, tags, and the month’s performance tracking. Inside the monthly review it sits among the standard sections: overall movement (GSC and PostHog), impact (conversions and SERP screenshots), the keyword report itself, what you did, what you learned, what else you can do, blockers, what’s planned next month (the output allocation, the forward-looking keyword report, and key actions), and action items to follow up on.

​
Steps

  1. Confirm the cycle is tagged and filed (from 2.2.3).
  2. Ask Pi to build the monthly look-ahead report off the tagged inventory.
  3. Review the clusters and the proposed first wave. Does it match your priorities for the cycle?
  4. Adjust ordering/priority, then use it as the month’s build queue.

​
Real prompt

build me the monthly look-ahead report for '[cycle-month]'. read the tagged inventory and give me:
- the clusters for this cycle (head term → the long-tail keywords that ladder up to it)
- the first wave to build — softest SERP cliff and highest intent first, BOFU before TOFU
- any quick wins already ranking pos 10–30 that just need a dedicated page
- any keywords deferred from last cycle that are now due
- anything blocked (product not live) that stays parked
then order it into a build plan for the month.
Pi reads the tagged keywords, clusters them, ranks the first wave by winnability, and returns a month plan you can execute against.
🎥 Video: Build the keyword report to plan the month.
Previous: 2.2.3 Organise, tag & file keywords · Theory: Part 1 §1.3 BOFU-first · The rigorous cycle version: 3.4 Organise keywords for a cycle