Skip to main content
Once a batch passes the gate, ask Pi (via the keyword-research-planning skill) to add the accepted keywords to the Keywords dashboard, apply the intent and relevance labels, tag the cycle, and file the supporting research to each keyword’s notes. Tag clean accepts as Core and secondary bets as Fringe, all under the cycle-month tag (e.g. jul'26); park leftovers under a future-cycle tag rather than deleting them. Keep two kinds of metadata straight: fixed structured labels (the 2-D intent × relevance framework) versus freeform tags (your cohort convention). Next, roll the tagged inventory into the monthly plan.
One intent, one keyword, no self-competition. Tagging is where the §1.5 Intent & cannibalization discipline gets recorded. The 2-D framework (intent × relevance) decides what survives and how it’s labelled.

​
Two kinds of metadata (don’t conflate them)

The dashboard has structured labels (fixed fields) and freeform tags (whatever you name them): Two systems run side by side. The freeform tags are the cycle and pillar convention you apply by hand: Core, Fringe, and Alternative are the pillar tags, sitting alongside the cycle-month tag and a source tag like from-sales. The app doesn’t enforce them, so keep the convention consistent month to month so the monthly report (2.2.4) stays comparable. The structured labels are the 2-D framework: seven intent labels (multi-select) and four relevance labels (single-select). Watch the overlap. “Alternative” lives in both systems. It’s a pillar tag here, and it’s also a value in the structured labels, both an intent label and a relevance label. Same word, two jobs: as a tag it groups a keyword into the Alternative pillar; as a label it marks a keyword’s intent or how relevant it is to what you sell.

​
Steps

  1. Load the ACCEPTs from 2.2.2 into the Keywords dashboard (bulk add / import, or ask Pi to add them directly).
  2. Apply the intent × relevance labels (the 2-D framework) and a priority.
  3. Tag the cycle: clean-accepts as Core, secondary bets as Fringe, all under the cycle-month tag (e.g. jul'26).
  4. File the supporting research to each keyword’s notes, so the “why it survived” travels with it.
  5. Park the leftovers under a future-cycle tag rather than deleting them.
  6. Sanity-check the keyword content planner view: no page/blog already generated for these, and no two keywords so similar they’d produce the same page.
❓ [needs Raymond: confirm the “keyword content planner” name]. A content-planning view exists in the dashboard (verified: ContentPlanningTable); confirm the user-facing label. Add to gap-register.md.

​
Real prompts

Tag the clean accepts and file the research:
Pi adds the keywords, applies labels/tags, writes the research into notes, and parks the rest. Add a keyword you supply by hand mid-session:
See the cluster structure before you commit page targets:
🎥 Video: Organize & file keywords within Synscribe. Loading, tagging, and filing in the dashboard.
Previous: 2.2.2 Evaluate + SERP-cliff a batch · Next: 2.2.4 Build the monthly look-ahead report · Theory: Part 1 §1.5 Intent & cannibalization · The rigorous cycle version: 3.4 Organise keywords for a cycle