Import reference · reviewed September 12, 2026

Moz backlink import guide

Prepare Moz backlink rows for AgentLinkOps: source and target columns, a compatible CSV example, preview behavior and common mistakes.

Use the moz adapter for a tabular file with source-page and target-page URLs. The fields below describe the implemented AgentLinkOps adapter. Check your actual headers before using a provider preset; exports can differ by report and version.

Columns this adapter recognizes

Representative compatible headers; aliases may also be supported.
Purpose	Header	Interpretation
source	`Source Page`	Required URL of the page containing the link
target	`Target Page`	Required URL the link points to
anchor	`Anchor Text`	Optional supplier-reported anchor text
first_seen	`First Seen`	Optional provider first-seen timestamp
last_seen	`Last Seen`	Optional provider observation timestamp
link attribute	`Nofollow`	Optional supplier flag; inspect its meaning before use

Domain Authority and Page Authority, when exported, remain Moz metrics in the supplier fields. They do not establish editorial relevance or current link presence.

Keep the original export: the adapter retains at most 32 additional nonblank metric fields, limits their names to 64 characters and string values to 256 characters. The normalized record is not a lossless archive.

A small compatible CSV

This synthetic example shows the minimum page pair and an optional anchor. The example domains are placeholders. Use a copy of your own file for a real preview.

Source Page,Target Page,Anchor Text
https://example.org/resources,https://example.com/guide,Example resource

Download this sample CSV

Preview from an existing repository checkout

The development CLI requires access to the AgentLinkOps repository. There is no public package installation step here. Run mkdir -p examples from the repository root, save the sample as examples/moz.csv, then preview it:

node cli/linktrail.mjs import examples/moz.csv --target example.com --from moz

The import command reads and validates the file. It reports accepted, rejected and duplicate rows; it does not write the local ledger, fetch the source pages or create a remote import run. Keep the preview result beside the original export, and resolve rejected rows before using the candidate list.

What to check before proceeding

Use individual source pages instead of an aggregate domain list. Preserve the target page so links to different resources on the same site remain distinguishable.

A Source Page column and a Source URL column are both recognized aliases. If a spreadsheet calls the column Page, provide the source mapping explicitly and review the target mapping too.

If you include a mapped link-attribute column, inspect empty cells. The current parser treats a blank Nofollow cell as false and a blank dofollow cell as false. Those defaults are not evidence from a current fetch; omit an unreliable flag column or normalize it deliberately.

Confirm that the target URLs match the intended site. A well-formed row for a different target is still outside that import scope. If a column is missing, use an explicit mapping to an existing column or prepare the required data; do not fill in an invented source page.

From an imported row to current evidence

Provider dates and flags describe the supplied data. They do not establish that the backlink is live now. Review the candidate, check the source page and preserve the check time before recording a confirmed placement. A failed request remains inconclusive until you have evidence of what the page contains.

Imports and selected candidate checks are available in the private pilot. Live supplier discovery and competitor-gap workflows are still in validation. A local preview alone does not approve or bind a frozen inventory for competitor comparison.