Dofollow describes an ordinary link, not a required switch
“Dofollow” is a common label for a link without search-qualification values such as nofollow, sponsored or ugc. It is not a special attribute that must be added to an anchor. Google’s outbound-link guidance says ordinary references need no such qualification. The visible text or a seller’s label cannot establish what the published element contains.
This tutorial inspects one exact source-to-target relationship. The separate relationship-comparison guide explains which values suit different publishing contexts. Here the question is practical: which element points to the target, what attributes does it have, and what evidence should be recorded?
Inspect the element and resolve the destination
Use the browser’s element inspector to select the actual anchor. Record its href, visible text and complete rel string. Resolve a relative href against the document base before comparing it with the expected target. A styled span with a data-href is not the same as an anchor with href. Google’s crawlable-link guidance explains this distinction.
Keep the source URL, collection date and whether you inspected server HTML or a rendered DOM. Scripts may insert or alter elements, so those views can differ. Inspect all matching references if the page contains more than one; the first match may not represent the link you intended to review.
Read five real markup examples
These authored examples use reserved domains and the same destination. Their expected outcomes are checked with the application’s existing HTML inspector against a “follow” expectation. FOUND means a matching reference satisfies that parser expectation; ATTRIBUTES_CHANGED means a reference exists but differs; NOT_FOUND means none was found in the supplied HTML. These are local parser results, not live website observations.
Example 1 has no qualifying rel value. Example 2 remains a link but contains sponsored and nofollow. Example 3 shows that writing dofollow does not cancel NOFOLLOW. Example 4 has two matching anchors, only one unqualified, so all matches matter. Example 5 provides a data attribute without an anchor and is not counted by this inspector.
| Example | Matching anchors | Follow expectation | Evidence |
|---|---|---|---|
| 1 | 1 | FOUND | Ordinary anchor |
| 2 | 1 | ATTRIBUTES_CHANGED | sponsored nofollow |
| 3 | 1 | ATTRIBUTES_CHANGED | dofollow NOFOLLOW |
| 4 | 2 | FOUND | One qualified and one unqualified |
| 5 | 0 | NOT_FOUND | span with data-href only |
1 · Ordinary anchor
<a href="https://resource.example/soil">soil-sampling guide</a>2 · Qualified reference
<a href="https://resource.example/soil" rel="sponsored nofollow">soil-sampling guide</a>3 · A misleading literal label
<a href="https://resource.example/soil" rel="dofollow NOFOLLOW">soil-sampling guide</a>4 · Two matching references
<a href="https://resource.example/soil" rel="sponsored">soil-sampling guide</a>
<a href="https://resource.example/soil">soil-sampling guide</a>5 · A styled element without an anchor
<span data-href="https://resource.example/soil">soil-sampling guide</span>Do not confuse browser attributes with search relationships
Values such as noopener and noreferrer describe browser-related behaviour; they are not substitutes for sponsored or nofollow. Preserve the complete original string before applying a reporting category. Google accepts some combined-value formats that differ from the browser’s whitespace token list, so a simplified provider label may hide important detail. The relationship explainer preserves both views.
A paid reference should retain appropriate qualification even if a campaign brief asks for “dofollow.” Do not change the publishing relationship to make a monitor expectation pass. Google describes these relationship values as hints; no local HTML check can promise how a search engine will value a specific link.
Create a repeatable inspection record
Keep the exact source, expected target, original HTML or DOM capture, method, date, anchor, rel values and match count. Record the expectation separately from the observation. If the link is present but qualified, report that difference rather than treating it as an absent reference. If several matches exist, identify which element supports your conclusion.
Download the example outcomes or a blank CSV for your own checks. The existing monitor can inspect supplied source/target pairs and retain their history within its limits; its server-HTML view does not execute a publisher’s JavaScript. Use a rendered browser inspection when that difference matters, and link the evidence rather than silently combining unlike observations.
Download the example inspection CSV · Download a blank inspection CSV
An unqualified anchor is not a ranking or acquisition guarantee
A present, unqualified link does not prove that the source is indexed, the destination is useful or rankings will improve. Check destination content and context separately. A technical inspection also does not establish that a publisher will keep a link or accept a new placement. Keep publication terms, current evidence and measured outcomes distinct.
This tutorial does not offer a free-site list, automatic approvals, named-platform placement recipes or guaranteed “high authority” opportunities. Those requests require current evidence beyond a markup definition. It provides a reproducible way to inspect a reference you already have permission to examine.