HTML rev Attribute

Beginner
⏱️ 5 min read
📚 Updated: Jun 2026
🎯 3 Examples
Links & Legacy

Introduction

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.

What You’ll Learn

01

Reverse

Inverse rel.

02

Obsolete

HTML5.

03

vs rel

Key diff.

04

a, link

Elements.

05

.rev

Legacy JS.

06

Use rel

Modern way.

Purpose of rev Attribute

In 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.

⚠️
Obsolete — do not use in new code

Browsers and search engines ignore rev for practical purposes today. Use rel on modern links instead.

📝 Syntax

Legacy syntax on a or link (historical reference only):

rev.html
<!-- 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>

Syntax Rules

  • Value is a space-separated list of link type keywords (like rel).
  • Historically valid on <a> and <link>.
  • Describes relationship from linked resource → current document.
  • Obsolete in HTML5 — validators may flag it.
  • JavaScript: element.rev existed on legacy DOM interfaces.
  • Prefer rel on each page instead of rev.
  • Not related to reversed on ol (different attribute).

💎 Values

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.
rev-values.html
<!-- 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>

⚡ Quick Reference

AttributeDirectionStatus
relCurrent → linkedActive, use this
revLinked → currentObsolete
rev="made"Target made by this page’s authorLegacy
rev="subsection"This page is part of targetLegacy
rel="up"Modern parent/nav hintPreferred
element.revLegacy JS propertyAvoid in new code

Applicable Elements

ElementHistorically?Today
<a>YesUse rel only
<link>YesUse rel only
<area>NoNever supported rev
<ol reversed>N/ADifferent attribute — not rev

rev vs rel

ScenarioLegacy revModern rel
Chapter → bookrev="subsection"rel="up" on chapter link
Page → author siterev="made"rel="author"
Related contentrev="related"rel="related" (forward is enough)
DirectionLinked → currentCurrent → linked

Examples Gallery

Legacy rev markup, dynamic element.rev in JavaScript, and the modern rel replacement.

👀 Live Preview

Legacy anchor with rev="related" (browsers render the link normally; rev has no visible effect):

Related: HTML rel attribute

The link works — but rev is ignored by modern browsers for relationship semantics. Use rel instead.

Example — rev="related" (legacy)

Historical reverse-relationship markup on an anchor:

rev-related.html
<a href="/docs/related-page.html" rev="related">
  Related document
</a>
Try It Yourself

How It Works

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.

Dynamic Values with JavaScript

Legacy DOM property element.rev (educational only):

dynamic-rev.html
<a id="dynamicLink" href="https://example.com">Visit Example</a>

<script>
  document.getElementById("dynamicLink").rev = "made";
</script>
Try It Yourself

How It Works

rev was writable like other string attributes, but setting it today does not improve SEO or browser behavior.

Example — Modern rel replacement

Express the relationship with rel instead:

rel-instead-of-rev.html
<!-- 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>
Try It Yourself

How It Works

Each page declares outbound relationships with rel. If you need a reciprocal hint, add the appropriate rel on the other page too.

♿ Accessibility

  • No user-facing effectrev never changed how links looked or behaved for assistive tech.
  • Use clear link text — Relationship metadata does not replace descriptive anchor text.
  • Landmarks from rel — Modern rel values like prev/next can aid navigation when paired with visible labels.
  • Do not rely on rev — Screen readers and browsers do not expose obsolete rev semantics.
  • Not reversed on ol — Do not confuse with the reversed boolean on ordered lists.

🧠 How rev Worked

1

Page A links

href → B.

Link
2

rel forward

A → B.

rel
3

rev reverse

B → A.

rev
=

Use rel now

One direction.

Browser Support

The rev attribute is obsolete. Browsers may still parse it in the DOM, but it has no meaningful effect in modern HTML.

⚠️ Obsolete · Not recommended

rev is legacy only

Use rel for all link relationships in modern HTML.

0% Practical support
All modern browsers Ignored for semantics
Obsolete
DOM property May still exist
No effect
rel replacement Fully supported
Use instead
rev attribute (semantic use) Obsolete

Bottom line: Learn rev for reading old HTML — use rel in all new markup.

💡 Best Practices

✅ Do

  • Use rel for all new link relationships
  • Learn rev only to understand legacy HTML 4 pages
  • Replace rev with equivalent rel when refactoring old sites
  • Use rel="prev" / rel="next" for pagination
  • Link to the rel attribute guide for active keywords

❌ Don’t

  • Add rev to new projects
  • Expect SEO benefit from rev
  • Confuse rev with reversed on <ol>
  • Use both rev and redundant rel without reason
  • Assume rev="made" means the current page created the target (read the spec carefully)

Conclusion

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.

Key Takeaways

Knowledge Unlocked

Five truths every developer should know about rev

Bookmark these when reading legacy HTML.

5
Core concepts
02

Obsolete

HTML5.

Status
🔗 03

Use rel

Modern fix.

Today
📝 04

a + link

Legacy only.

Scope
🚫 05

Not reversed

Different attr.

Gotcha

❓ Frequently Asked Questions

It described the relationship from the linked document back to the current document — the reverse of rel on the same link.
No. rev is obsolete. Do not use it in new HTML. Use rel instead.
rel = current page → linked resource. rev = linked resource → current page (legacy).
No. 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".
The DOM property may exist, but rev has no semantic effect in modern browsers or search engines.

Learn legacy links, build with rel

Understand obsolete rev markup, then use the active rel attribute for real link relationships.

Read rel guide →

About the author

Mari Selvan M P
Mari Selvan M P 🔗

Developer, cloud engineer, and technical writer

  • Experience 12 years building web and cloud systems
  • Focus Full Stack Development, AWS, and Developer Education

I write practical tutorials so students and working developers can learn by doing—from databases and APIs to deployment on AWS.

5 people found this page helpful