Skip to content

usage.md

Latest commit

 

History

History
51 lines (37 loc) · 2.1 KB

usage.md

File metadata and controls

51 lines (37 loc) · 2.1 KB

Usage

This repo can be used in two ways:

  1. Skill-first
  2. Prompt-first

Skill-First Examples

  • Use the seo-audit skill to audit https://example.com and create a report plus action plan.
  • Use the technical-seo skill to check https://example.com for crawl, rendering, and CWV issues.
  • Use the keyword-research skill to research "warehouse management software" for the US market.
  • Use the content-brief skill to brief a comparison page for product A vs product B.
  • Use the local-seo skill to review a 25-location service business site.
  • Use the seo-reporting skill to package the latest findings for a stakeholder update.

Prompt-First Examples

  • Follow .codex/prompts/seo-audit.md for https://example.com.
  • Follow .codex/prompts/keyword-research.md for "best payroll software for agencies".
  • Follow .codex/prompts/content-brief.md for a local-service landing page.

Suggested Workflow

  1. Start with seo-audit for a broad diagnosis.
  2. Use technical-seo when the audit surfaces implementation issues.
  3. Use keyword-research to define target demand and content opportunities.
  4. Use content-brief to turn priorities into execution-ready pages.
  5. Use local-seo when the business depends on geographic visibility.
  6. Use seo-reporting to summarize the work for stakeholders.

Deliverable Conventions

  • Full audits: FULL-AUDIT-REPORT.md, ACTION-PLAN.md
  • Technical reviews: TECHNICAL-SEO-REPORT.md
  • Keyword research: KEYWORD-RESEARCH.md
  • Content briefs: CONTENT-BRIEF-<slug>.md
  • Local reviews: LOCAL-SEO-ANALYSIS-<domain>.md
  • Reporting: SEO-REPORT.md, optionally EXECUTIVE-SUMMARY.md

Good Prompts

  • Be explicit about URL, geography, and business type if you know them.
  • Tell Codex whether you want a full audit, a focused diagnosis, or a stakeholder-ready report.
  • Mention whether data is available from analytics, rankings, CRM, or reviews.

Avoid

  • asking for precise traffic or rank estimates without data access
  • mixing multiple workflows in one request without saying which is primary
  • assuming a local SEO framing when the site may not be a local business