Backlink imports: bring the sources you already use

Keep the original export

Retain the file and note the provider, export date and filters. Columns such as first seen and last seen describe provider observations. They do not establish that AgentLinkOps checked the page at those times.

Map a source page to a target page

The importer needs both URLs for each row. A table of linking domains or a summary of link counts is not a page-level backlink export. Choose the appropriate adapter, inspect the detected columns and supply overrides if your headers differ.

Preview and resolve rejected rows

The repository CLI import command reads the file and reports what it would accept. It does not write a ledger or import a remote run. Correct mapping problems and investigate rejected rows before handing accepted candidates to an authorized workflow.

Verify selected candidates separately

A parsed URL is not a verified backlink. Check the candidate source page before relying on its current anchor or link attributes. Keep provider data and current observations distinct in your own records.

A practical example

A CSV contains two rows for the same source and target, one malformed source URL and one link to another domain. A useful preview surfaces duplicates and rejected rows instead of silently treating every line as a new placement. Keep those results beside the original file so the next reviewer can explain the totals.

Choose the supplier guide that matches your file headers. The examples are small synthetic compatibility fixtures, not promises about every current export variant. When a provider changes labels or your file has been transformed, use explicit mappings and check the preview.

What you can use in AgentLinkOps

Imports and individual candidate checks exist in the private pilot. The CLI examples require an existing authorized repository checkout. No public package installation is implied, and a successful local preview does not create a competitor inventory or activate live supplier discovery.

Read the tool guide and connection requirements before setting up a workflow.