Skip to main content

Squillify development is paused indefinitely. Read why, and discover what this experiment achieved. Read the story

Squillify
MicroSkills Reference

Detect Missing Metadata

seo.detect_missing_metadata

ProductionBounded custom (Class B)Deterministicstrictinstantv1.0.0
No network

Overview

List required metadata fields that are missing or empty in a supplied record. We never fetch a URL, run a script, or choose a winner. A successful call costs 1 execution credit.

A page audit should not hide a missing canonical inside a prose report; this lists the gaps.

Reliability

seo.detect_missing_metadata 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 extracted title, description, canonical, or robots fields and need a gap list.

When the fields are still inside HTML — run seo.extract_meta_tags first — or you want us to invent the missing copy.

Scope

Note
List required metadata fields that are missing or empty in a supplied record.

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 invent missing metadata

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

analysisparsing

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input1 MB

How we handle your data

Sensitive output possible
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.

Read the Microskill Data Handling Policy

Input schema

FieldTypeRequiredDescription
metadataobjectYesRequired. Extracted metadata record with named title, description, canonical, and robots string fields, each bounded.
requiredFieldsarrayNoFields that must be present. Omit it and we require title, description, and canonical.

Output schema

FieldTypeRequiredDescription
missingarrayYesRequired. Structured 'missing' value. Objects expose named properties; arrays list bounded rows or strings produced from the supplied artifacts, up to 10,000 entries.
emptyarrayYesRequired. Structured 'empty' value. Objects expose named properties; arrays list bounded rows or strings produced from the supplied artifacts, up to 10,000 entries.
requiredFieldsarrayYesRequired. Structured 'requiredFields' value. Objects expose named properties; arrays list bounded rows or strings produced from the supplied artifacts, up to 10,000 entries.
completebooleanYesRequired. Structured 'complete' value produced by this offline analysis.
findingsarrayYesArray of 0 to 1000 finding objects. Each item has ruleId, severity (ERROR, WARNING, or INFO), certainty, subject {type, id}, message, evidence[{artifactId, path, actual}], and profile {id, checksumSha256}.

API contract

POST /v1/execute
curl
curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"seo.detect_missing_metadata","input":{"metadata":{"title":"Acme"}}}'
Integrations
TypeScript SDK
import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("seo.detect_missing_metadata", {"metadata":{"title":"Acme","description":"Plans","canonical":"https://www.example.com/"}});

Errors

CodeHTTPRetryableDescription
VALIDATION_ERROR400NoThe request payload failed schema validation.
UNAUTHORIZED401NoMissing or invalid API key.
SKILL_NOT_ACCESSIBLE403NoThe API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN403NoThis skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE503YesPlan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND404NoThe requested skill or version does not exist.
TENANT_RATE_LIMITED429YesRequest rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED429YesPlan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT504YesExecution exceeded the allowed time budget.
SEO_INPUT_REQUIRED400NoThe request payload failed this skill's input validation.
SEO_INPUT_TOO_LARGE429NoA size, quota, rate, or time limit was exceeded.
SEO_HTML_MALFORMED400NoThe request payload failed this skill's input validation.
SEO_PROFILE_UNKNOWN400NoThe request payload failed this skill's input validation.
SEO_TOO_MANY_RECORDS429NoA size, quota, rate, or time limit was exceeded.

Other limits

LimitValue
Recommended inline bytes32 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 invent missing metadata
  • Writing the missing description
  • Crawling to discover metadata

How to call

POST /v1/execute (requires authentication)

Request bodyjson
{
  "skillKey": "seo.detect_missing_metadata",
  "input": {
    "metadata": {
      "title": "Acme",
      "description": "Plans",
      "canonical": "https://www.example.com/"
    }
  }
}

Examples

Primary business path

Inputjson
{
  "metadata": {
    "title": "Acme",
    "description": "Plans",
    "canonical": "https://www.example.com/"
  }
}
Expected outputjson
{
  "findings": [],
  "requiredFields": [
    "title",
    "description",
    "canonical"
  ],
  "empty": [],
  "complete": true,
  "missing": []
}
Tip
First realistic scenario for this skill.

Boundary or option path

Inputjson
{
  "metadata": {
    "title": "Acme"
  }
}
Expected outputjson
{
  "findings": [
    {
      "certainty": "POLICY_RESULT",
      "evidence": [
        {
          "actual": "",
          "artifactId": "input",
          "path": "description"
        }
      ],
      "message": "Required field description is missing from the supplied metadata.",
      "profile": {
        "checksumSha256": "25d629f6642e42597c6e5a9d68fafe85fb76a5080fe3c21c7f14828176f1c5af",
        "id": "seo.default@1"
      },
      "ruleId": "metadata.description.missing",
      "severity": "ERROR",
      "subject": {
        "id": "",
        "type": "description"
      }
    },
    {
      "certainty": "POLICY_RESULT",
      "evidence": [
        {
          "actual": "",
          "artifactId": "input",
          "path": "canonical"
        }
      ],
      "message": "Required field canonical is missing from the supplied metadata.",
      "profile": {
        "checksumSha256": "25d629f6642e42597c6e5a9d68fafe85fb76a5080fe3c21c7f14828176f1c5af",
        "id": "seo.default@1"
      },
      "ruleId": "metadata.canonical.missing",
      "severity": "ERROR",
      "subject": {
        "id": "",
        "type": "canonical"
      }
    }
  ],
  "requiredFields": [
    "title",
    "description",
    "canonical"
  ],
  "empty": [],
  "complete": false,
  "missing": [
    "description",
    "canonical"
  ]
}
Tip
Second scenario using an optional field or edge case.

Recommended use cases

  • Check a CMS export for missing canonicals
  • Require title and description before a publish gate

Avoid for

  • Writing the missing description
  • Crawling to discover metadata

Related skills

seo.validate_title_lengthseo.extract_meta_tags

Composable with

seo.validate_title_length

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.

Tags

seowebparsing
Back to MicroSkills Reference