> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentlinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Check one backlink locally

> Use the supplied CLI to check one public page without an account, read present, absent or unknown results and optionally save the observation in a local ledger.

Use this path for a first result with nothing but Node.js 22 or later and network access: `npm install -g agentlinkops`, or prefix each command with `npx -y` to run it without installing. No account or ledger is needed. [Connect with the CLI](/guides/connect-cli) covers the hosted side.

For hosted checks through your agent, follow [Get started](/quickstart); [availability](/capability-status) tracks releases.

## Run one check

Replace the checkout path and both example URLs:

```bash theme={null}
agentlinkops check \
  --source https://publisher.example/resources \
  --target https://your-site.example/guide \
  --scope exact \
  --out result.json
```

The source is the publisher page; the target is your destination. `exact` matches that URL under the verifier's normalization rules. Use a public page you are permitted to fetch.

## Read the result

* `present`: the read found a matching link. Inspect its occurrences and anchor.
* `absent`: the read found no match. Check the source, target and scope.
* `unknown`: the verifier could not decide. Read the reason, such as a challenge or timeout, and inspect the page with your browser when appropriate.

An unknown result never establishes removal. [Evidence states](/evidence) separates one observation from confirmed loss.

## Save it when useful

To save the original result in a new ledger:

```bash theme={null}
agentlinkops init
agentlinkops adopt-result result.json \
  --intent expected
agentlinkops status
```

Use `expected` when the placement should exist now, or `wanted` when you are pursuing it. Adopting preserves the observation and supports replay. It does not schedule future checks.

Read [file ownership](/ledger) before committing the ledger. For recurring checks, [connect the CLI](/guides/connect-cli) and use [hosted monitoring](/guides/monitor-changes). See [troubleshooting](/guides/troubleshooting) if the command fails.