import_backlinks
Store a backlink export the user already owns, from Ahrefs, Search Console, Semrush, Majestic, Moz, DataForSEO, Linkody or a generic CSV, as discovery candidates. Costs nothing and buys nothing: the user already paid their supplier. The supplier is named in provenance and its dates stay supplier dates, separate from any check we run. An import NEVER claims complete coverage, because nothing in an export says whether it is the whole result or one filtered page. Rejected rows come back with the response, identified by position; none is dropped. Re-importing the same rows returns the same run rather than duplicating candidates. Imported rows are not verified links, are not enrolled in monitoring, and never enter a shared corpus.
Hosted MCP registration verified. These schemas describe the development contract; confirm supported inputs with tools/list. Generic CLI/HTTP calls require a matching development server. Configure LINKTRAIL_API_URL; production does not expose these command routes.
Reading saved data does not start a verification job. Mutations can change saved records or access; the effects below apply.
Example request
Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.Returned result
Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data instructuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.
Input fields
Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.Validation and omitted values
includeSubdomains and backlinksStatus are required import scope choices. Omitted supplierGeneratedAt remains null, rather than using the import date as a supplier date. Omitted idempotencyKey uses deterministic content-based import identity. Re-importing the same scope, supplier and rows as supplied reuses the run. Imported order remains as_supplied. Every row requires source_url and target_url. Optional supplier metadata retains its provenance; invalid rows are returned with their positions while valid neighbors continue.Defaults when omitted
Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
Download input schema · Download output schema