# Website & AI Crawler Audit: Public Page Signals (`hirepulse/ad-waste-and-ai-leak-auditor`) Actor

Inspect homepage HTML, technology markers, robots.txt and llms.txt. Return HTTP evidence and observed public emails. Scores are static checklist heuristics, not measured conversion loss, AI rankings or verified decision-maker identity.

- **URL**: https://apify.com/hirepulse/ad-waste-and-ai-leak-auditor.md
- **Developed by:** [HirePulse](https://apify.com/hirepulse) (community)
- **Categories:** E-commerce, Lead generation, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 store leak audits

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 & AI Crawler Audit: Public Page Signals

Inspect public homepage HTML and crawler files for a reproducible website review.
The Actor returns HTTP evidence, observed platform/marketing markers, robots.txt
homepage rules, llms.txt observations, homepage Product/Offer JSON-LD and published
homepage email addresses. It does not run a browser or query ChatGPT/Perplexity.

### Small first run

```json
{"domains":["linear.app"],"checkAiShoppingReadiness":true,"checkConversionAndTechLeaks":true,"checkContactsAndHiring":true}
```

Supply explicit targets through the API. Console prefill is an editable example;
missing input does not start checks against unrelated default websites. An audit
fetches the homepage and, when enabled, robots.txt and llms.txt. Only public HTTPS
targets are fetched. Local/private IPs, mixed public/private DNS answers, unsafe
redirects and oversized responses are rejected; certificate checks remain enabled.

### Interpret the result

`completed_verified` is retained for compatibility and means that static HTTP
observations were obtained. Read `verification_scope`, `http_evidence`, `score_type`
and `limitations`. The legacy `bleeding_funnel_score` field is a local checklist
heuristic, not measured revenue loss. `missing_revenue_pixels` lists markers not
observed in that fetched homepage; they may load after JavaScript or consent.
Next.js by itself is not evidence that a site is an online store. Product-page
schema, checkout, conversion rates and AI answer visibility are not verified.
Crawler-file fetch failures produce unknown access values, not fabricated bans.

`decision_maker_contacts.public_emails` contains only addresses found in the fetched
homepage and can be empty. No email patterns or decision-maker identities are
invented. Hiring and DNS data are not collected by this Actor. `cold_outreach_pitch`
is an optional draft for owner review; no message is sent and no video recording
or AI-assistant assessment is claimed. `workspaceStateKey` is reserved and does not
enable history, schedules or change detection. Disable an input check to skip it.

### Pricing and failures

One delivered public-page audit uses the existing `store-leak-audit` event. Standard
free-plan event price is $0.025; paid-plan discounts and startup events are shown
in the live Pricing tab. A $0.03 maximum event charge covers one audit at this
price; platform charges may apply according to the account plan. Unavailable or
unsafe targets produce a diagnostic row without an audit-result event. A run with
no reachable target fails with SOURCE_UNAVAILABLE rather than pretending that an
audit succeeded. Partial failures and spending limits are explicit in OUTPUT.

The service does not use external paid data providers. Coverage is limited to the
public pages fetched during the run. No revenue, ranking, completeness or fixed
runtime guarantee is made. Output is available as JSON, CSV or Excel through Apify.

# Actor input Schema

## `domains` (type: `array`):

Required explicit public domains or website URLs, up to 200. No hidden example targets are audited when API input is missing.

## `checkAiShoppingReadiness` (type: `boolean`):

Inspect robots.txt homepage rules, llms.txt and homepage Product/Offer JSON-LD. Does not query AI assistants or measure rankings; missing static signals are not proof of site-wide absence.

## `checkConversionAndTechLeaks` (type: `boolean`):

Report technology and optional marketing markers observed in static homepage HTML. Does not test checkout, browser consent states, server-side tracking or revenue loss.

## `checkContactsAndHiring` (type: `boolean`):

Return only email addresses found in fetched homepage HTML. No generated addresses, decision-maker verification, hiring lookup, DNS check or message delivery.

## `workspaceStateKey` (type: `string`):

Reserved compatibility field. This Actor does not persist change history or emit delta-monitoring events.

## Actor input object example

```json
{
  "domains": [
    "linear.app"
  ],
  "checkAiShoppingReadiness": true,
  "checkConversionAndTechLeaks": true,
  "checkContactsAndHiring": true,
  "workspaceStateKey": "default-agency-radar"
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# 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 = {
    "domains": [
        "linear.app"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hirepulse/ad-waste-and-ai-leak-auditor").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 = { "domains": ["linear.app"] }

# Run the Actor and wait for it to finish
run = client.actor("hirepulse/ad-waste-and-ai-leak-auditor").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 '{
  "domains": [
    "linear.app"
  ]
}' |
apify call hirepulse/ad-waste-and-ai-leak-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hirepulse/ad-waste-and-ai-leak-auditor"
        }
    }
}
```

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/p2wfpTPuSKhm3fvq2/builds/MOHnsrsyxKkd0eGCq/openapi.json