👀 Live Preview
Legacy anchor with rev="related" (browsers render the link normally; rev has no visible effect):
The link works — but rev is ignored by modern browsers for relationship semantics. Use rel instead.

The rev attribute described the reverse relationship on a hyperlink — how the linked document relates back to the current page. It was the inverse of rel on the same <a> or <link> element. Important: rev is obsolete in HTML5 and should not be used in new projects. Modern sites use rel from each document’s own perspective instead. This tutorial explains rev for learning legacy markup and understanding how it differs from rel.
Inverse rel.
HTML5.
Key diff.
Elements.
Legacy JS.
Modern way.
rev AttributeIn HTML 4, link relationships could be expressed in two directions on one tag. The rel attribute said what the linked resource is to the current document (forward). The rev attribute said what the current document is to the linked resource (reverse).
For example, a chapter page linking to its book might use rel="up" (the target is above in the hierarchy). The same link could also have used rev="subsection" (the current page is a subsection of the target). HTML5 dropped rev because expressing one direction with rel is clearer and sufficient.
Browsers and search engines ignore rev for practical purposes today. Use rel on modern links instead.
Legacy syntax on a or link (historical reference only):
<!-- Reverse relationship (obsolete) -->
<a href="/guide/index.html" rev="subsection">Back to guide</a>
<!-- Modern equivalent: use rel from this page -->
<a href="/guide/index.html" rel="up">Back to guide</a>rel).<a> and <link>.element.rev existed on legacy DOM interfaces.rel on each page instead of rev.reversed on ol (different attribute).Common legacy rev keywords (HTML 4 link types):
rev="made" — Linked resource was created by the author of the current page (e.g. author homepage link).rev="subsection" — Current document is a subsection of the linked resource.rev="derived" — Current document was derived from the linked resource.rev="related" — General reverse relationship between documents.<!-- Author page link (legacy) -->
<a href="https://author.example.com" rev="made">Author</a>
<!-- Modern: use rel=author on the same link -->
<a href="https://author.example.com" rel="author">Author</a>| Attribute | Direction | Status |
|---|---|---|
rel | Current → linked | Active, use this |
rev | Linked → current | Obsolete |
rev="made" | Target made by this page’s author | Legacy |
rev="subsection" | This page is part of target | Legacy |
rel="up" | Modern parent/nav hint | Preferred |
element.rev | Legacy JS property | Avoid in new code |
| Element | Historically? | Today |
|---|---|---|
<a> | Yes | Use rel only |
<link> | Yes | Use rel only |
<area> | No | Never supported rev |
<ol reversed> | N/A | Different attribute — not rev |
rev vs rel| Scenario | Legacy rev | Modern rel |
|---|---|---|
| Chapter → book | rev="subsection" | rel="up" on chapter link |
| Page → author site | rev="made" | rel="author" |
| Related content | rev="related" | rel="related" (forward is enough) |
| Direction | Linked → current | Current → linked |
Legacy rev markup, dynamic element.rev in JavaScript, and the modern rel replacement.
Legacy anchor with rev="related" (browsers render the link normally; rev has no visible effect):
The link works — but rev is ignored by modern browsers for relationship semantics. Use rel instead.
Historical reverse-relationship markup on an anchor:
<a href="/docs/related-page.html" rev="related">
Related document
</a>rev="related" once hinted that the linked page had a reverse “related” tie to this page. Today, rel="related" on the forward link is sufficient.
Legacy DOM property element.rev (educational only):
<a id="dynamicLink" href="https://example.com">Visit Example</a>
<script>
document.getElementById("dynamicLink").rev = "made";
</script>rev was writable like other string attributes, but setting it today does not improve SEO or browser behavior.
Express the relationship with rel instead:
<!-- Instead of rev="subsection" -->
<a href="/guide/" rel="up">Parent guide</a>
<!-- Instead of rev="made" -->
<a href="https://author.example.com" rel="author">Author</a>
<!-- Pagination -->
<a href="/page/2" rel="next">Next</a>Each page declares outbound relationships with rel. If you need a reciprocal hint, add the appropriate rel on the other page too.
rev never changed how links looked or behaved for assistive tech.rel values like prev/next can aid navigation when paired with visible labels.rev semantics.reversed boolean on ordered lists.href → B.
A → B.
B → A.
One direction.
The rev attribute is obsolete. Browsers may still parse it in the DOM, but it has no meaningful effect in modern HTML.
rev is legacy onlyUse rel for all link relationships in modern HTML.
rel replacement Fully supportedBottom line: Learn rev for reading old HTML — use rel in all new markup.
rel for all new link relationshipsrev only to understand legacy HTML 4 pagesrev with equivalent rel when refactoring old sitesrel="prev" / rel="next" for paginationrev to new projectsrevrev with reversed on <ol>rev and redundant rel without reasonrev="made" means the current page created the target (read the spec carefully)The rev attribute described reverse link relationships in HTML 4 — the inverse of rel on the same element.
It is obsolete in HTML5. For all practical purposes today, use rel and express relationships from each document’s own perspective.
revBookmark these when reading legacy HTML.
Inverse dir.
ConceptHTML5.
StatusModern fix.
TodayLegacy only.
ScopeDifferent attr.
Gotcharel on the same link.rev is obsolete. Do not use it in new HTML. Use rel instead.rel = current page → linked resource. rev = linked resource → current page (legacy).reversed is a boolean on <ol> that reverses list numbering. Completely unrelated to rev.rel with the appropriate forward keyword — e.g. rel="up" instead of rev="subsection", or rel="author" instead of rev="made".rev has no semantic effect in modern browsers or search engines.Understand obsolete rev markup, then use the active rel attribute for real link relationships.
5 people found this page helpful