SEO Tools
HTTP Link header parser.
Paste a Link: response header. See every link split out with its rel values, hreflang, type, media, anchor, and decoded title*. Missing rel, duplicate parameters, and relative URIs are flagged.
Header
Privacy note: parsing runs in this browser. Nothing is uploaded and no URL you paste is contacted. This checks header syntax only; it does not confirm the linked pages exist.
Parsed links
Paste a header and press Parse header.
What this parser does
Grammar
Follows RFC 8288 section 3: <URI-Reference> then ;-separated parameters, each a token or quoted-string. Commas and semicolons inside quotes do not split anything.
Parameters
Lists each rel (space-separated values become separate relations), plus anchor, hreflang, type, media, and title. title* is decoded as an RFC 8187 value (UTF-8 or ISO-8859-1) and wins over title.
Diagnostics
Flags a missing rel, repeated rel/type/media/title, deprecated rev, malformed quoting, and relative URIs. Enter a base URL to see them resolved.
Link header questions
How is this different from the hreflang checker?
The hreflang checker reads language alternates in HTML, headers, and sitemaps. This tool parses any Link header, whatever the relation: canonical, preload, next, prev, alternate, or extension types.
What happens when a parameter is repeated?
RFC 8288 says rel, media, title, title*, and type must not appear more than once in a link and later occurrences are ignored. hreflang may repeat. The parser reports the repeat and uses the first value.
Does a clean result mean the link works?
No. It confirms the header is well-formed. It does not fetch the target or confirm that a browser or search engine will act on it.
Standards
- RFC 8288: Web LinkingLink header ABNF, rel, anchor, and target attributes (October 2017).
- RFC 8187: Indicating Character Encoding and Language for HTTP Header Field ParametersThe title* ext-value encoding.
- RFC 3986 section 5Relative reference resolution.