Live

SEO Memory

Maintain a project knowledge file for SEO content creation. Use when the user shares critical context about their project — product renames, new/removed features, service changes, subproduct launches, pricing updates, audience shifts, or any factual change that SEO content should reflect. Also triggers on "update seo memory", "remember this for content", "setup seo memory from sitemap", or when the user corrects a factual detail about their product/service. Even small updates matter — stale project facts in published content erode trust.

Workflow

1
Load memory
2
Determine if update is needed

Install

$npx skills add rankearly/rankearly-skills --skill seo-memory
Downloadseo-memory.zip

Extract the SKILL.md into your project's .claude/skills/ directory.

Allowed Tools

Skill

Load or maintain project context so content skills have accurate product, audience, and positioning information.

Memory lives in ./seo-memory/:

  • main-memory.md — topical map. Lists every topic with 1 primary + up to 2 secondary sources. Thin topics keep their details inline; rich topics have a one-line router stub pointing at a dedicated file.
  • {topic-slug}.md — full details for a rich topic, loaded on demand.
  • seo-urls.md — sitemap URL tracking, used during setup only.

Route

  • Setup from sitemap — user wants to build seo-memory from a new site. Follow references/setup.md.
  • Load — light — a topic is mentioned but not central to the task. Read main-memory.md and cite the topic's primary source. Do not open the topic's detail file.
  • Load — deep — a topic drives the current task. Read main-memory.md, then load seo-memory/{topic-slug}.md if the topic has been split out. If details are still inline in main-memory.md, that's enough.
  • Update — user shared business facts. (subagent) Follow references/update.md.
  • Organizemain-memory.md grew messy after a setup batch or bulk update. (subagent) Follow references/organize.md to merge duplicates and split rich topics into their own files.

If seo-memory/ is missing on any Load or Update route, ask the user whether to run Setup or create an empty main-memory.md from references/template.md.