SEO Keyword Gap Briefs: The Right Eight Briefs, With Writers Who Have Room for Them

A keyword queue that goes stale between the analysis and the brief

The gap analysis leaves a queue in Google Sheets: keywords where competitors rank and the company does not. The gap policy decides which become briefs. A keyword needs enough search volume, a difficulty under the ceiling, an intent that matches a page the company would publish, and no existing page already targeting it. Each one that passes goes to a writer, inside the capacity the managing editor sets per writer.

The queue is only right on the day Semrush was read. Difficulty scores refresh and a keyword slips past the ceiling. A writer's month fills up and their allocation has to move. A page published last week in the Notion content database now targets a keyword still sitting in someone's queue, and a new article would end up competing with the company's own page.

Who works in the room

The content team opens a Kylon room for each brief cycle. Ada is the default agent and owns the keyword decisions, so a question about why a keyword was dropped goes to Ada. Ryan allocates and files briefs, and Myco checks the editor's sheets against the plan and picks up the capacity changes writers post in Slack. Ada reads Semrush through a grant the SEO lead approved for the room. When Ada's decisions are approved, it hands the surviving keywords to Ryan in the thread, each with its metrics and the reason it passed, and Ryan leads from allocation onward.

From keyword queue to filed brief

Before any keyword is allocated, the room guidelines require a check of the content database for published pages. The gap policy and writer capacities sit in the cycle folder.

Capacity drops and pages go live

Changes arrive in no particular order, and each one can undo part of the last. When a writer's capacity drops from five briefs to two for the month, Ryan moves their three lowest-priority keywords to writers with room, and the allocation shows the new owner on each. When a page is published in the content database, Ada excludes every queued keyword it now targets, and Ryan recounts each writer's load before anything new is allocated.

The order matters because the cycle ends with a fixed number: eight briefs. After every change, Ryan rebuilds the brief list from the current allocation, not the original plan. A keyword that dropped on difficulty does not get a brief anyway, and no writer is left holding an assignment that no longer exists.

What the checks catch

• A keyword already targeted by a published page in the content database
• A keyword that passed last week but sits past the difficulty ceiling after the refresh
• A writer still holding keywords after their capacity dropped
• A ninth brief, filed for a keyword that has since been excluded

What stays with people

• Setting the gap policy and approving each keyword decision
• Setting writer capacity and approving every allocation
• Reviewing each brief before a writer starts on it
• Signing off the cycle close-out

Integrations in this workflow

Kylon is not an SEO suite or a content management system, and it does not replace either. It sits across Semrush, Notion and the team's sheets and holds the coordination from keyword to brief.

• Google Drive
• Google Sheets
• Notion
• Semrush
• Slack

• Semrush supplies search volume, keyword difficulty and the competitors ranking for each term
• Notion holds the content database of published pages and receives each filed brief
• Google Sheets holds the keyword queue and the editor's allocation sheet
• Google Drive keeps the gap policy, the writer capacities and each change notice
• Slack is where writers post capacity changes and questions about a brief

Where to start

Choose one content area and one brief cycle. Connect Semrush and the Notion content database to the room. The rule for the room guidelines is short: no keyword is allocated until the content database has been checked for a page that already targets it.

“The cycle files eight briefs. Which eight can change four times before Friday.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.