Normalize URL

Overview

Rewrite one URL with a named RFC 3986 profile and keep the original string beside the result 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.

Two strings that differ only by case or a default port should compare equal without anyone fetching them.

When to use it

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 follow redirects or claim search-engine equivalence

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"seo.normalize_url","input":{"url":"HTTPS://Example.com/a/../product/1?x=1"}}'

import { Squillify } from "@squillify/sdk";

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

const { output } = await sq.execute("seo.normalize_url", {"url":"HTTPS://Example.com:443/a/../product/1?x=1"});

Errors

Other limits

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 follow redirects or claim search-engine equivalence
• Asking whether the URL returns 200
• Picking a preferred canonical from HTML

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "seo.normalize_url",
  "input": {
    "url": "HTTPS://Example.com:443/a/../product/1?x=1"
  }
}

Examples

{
  "url": "HTTPS://Example.com:443/a/../product/1?x=1"
}

{
  "changed": true,
  "profile": "seo.safe.url.normalization@1",
  "transformations": [
    "scheme_case",
    "host_case",
    "default_port",
    "dot_segments"
  ],
  "normalized": "https://example.com/product/1?x=1",
  "original": "HTTPS://Example.com:443/a/../product/1?x=1",
  "equivalence": "SYNTACTIC_ONLY",
  "identityKey": "https://example.com/product/1?x=1"
}

{
  "baseUrl": "https://www.example.com/blog/post/",
  "url": "../pricing"
}

{
  "changed": true,
  "profile": "seo.safe.url.normalization@1",
  "transformations": [
    "resolve"
  ],
  "normalized": "https://www.example.com/blog/pricing",
  "original": "../pricing",
  "equivalence": "SYNTACTIC_ONLY",
  "identityKey": "https://www.example.com/blog/pricing"
}

Recommended use cases

• Fold scheme and host case before you group product URLs
• Resolve ../pricing against the page that linked it

Avoid for

• Asking whether the URL returns 200
• Picking a preferred canonical from HTML

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.

Tags