YourText.Guru Score

The YourText.Guru Score node analyzes a piece of content against a YourText.Guru guide and returns its SEO (SOSEO) and over-optimization (DSEO) scores.

What does the YourText.Guru Score node do?

The YourText.Guru Score node calls the YourText.Guru guides/{guideId}/check endpoint to evaluate a piece of content against an existing guide. It returns the SEO score (SOSEO), the over-optimization score (DSEO), the target ranges recommended by YourText.Guru, and a per-term analysis of how well each guide term is covered in the text.

Common use cases:

• Auditing an article generated by an LLM before publishing it on a CMS.
• Iterating on a draft until SOSEO reaches the target range while DSEO stays low.
• Scoring several content variants in batch to pick the best version.

Quick setup

Configuration parameters

Configure how the node authenticates and what it scores.

Required fields

What does the node output?

The node returns a JSON string with the SOSEO and DSEO scores, the target ranges recommended by the guide, and a per-term breakdown.

How to use the output

1. Draw a connection from the Score output port to the next node.
2. In that node, create a variable name (for example, score_json).
3. Use a JSON Path Extractor or an LLM downstream to read fields like score, danger, or analyze.

Usage examples

Example 1: Score an LLM-generated article

Score an article produced by an LLM against an existing guide and route it to a follow-up node only when SOSEO is high enough.

Configuration:

• Guide ID = 123456
• Content = output of an upstream LLM node
• YourText.Guru Integration = your YourText.Guru account

Generated output:

{
  "score": 78,
  "danger": 12,
  "target_soseo_min": 70,
  "target_soseo_max": 85,
  "target_dseo_min": 0,
  "target_dseo_max": 25,
  "analyze": {
    "content strategy": 3,
    "audience": 2,
    "keyword research": 1
  }
}

Example 2: Iterate on a draft until the target range is reached

Use a Conditional node downstream to loop back to the LLM whenever score falls below target_soseo_min or danger exceeds target_dseo_max.

Configuration:

• Guide ID = 123456
• Content = the current draft
• Downstream Conditional reads score_json.score and score_json.danger and decides whether to regenerate.

This pattern lets you optimize content iteratively without manual review.

Common issues

YourText.Guru Score : Integration not configured

Cause: No YourText.Guru integration is selected on the node.

Solution: Open the node settings and pick a valid integration in the YourText.Guru Integration field, or create one from the Integrations page using your YourText.Guru API key.

YourText.Guru Score : No guide ID

Cause: The Guide ID input is empty.

Solution: Connect an upstream node that produces the guide ID (for example, the YourText.Guru Keywords node) or paste a valid guide ID.

YourText.Guru Score : No content

Cause: The Content input is empty.

Solution: Connect an upstream node that produces the text to score (LLM, Text Input, HTML to Markdown).

YourText.Guru Score : Not enough tokens on your Text Guru account

Cause: The YourText.Guru account linked to the integration has run out of credits (HTTP 550).

Solution: Top up your YourText.Guru account or switch to an integration with available credits.

YourText.Guru Score : Invalid metadata. Reconnect the YourText.Guru integration

Cause: The integration record exists but the API key is missing or no longer valid.

Solution: Open the Integrations page and reconnect the YourText.Guru integration with a fresh API key.

Best practices and pitfalls

How does it fit into a workflow?

YourText.Guru Score typically sits between a content-generating node and a decision or storage node.

graph LR
    Kw[YourText.Guru Keywords] --> LLM[LLM writes article]
    LLM --> Score[YourText.Guru Score]
    Score --> Cond[Conditional checks score]
    Cond --> Sheets[Sheets Writer]

Related nodes