# Website Tracking, Consent, Schema and AI-Crawler Audit (`agent-harbor-llc/site-signal-audit`) Actor

Given a business home page URL, audits it and returns a ranked fix list with evidence: analytics and ad tags, consent manager and tracking before consent, structured data, AI-crawler access and SEO basics. $0.02 per fully audited page; blocked pages are free.

- **URL**: https://apify.com/agent-harbor-llc/site-signal-audit.md
- **Developed by:** [Agent Harbor LLC](https://apify.com/agent-harbor-llc) (community)
- **Categories:** SEO tools, Marketing, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 fully audited pages

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

## Website Tracking, Consent, Schema and AI-Crawler Audit

Paste in a list of pages (usually home pages) and get, for each one, a **ranked fix list** covering the things that quietly break marketing reports and local search:

- **Tracking:** Google Tag Manager containers, GA4 / Google tag / Universal Analytics IDs, Google Ads, Meta, TikTok, LinkedIn, Pinterest and Bing pixels; the same container or property installed twice (inflated pageviews), legacy Universal Analytics left on.
- **Consent:** which consent manager is present (15 vendors recognised), whether a Google Consent Mode default is set, and whether it loads before the tags.
- **Structured data:** JSON-LD that does not parse, missing `@context`/`@type`, incomplete LocalBusiness and Organization data (address, phone, hours, logo, sameAs).
- **AI crawlers:** what `robots.txt` really lets GPTBot, ClaudeBot, PerplexityBot, Google-Extended and others fetch (evaluated the way RFC 9309 specifies), `llms.txt`, and `noindex`/`nosnippet` left over from a staging launch.
- **SEO basics:** title and description length, one `<h1>`, canonical, hreflang, `lang`, image alt text, Open Graph, and an optional spot-check of internal links.

Every finding carries its **evidence** (the matched snippet or URL) and a plain-language fix. Same input, same output: there is no AI in the audit, so results are repeatable and you can diff them month to month.

### Who it is for

Agencies and in-house marketers who audit many small-business sites and want a first pass in minutes; consultants who need an evidence-backed list to send a client; anyone checking a site after a migration or a redesign.

### What it cannot see (read this)

The audit reads the HTML the server returns, plus `robots.txt` and `llms.txt`. It does **not** run a browser. Tags that a tag manager, consent manager or website builder injects with JavaScript do not appear in that HTML. In our own tests on small-business sites, a first sample of 12 (used to fix detection bugs) found a tag or pixel on 8, and a fresh sample of 11 found one on 6 of the 9 sites the audit could read (2 sites blocked or timed out the request and are reported as such). Cross-checking the misses in a real browser, most had no analytics hosts at all, but one (a Wix site in the first sample and a Tealium-managed site in the second) loaded Google Analytics only at runtime. The report names the website builder or tag manager when it can recognise one. For that reason every "not found" result is marked `verify` and worded as "not found in the static HTML": a lead to check in a browser, not a verdict. A browser-based check is planned.

Nothing here is legal advice. Consent findings are technical observations; they do not say a site complies or fails to comply with any law.

### Input

- **Pages to audit:** one URL per page, up to 100 per run. `http` and `https` only; private and internal addresses are refused.
- **Internal links to spot-check:** 0-25 same-site links per page, checked for errors (default 10; 0 turns it off).

### Output

One dataset row per page: `url`, `ok`, counts of high/medium/low findings, `topFix`, the full `fixList`, every `finding` with `evidence` and `confidence` (`confirmed` or `verify`), and an `inventory` of what was detected. A page that blocks the audit (a 403 or error page) is returned as `partial` with only its `robots.txt` and `llms.txt` evaluated, and **is not charged**. A page that could not be reached at all is reported with an error and not charged.

### Pricing

Pay per audited page (see the Pricing tab). You are never charged for a page that was blocked, unreachable or refused.

### Good to know

The Actor identifies itself as `SiteSignalAudit/0.1` and fetches one page, `robots.txt` and `llms.txt` per site (plus your chosen link sample), so it is gentle on the sites it audits.

# Actor input Schema

## `urls` (type: `array`):

One page per URL (usually the home page). http and https only.

## `linkSample` (type: `integer`):

How many same-site links on each page to check for broken responses (0 turns this off).

## Actor input object example

```json
{
  "urls": [
    {
      "url": "https://example.com"
    }
  ],
  "linkSample": 10
}
```

# Actor output Schema

## `results` (type: `string`):

One row per audited page: summary, ranked fix list and findings with evidence.

# 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 = {
    "urls": [
        {
            "url": "https://example.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("agent-harbor-llc/site-signal-audit").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 = { "urls": [{ "url": "https://example.com" }] }

# Run the Actor and wait for it to finish
run = client.actor("agent-harbor-llc/site-signal-audit").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 '{
  "urls": [
    {
      "url": "https://example.com"
    }
  ]
}' |
apify call agent-harbor-llc/site-signal-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,agent-harbor-llc/site-signal-audit"
        }
    }
}
```

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/nsycn9UJyTya0yXhn/builds/dwlwqS4I62JagAepv/openapi.json