Start with the source and the page receiving the link
A backlink is easiest to recognize when you keep two pages in view. In the first scene, an article on fieldnotes.example refers readers to a sampling method on soil-lab.example. For the article, that is an outgoing link. For the method page, it is an incoming backlink. Reversing the viewpoint does not create a second link.
Use the numbered markers in the walkthrough: 1 identifies the source page, 2 the linked text or image, and 3 the resolved destination. All sites and page scenes are invented for teaching. The destinations are printed for inspection, not offered as publisher inventory. Switch to the HTML view when the visual appearance leaves a question unanswered.
An editorial citation explains why the destination belongs
The first paragraph needs a method behind a soil-test result. Its linked phrase names that method, and its href points to the method page rather than an unrelated homepage. The citation has a clear reader task: find out how the sample was collected before interpreting the measurement. This is the useful property illustrated by the example.
The same words could be placed on an irrelevant page or point to a different resource. A screenshot alone would not establish the context or destination. Google recommends an a element with a resolvable href for reliable crawling. A recognisable link is still not proof that a search engine indexed it or that it improved rankings.
An author-bio link serves a different reading task
The biography scene introduces a research team and links to its notebook. The link gives the reader a way to learn about the contributor’s work. Record the biography page as the source and the notebook as the destination; do not replace either with a domain-only label when explaining the example.
Being in a biography says where the link appears. It does not tell you whether the contribution was paid, who reviewed it or how useful the notebook is. A guest contribution can also contain a link in its body. Keep the placement location separate from the publishing relationship, and examine the actual page instead of treating “author bio” as a quality certificate.
A sponsored guest post makes the relationship visible
The paid-collaboration scene states its commercial context and links to a container-sizing guide. The snippet preserves both sponsored and nofollow. It is still a hyperlink to a separate site; the attributes give additional information about the relationship. Do not remove one value from an evidence record just to fit a single display label.
Google recommends sponsored for paid links and ugc for user content; combinations are allowed. Google’s link-spam policy addresses links created primarily to manipulate rankings. This example explains how to read a paid placement, not how to buy a guaranteed ranking result or verify a publisher’s claims.
For an image link, separate the image file from the target
The illustrated scene has two paths in its snippet. The img src points to the picture file on the source site. The surrounding a href points to a guide on the laboratory site. The reader follows the latter when activating the image link. The diagram labels the guide as the destination, not the SVG file.
The alt text in this example describes the illustration. Compare it with the visible caption, which is a separate presentation choice. The downloaded reference pack keeps the code as text so the sample image path is never fetched. The drawing is an authored illustration; neither its appearance nor its alternative text establishes the quality of the destination.
Read comments and resource lists in their own context
A community participant shares a sampling checklist while explaining a process. The ugc nofollow values remain visible in the snippet and comparison file. The surrounding comment helps explain the reference, but it does not show that the whole community has reviewed or endorsed the linked resource. An individual contribution and a publisher’s editorial recommendation are different observations.
The resource-list scene also points to a checklist, but it appears among materials for a field session. Ask why that item helps the intended reader and whether the destination still matches that purpose. A list entry is not automatically valuable because it looks organised, and a comment is not automatically useful because it contains a relevant phrase. Inspect the specific example instead of ranking formats.
Compare a domain mention with an internal link
The workshop notes contain the visible string soil-lab.example, but the snippet uses span and has no href. It is a name in the text, not a hyperlink in this example. Blue text, an underline or a familiar domain spelling cannot substitute for inspecting the actual element. The walkthrough consequently shows no resolved destination for this scene.
The final scene does contain a link: ./sample-storage resolves to another page on fieldnotes.example. Relative href values resolve from the current document’s address. It is internal navigation here because the source and target stay on the same illustrated site. The example uses no redirect or base element; those would require additional evidence on a real page.
Keep a compact record you can check again
Save the selected scene as TXT when explaining one placement, or download the HTML reference pack and CSV to compare all eight. Each record retains the full source address, literal href, resolved destination, visible wording or image alt text, recorded attributes, interpretation and fictional provenance. The reference HTML has no external assets or scripts and can be printed offline.
For a real page, retain its URL and observation date, inspect the element and destination, and record the publishing relationship only when supported. Keep unknown facts unknown. A good example teaches what the evidence shows; it does not replace an audit, an outreach plan or a live backlink database. Continue with the separate definition, taxonomy and attribute guides when those questions become relevant.