YepAPI/skills

Keyword Research Workflow

Dedicated keyword research workflow — discover, evaluate, and prioritize keywords using YepAPI endpoints.

Endpoints Used

Endpoint	Cost	Purpose
POST /v1/seo/keywords/ideas	$0.03	Keyword suggestions from a seed keyword
POST /v1/seo/keywords/related	$0.03	Related keywords for a seed keyword
POST /v1/seo/keywords	$0.15	Bulk keyword metrics (volume, CPC, difficulty, intent)
POST /v1/seo/keyword-gap	$0.04	Keyword gap analysis between two domains

Workflow

Step 1: Generate Keyword Ideas

Start with a seed keyword. Run POST /v1/seo/keywords/ideas.

{
  "keyword": "project management",
  "location": "us"
}

Returns: keyword suggestions based on the seed — content angles and long-tail variations.

Step 2: Find Related Keywords

Expand with POST /v1/seo/keywords/related.

{
  "keyword": "project management",
  "location": "us"
}

Returns: semantically related terms — broader and narrower variations.

Step 3: Evaluate Keyword Metrics

Run POST /v1/seo/keywords with all candidate keywords.

{
  "keywords": ["project management software", "project management tools", "best project management app"],
  "location": "us"
}

Returns: search volume, CPC, keyword difficulty, search intent (informational/commercial/transactional), 12-month trends.

Step 4: Keyword Gap Analysis (Optional)

If the user has a domain and a competitor, run POST /v1/seo/keyword-gap.

{
  "domain": "example.com",
  "competitor": "competitor.com"
}

Returns: keywords the competitor ranks for that the user doesn't — untapped opportunities.

Step 5: Prioritize Keywords

Present a prioritized keyword list sorted by opportunity score:

• High opportunity — high volume + low difficulty
• Group by intent — informational, navigational, commercial, transactional
• Flag seasonal keywords — note 12-month patterns from trends data

Rules

• Start broad with ideas, then narrow with metrics
• Group keywords by search intent: informational, navigational, commercial, transactional
• Flag seasonal keywords using trends data (12-month pattern)
• Batch keyword metrics calls — up to 100 keywords per request ($0.15) is cheaper than individual lookups

Error Handling

• NO_CREDITS (402) — Tell the user to add credits at https://yepapi.com/dashboard
• UPSTREAM_ERROR (502) — Retry once; if it fails again, skip that step and note it
• VALIDATION_ERROR (400) — Check keyword format; keywords must be non-empty strings
• RATE_LIMITED (429) — Wait and retry; respect the Retry-After header