Validate SEO Slug
seo.validate_slug
Overview
Check whether one path segment already matches the generated ASCII slug policy We never open a connection, resolve DNS, or follow a redirect. The answer is a structured fact or policy result you can store. A successful call costs 1 execution credit.
A generate-only skill cannot tell you the CMS mutated the slug; this checks the string you actually stored.
Reliability
seo.validate_slug is stable for identical input. Identical input always produces identical JSON. SEO_INPUT_REQUIRED means a required field is missing or has the wrong shape, so send the published object rather than a guessed map; retrying unchanged will not help. SEO_INPUT_TOO_LARGE means a value exceeds its ceiling, so trim it. SEO_HTML_MALFORMED means the HTML could not be parsed under the offline HTML contract, so fix the markup. SEO_XML_MALFORMED means the XML is not well-formed, so correct it. SEO_XML_DOCTYPE_NOT_ALLOWED means the XML includes a DOCTYPE declaration, so strip the DOCTYPE and resend; we refuse DTDs rather than expanding entities. SEO_JSONLD_MALFORMED means a JSON-LD block is not usable JSON, so correct it. SEO_PROFILE_UNKNOWN means the named profile is not bundled, so send one of the published profile ids. SEO_TOO_MANY_RECORDS means a list exceeded its ceiling, so split the batch. SEO_GRAPH_LIMIT_EXCEEDED means the graph exceeded its node or edge ceiling, so shrink it. SEO_INVALID_URL means a URL string is not a usable RFC 3986 URI, so send an absolute URI. SEO_OBSERVATION_INCOMPLETE means required observation coverage is missing, so add the missing evidence. SEO_INPUT_CONFLICT means two fields that cannot be used together were both supplied, so drop one. Retrying an unchanged request will not help.
Context footprint
Returns a compact structured record. A successful call costs 1 execution credit.
When to use it
When you already have a candidate slug string and need to know whether it matches the generated ASCII form and length rules.
When you still need to create the slug from a title — use seo.generate_slug — or you are validating a full URL.
Scope
Non-goals
- Does not fetch a URL, resolve DNS, or run a browser
- Does not predict ranking, choose a winner, or claim live index status
- Does not generate a slug or fetch the path
Properties
Capabilities
Cost & billing
Flat rate per invocation
File handling
How we handle your data
What this means
This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.
Squillify guarantees
- Runs inside Squillify
- This skill runs inside Squillify.
- Payloads are not sent to an external service by this skill.
- Squillify does not permanently store submitted payloads.
- Telemetry records metadata only, not submitted content.
- Submitted payloads are not used for training.
- Submitted payloads are not reviewed by humans.
- This skill does not target sensitive data.
- The response may contain submitted or transformed content.
Your responsibility
Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
| slug | string | Yes | Required. Candidate path segment to check against the generated ASCII form. |
| separator | string | No | Single character expected between words. Omit it and we use a hyphen. |
| maxLength | integer | No | Policy maximum length. Omit it and we use 80. |
Output schema
| Field | Type | Required | Description |
|---|---|---|---|
| valid | boolean | Yes | True when the slug already equals the generated candidate and is within length. |
| normalizedCandidate | string | Yes | What generate would produce from the same slug text. |
| profile | string | Yes | Effective slug profile id. |
| measurements | object | Yes | Closed map with length, maxLength, and separator for the candidate that was checked. |
| findings | array | Yes | Policy findings for form or length. Empty when valid is true. |
API contract
POST /v1/executecurl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"seo.validate_slug","input":{"slug":"cafe-resume-2026"}}'import { Squillify } from "@squillify/sdk";
const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });
const { output } = await sq.execute("seo.validate_slug", {"slug":"cafe-resume-2026"});Errors
| Code | HTTP | Retryable | Description |
|---|---|---|---|
| VALIDATION_ERROR | 400 | No | The request payload failed schema validation. |
| UNAUTHORIZED | 401 | No | Missing or invalid API key. |
| SKILL_NOT_ACCESSIBLE | 403 | No | The API key is not granted access to this skill. |
| SKILL_NOT_AVAILABLE_FOR_PLAN | 403 | No | This skill is not included in your current plan. |
| PLAN_ELIGIBILITY_UNAVAILABLE | 503 | Yes | Plan eligibility could not be decided. Retry after backoff. |
| SKILL_NOT_FOUND | 404 | No | The requested skill or version does not exist. |
| TENANT_RATE_LIMITED | 429 | Yes | Request rate limit exceeded. Retry after backoff. |
| QUOTA_EXCEEDED | 429 | Yes | Plan quota exhausted. Retryable once the quota period resets. |
| EXECUTION_TIMEOUT | 504 | Yes | Execution exceeded the allowed time budget. |
| SEO_INPUT_REQUIRED | 400 | No | The request payload failed this skill's input validation. |
| SEO_INPUT_TOO_LARGE | 429 | No | A size, quota, rate, or time limit was exceeded. |
Other limits
| Limit | Value |
|---|---|
| Recommended inline bytes | 32 KiB |
Limitations
- Does not fetch a URL, resolve DNS, or run a browser
- Does not predict ranking, choose a winner, or claim live index status
- Does not generate a slug or fetch the path
- Creating the slug from a title
- Fetching the published path
How to call
POST /v1/execute (requires authentication)
{
"skillKey": "seo.validate_slug",
"input": {
"slug": "cafe-resume-2026"
}
}Examples
Primary business path
{
"slug": "cafe-resume-2026"
}{
"normalizedCandidate": "cafe-resume-2026",
"valid": true,
"profile": "seo.slug.default@1",
"measurements": {
"length": 16,
"maxLength": 80,
"separator": "-"
},
"findings": []
}Boundary or option path
{
"slug": "NOT A SLUG"
}{
"normalizedCandidate": "not-a-slug",
"valid": false,
"profile": "seo.slug.default@1",
"measurements": {
"length": 10,
"maxLength": 80,
"separator": "-"
},
"findings": [
{
"certainty": "POLICY_RESULT",
"evidence": [
{
"actual": "NOT A SLUG",
"artifactId": "slug",
"path": "/slug"
}
],
"message": "Slug is not in the generated ASCII form for this profile.",
"profile": {
"checksumSha256": "25d629f6642e42597c6e5a9d68fafe85fb76a5080fe3c21c7f14828176f1c5af",
"id": "seo.default@1"
},
"ruleId": "slug.form",
"severity": "WARNING",
"subject": {
"id": "value",
"type": "slug"
}
}
]
}Recommended use cases
- Reject a slug with spaces or uppercase
- Confirm a generated slug still passes after a CMS round-trip
Avoid for
- Creating the slug from a title
- Fetching the published path
Related skills
Composable with
Safety & privacy
- Runs without calling any external service.
- Your payloads are never stored permanently.
- Telemetry captures metadata only — never your payload contents.
- We never train models on your payloads.
- No human reviews your payloads.