---
name: content-seo-and-editorial
description: "Build evidence-led content briefs and improve existing pages for search intent. Use when the user requests seo content and editorial planning. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# SEO Content and Editorial Planning

Build evidence-led content briefs and improve existing pages for search intent.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Approved positioning
- Search demand evidence
- Existing page inventory
- Editorial constraints

## Methods

### Map search intent

Group queries by intent and compare the current pages serving each group. Identify content gaps and competing pages before proposing new URLs.

### Build an evidence-based brief

Separate verified product facts from editorial interpretation. Build a brief with the reader’s question, answer structure, supporting sources and relevant next action.

### Revise pages coherently

For a revision, preserve useful URLs and references; update titles, headings, internal links and copy coherently. Do not manufacture expertise, reviews or structured-data claims.

### Verify rendering and measurement

Check published rendering and links after an authorized update. Measure against a stated baseline and window without promising rankings or AI citation placement.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.