staticdata.dev
Menu
Datasets About Contact

Link Relations

The complete registry of IANA-registered link relation types as used in HTTP Link headers, HTML link elements, and Atom feeds. Each entry includes the relation name (the rel value), a description of its semantics, and the normative reference (typically an RFC or W3C specification) that defines it. The dataset covers all 134 registered relations (as of October 2026) — from common ones like canonical, stylesheet, and next to specialised types for versioning, time ontology, and WebSub notifications.

v1.0.0 MIT 134 records Updated 2026-10-05 stable Source:  IANA Link Relations Registry

Quick fetch

Stable URL. CORS-enabled. No auth.

bash 
curl https://staticdata.dev/v1/link-relations.json

Or use as a typed import: import { linkRelations } from "https://staticdata.dev/v1/link-relations.ts"

Formats

  • JSON 26.8 KB

    /v1/link-relations.json

    Open

    min: 23.6 KB · /v1/link-relations.min.json

  • CSV 18.0 KB

    /v1/link-relations.csv

    Open
  • TypeScript 27.0 KB

    /v1/link-relations.ts

    export const linkRelations

    type LinkRelation = (typeof linkRelations)[number]

    Open

Schema

Each record in the dataset has the following shape.

Schema
Field Type Description Example
relation string The link relation type name (the rel value) canonical
description string Human-readable description of the relation's semantics Designates the preferred version of a resource (the IRI and its contents).
reference string Normative reference that defines this relation type [RFC6596]

Preview

First 10 records.

Data preview
relationdescriptionreference
aboutRefers to a resource that is the subject of the link's context.[RFC6903], section 2
aclAsserts that the link target provides an access control resource for the link context.[https://solidproject.org/TR/wac#acl-link-relation]
alternateRefers to a substitute for this context[HTML]
amphtmlUsed to reference alternative content that uses the AMP profile of the HTML format.[AMP HTML]
api-catalogRefers to a list of APIs available from the Publisher of the link context.[RFC9727]
appendixRefers to an appendix.[HTML 4.01 Specification]
apple-touch-iconRefers to an icon for the context. Synonym for icon.[Configuring Web Applications]
apple-touch-startup-imageRefers to a launch screen for the context.[Configuring Web Applications]
archivesRefers to a collection of records, documents, or other materials of historical interest.[HTML5]
authorRefers to the context's author.[HTML]

Showing 10 of 134. View full data:  JSON · CSV

Fetch examples

Drop-in snippets in five languages.

curl 
curl -sSL https://staticdata.dev/v1/link-relations.json | jq '.[0]'
JavaScript 
import type { LinkRelation } from "https://staticdata.dev/v1/link-relations.ts";

const res = await fetch("https://staticdata.dev/v1/link-relations.min.json");
if (!res.ok) throw new Error(`Fetch failed: ${res.status}`);
const linkRelations: LinkRelation[] = await res.json();
console.log(linkRelations[0]);
Python 
import urllib.request, json

with urllib.request.urlopen("https://staticdata.dev/v1/link-relations.min.json") as r:
    linkRelations = json.load(r)

print(linkRelations[0])
Go 
package main

import (
	"encoding/json"
	"fmt"
	"net/http"
)

func main() {
	resp, err := http.Get("https://staticdata.dev/v1/link-relations.min.json")
	if err != nil { panic(err) }
	defer resp.Body.Close()

	var data []map[string]any
	if err := json.NewDecoder(resp.Body).Decode(&data); err != nil {
		panic(err)
	}
	fmt.Println(data[0])
}
Rust 
use serde_json::Value;

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let body = ureq::get("https://staticdata.dev/v1/link-relations.min.json").call()?.into_string()?;
    let data: Vec<Value> = serde_json::from_str(&body)?;
    println!("{:?}", data.first());
    Ok(())
}

Sources and methodology

Link relation types are standardised tokens that describe the relationship between a linking resource and the target resource. They appear in the rel attribute of HTML <link> and <a> elements, in HTTP Link response headers as defined by RFC 8288, and in Atom feed entries. IANA maintains the authoritative registry at https://www.iana.org/assignments/link-relations/, and this dataset is a direct, faithful transcription of that registry as of October 2026.

The registry encompasses relation types from a wide range of specifications. Many everyday types — stylesheet, icon, next, prev, prefetch, preconnect, nofollow, noreferrer — are defined by the HTML Living Standard and are familiar to front-end developers; others in daily use come from their own specifications, such as canonical (RFC 6596), preload (W3C Preload) and manifest (Web App Manifest). Others originate in IETF RFCs: via, self, related, enclosure (RFC 4287 / Atom), edit, service (RFC 5023 / Atom Publishing Protocol), first, last, up, payment (RFC 8288), and many more. A group of fifteen interval* relations (from the W3C Time Ontology in OWL) support linked-data temporal semantics.

Reference values are included exactly as they appear in the IANA registry — typically an RFC citation in square brackets, a URL, or a specification title. Some references are informal (e.g. [HTML], [HTML5]) pointing to the HTML Living Standard or its predecessor. Descriptions for multi-line entries in the source CSV have had internal whitespace normalised to a single space; no editorial changes were made to the wording.

Versioning

URLs under /v1/ are stable: field names and types will not change in a way that breaks consumers. Values can be corrected or records added when the upstream source changes; schema-incompatible updates ship under a new version path. See the link-relations changelog for this dataset's history.

Related datasets

More Web datasets