# Store/Crawler Surface Preflight (`checksmithcats/store-crawler-surface-preflight`) Actor

Cross-check public robots.txt, sitemap, noindex, llms.txt, policy links, and contact signals from a storefront URL. Reads only public URLs; no account access.

- **URL**: https://apify.com/checksmithcats/store-crawler-surface-preflight.md
- **Developed by:** [Checksmith Cats](https://apify.com/checksmithcats) (community)
- **Categories:** E-commerce, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Store/Crawler Surface Preflight

### Summary

Cross-check robots.txt, sitemap, noindex, llms.txt, policy links, and contact signals from a public storefront URL.

### Description

Run a public URL preflight for crawler-facing and storefront surface signals. The Actor reads robots.txt, declared sitemap URLs, the homepage, one sample page when available, /llms.txt, and static policy/contact links.

The report highlights what was visible to the scanner, what could not be checked, and the exact public URLs used for reproducibility. It is designed as an informational first pass before deeper feed x page checks.

Not affiliated with Google, Bing, OpenAI, Anthropic, Common Crawl, or crawler operators. This is a diagnostic report, not platform certification or a recreation of any review decision.

Related: use Merchant Feed Preflight when you need paid feed x product-page consistency checks for prices, stock, images, and structured data.

### Good Fit

- ecommerce operators checking crawlability, policy-link, and contact signals before a feed or site update
- agencies documenting robots, sitemap, and storefront basics for a client
- developers validating static storefront signals after a theme or routing change
- QA pipelines that need JSON rows for public crawlability checks

### Not a Fit

- managed account help
- appeal writing
- policy or legal review
- managed site repair
- checkout testing
- login, CAPTCHA, or proxy bypass
- private intranet or staging URLs

### Input

- `storeUrl`: public storefront URL
- `sitemapUrl`: optional public sitemap URL

### Output

- dataset rows, one per finding
- JSON report
- HTML report
- Markdown report
- Evidence Pack with target URL, inspection date, check list, unchecked items, warnings, engine version, and non-certification note

### Pricing

Free Actor. No pay-per-event charges are configured.

### Support Boundary

Support is limited to reproducible bugs, documentation corrections, false-positive feedback, and requests for additional machine-readable checks through issue-based feedback.

### Related Checksmith Tools

- Merchant Feed Preflight - Use when crawler access checks need to be paired with feed/page product consistency.
- AI Crawler Policy Preflight - Use when the surface to inspect is robots, AI crawler tokens, llms.txt, and noindex policy.
- Security Headers Bulk QA - Use when access looks fine but launch hardening headers still need a static pass.

# Actor input Schema

## `storeUrl` (type: `string`):

Public http(s) storefront URL to check. The Actor reads public pages only.

## `sitemapUrl` (type: `string`):

Optional public sitemap URL. If omitted, the Actor uses Sitemap lines from robots.txt when present.

## Actor input object example

```json
{
  "storeUrl": "https://example.com/"
}
```

# Actor output Schema

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

No description

## `report` (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 = {
    "storeUrl": "https://example.com/"
};

// Run the Actor and wait for it to finish
const run = await client.actor("checksmithcats/store-crawler-surface-preflight").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 = { "storeUrl": "https://example.com/" }

# Run the Actor and wait for it to finish
run = client.actor("checksmithcats/store-crawler-surface-preflight").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "storeUrl": "https://example.com/"
}' |
apify call checksmithcats/store-crawler-surface-preflight --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=checksmithcats/store-crawler-surface-preflight",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/BtnHQZ1NG1M4iVg0B/builds/vJAMbeGgoVK1hLlft/openapi.json