Check one backlink locally

You need Node.js 22.13.0 or later and network access. The command below reads the publisher’s HTML once and saves evidence you can compare later. No account or ledger is required. Prefer a browser? Use the public backlink checker. It performs a one-time check and starts no monitoring.

Check a page

The source is the publisher page containing the link. The target is the page on your site it should point to. Replace both URLs with public pages:

npx -y agentlinkops check \
  --source https://publisher.example/resources \
  --target https://your-site.example/guide \
  --scope exact \
  --json \
  --out result.json

--json shows the evidence; --out keeps it in a file. Choose a new filename if result.json already exists.

See what you found

A present result might contain the values below. They are illustrative; read your own values under observation in result.json.

Evidence	Illustrative value and meaning
Link found	`present`. The fetched HTML contains a matching link.
Destination	`https://your-site.example/guide`. Where the matched link points.
Anchor text	`Your guide`. The link text the publisher used.
Link attributes	`["nofollow", "ugc"]`. The publisher’s link qualifications.
Nearby text	`Recommended reading: Your guide`. Nearby text to help you locate the link.
Publisher response	`200`. The publisher page’s HTTP response.
Page indexing directive	`false`. No generic page-level noindex directive was found.

In this example, the link points to the expected guide, but it carries nofollow and ugc. Compare these with the placement you expected. Google explains rel values. This check reads static HTML; it does not render JavaScript or check visual visibility. Page directives do not establish whether Google indexed the page.

Find these values in the JSON result

All paths below are inside observation:

Evidence	JSON path
Link found	`state`
Destination	`occurrences[].targetUrl`
Anchor text	`occurrences[].anchor`
Link attributes	`occurrences[].rel`
Nearby text	`occurrences[].context`
Publisher response	`httpStatus`
Page indexing directive	`directives.noindex`

Choose the next action

Result	Next action
`present`	Review the matched URL, anchor and attributes; keep the evidence if this is a placement you track.
`absent`	Check both URLs and open the publisher page before treating the placement as missing.
`unknown`	Read `reason`; a challenge, timeout or page needing JavaScript requires another way to inspect it.
`source_unavailable`	Review the dated publisher response, such as HTTP 404 or 410.

A single observation does not confirm removal. Evidence states explains the distinction.

Organize a saved placement

The local check reports what the page contains. It does not assign a type or tags.

Read supplier score dates in the app

In Links and Find backlinks, the Retrieved date under the first visible score (Domain strength, Spam risk or Page strength) records when AgentLinkOps obtained the backlink index’s scores. Date unavailable means the saved retrieval date is missing or invalid. This date does not tell you when the page was checked or when the index calculated the score. Missing scores remain Unavailable.

For saved links, choose Link type yourself and use Tags for campaign or client labels. These choices are separate from observed attributes such as nofollow. Link types explains saved choices, deliberate clears and any retained assessment evidence. Use the app to keep the placement in your workspace, or choose the optional ledger below.

Keep this result in a new local ledger

Run these commands in the folder where you want your records:

npx -y agentlinkops init
npx -y agentlinkops adopt-result result.json --intent expected
npx -y agentlinkops status

Use expected for a placement that should exist now, or wanted for one you are pursuing. Adoption requires the CLI’s native lock on macOS or Linux. It keeps the original observation; it does not schedule future checks. Local ledger tags are labels you supply. Read file ownership before committing the records.

For recurring hosted checks, connect the CLI and follow monitoring. Read troubleshooting if the command fails.

Start here

Links and reports

Outreach

Connections and local files

Understand and troubleshoot

Check one backlink locally

Check a page

See what you found

Choose the next action

Organize a saved placement

​Check a page

​See what you found

​Choose the next action

​Organize a saved placement

Check a page

See what you found

Choose the next action

Organize a saved placement