# Backlink Placement Change Receipts (`muazah/backlink-placement-receipts`) Actor

- **URL**: https://apify.com/muazah/backlink-placement-receipts.md
- **Developed by:** [muazah](https://apify.com/muazah) (community)
- **Categories:** SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 source page auditeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Backlink Placement Change Receipts

You know where your links should be. This checks that they are still there, the way you agreed, and receipts every change.

### What it does

- Checks the placements you supply: source page URL + expected target, up to 500 placements on 100 distinct source pages per run (10 placements per source).
- Per placement: presence in the served HTML, anchor text, resolved URL, rel token set, and tag locator. All matches are captured; several anchors to the same target come back as MULTIPLE\_MATCHES, never a guess.
- Your policy, compared: allowed anchors and required rel tokens (sponsored, ugc, nofollow). No "dofollow" attribute exists and this actor does not score follow value.
- Evidence per source page: final URL after validated redirects, noindex flag, canonical, and a content fingerprint.
- Change receipts across runs per monitorKey: anchor, target, rel, and presence changes with before/after and both timestamps.
- False-loss suppression: a first absence is a suspected loss; CONFIRMED\_HTML\_ABSENCE only after consecutive successful fetches miss the link (default 2). Blocked pages and transport errors never overwrite last-good state.

### Honest limits

- Public HTTPS HTML only. No logins, no proxies, no JavaScript rendering: a link injected by JS alone is reported as not observed in the served HTML, which is what this actor verifies.
- Absence from observed server HTML is not proof the link was removed from the rendered DOM or from any search index.
- Tracking parameters matter: a link whose query differs from your expected target is reported (TARGET\_QUERY\_DIFFERENT), never silently equated. Fragments are stripped by documented policy.
- Blocked pages (403/429) come back as BLOCKED\_OR\_UNVERIFIABLE, uncharged, and are reported, never routed around.

### Input

```json
{
  "placements": [{"id": "p1", "sourceUrl": "https://blog.example.com/post", "targetUrl": "https://yoursite.com", "allowedAnchors": ["Your Brand"], "requiredRel": ["sponsored"]}],
  "monitorKey": "campaign-a"
}
```

### Output

One placement\_receipt per placement (status: MATCH, EXPECTATION\_MISMATCH, MULTIPLE\_MATCHES, NOT\_OBSERVED\_IN\_HTML, BLOCKED\_OR\_UNVERIFIABLE, FETCH\_FAILED, INVALID\_INPUT), change rows with before/after, plus placements.csv, changes.csv and a summary in the run's key-value store. Your placement lists stay in your own run storage.

### Billing

Pay per distinct source page successfully fetched; every placement row on that page and all changes are included. A completed page where the link is absent is charged and returns NOT\_OBSERVED\_IN\_HTML. Invalid, blocked, or failed pages are free.

# Actor input Schema

## `placements` (type: `array`):

Known placements to verify (max 500): id, sourceUrl (public HTTPS page), targetUrl (expected link target). Optional allowedAnchors and requiredRel (e.g. \["sponsored"]). Queries are preserved in comparison; fragments are stripped by documented policy.

## `monitorKey` (type: `string`):

Namespaces stored baselines. Run the same key repeatedly to get change receipts across runs.

## `maxSourcePages` (type: `integer`):

Distinct source pages fetched per run (hard cap 100; max 10 placements per source).

## `confirmAbsentAfter` (type: `integer`):

Successful fetches that must miss the link before CONFIRMED\_HTML\_ABSENCE (min 2). A first absence is a suspected loss, never confirmed.

## Actor input object example

```json
{
  "placements": [
    {
      "id": "p1",
      "sourceUrl": "https://example.org/",
      "targetUrl": "https://iana.org/help/example-domains"
    }
  ],
  "monitorKey": "default",
  "maxSourcePages": 100,
  "confirmAbsentAfter": 2
}
```

# Actor output Schema

## `receiptRows` (type: `string`):

One placement\_receipt per placement (status, observed matches, expectation issues, billable flag) plus before/after change rows.

## `summary` (type: `string`):

Placements, distinct source pages, billable pages, counts by status and change count.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "placements": [
        {
            "id": "p1",
            "sourceUrl": "https://example.org/",
            "targetUrl": "https://iana.org/help/example-domains"
        }
    ],
    "monitorKey": "default",
    "maxSourcePages": 100,
    "confirmAbsentAfter": 2
};

// Run the Actor and wait for it to finish
const run = await client.actor("muazah/backlink-placement-receipts").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "placements": [{
            "id": "p1",
            "sourceUrl": "https://example.org/",
            "targetUrl": "https://iana.org/help/example-domains",
        }],
    "monitorKey": "default",
    "maxSourcePages": 100,
    "confirmAbsentAfter": 2,
}

# Run the Actor and wait for it to finish
run = client.actor("muazah/backlink-placement-receipts").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "placements": [
    {
      "id": "p1",
      "sourceUrl": "https://example.org/",
      "targetUrl": "https://iana.org/help/example-domains"
    }
  ],
  "monitorKey": "default",
  "maxSourcePages": 100,
  "confirmAbsentAfter": 2
}' |
apify call muazah/backlink-placement-receipts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,muazah/backlink-placement-receipts"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/0vEc0fVh4OSOK6KyM/builds/3BL1XJEt5OnEhEGXl/openapi.json