# Robots.txt & Sitemap SEO Auditor (`quanmatrix/robots-sitemap-seo-auditor`) Actor

Audit robots.txt and XML sitemaps, discover crawl URLs, sample page availability, and flag technical SEO issues in structured output with a simple 0-100 readiness score.

- **URL**: https://apify.com/quanmatrix/robots-sitemap-seo-auditor.md
- **Developed by:** [Rafael Barreto Haddad](https://apify.com/quanmatrix) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.43 / 1,000 results

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?

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

## Robots.txt & Sitemap SEO Auditor

Audit the crawl-discovery layer of public websites in one structured run. The Actor checks `robots.txt`, follows declared or fallback XML sitemaps, counts discovered URLs, samples page availability, and returns issue flags plus a simple readiness score.

### Why use this Actor

Robots and sitemap problems are easy to overlook and tedious to inspect across many domains. This Actor turns those checks into consistent JSON records that can feed SEO audits, monitoring jobs, agency reports, or technical QA pipelines.

### Key features

- Checks public `robots.txt` availability and extracts user-agent, allow, disallow, and sitemap directives.
- Follows sitemap indexes and URL sets up to configurable limits.
- Falls back to `/sitemap.xml` when no sitemap is declared in `robots.txt`.
- Counts discovered page URLs and optionally samples their HTTP availability.
- Reports broken/invalid sitemap conditions and missing crawl-discovery signals.
- Produces a 0-100 heuristic score for quick triage.
- Blocks localhost, private-network targets, and unsafe redirects.

### Input

```json
{
  "domains": ["https://example.com"],
  "maxSitemapsPerDomain": 10,
  "maxUrlsPerDomain": 200,
  "checkSampleUrls": 5
}
```

### Output

One dataset item is produced per domain with the base URL, robots status and directives, sitemap reports, discovered URL count, sampled URL results, issue list, and score.

### Example

```json
{
  "baseUrl": "https://example.com",
  "ok": true,
  "score": 65,
  "robots": {"status": 200, "declaredSitemaps": []},
  "discoveredUrlCount": 1,
  "issues": ["sitemap_unavailable_or_invalid"]
}
```

### Use cases

- Technical SEO audits across many domains
- Website-launch QA
- Agency site-health checks
- Sitemap discovery for downstream crawlers
- Monitoring crawl-discovery regressions
- Preflight checks before larger scraping or indexing workflows

### Pricing

Pay per result. The current price is **$0.0005 per audited domain**, or **$0.50 per 1,000 results**.

### Limitations

- The score is a practical heuristic, not a search-engine ranking score.
- Very large sitemap estates are intentionally capped by the input limits.
- The Actor does not emulate Googlebot or guarantee how a search engine will interpret directives.
- Authentication, CAPTCHAs, WAF rules, or temporary upstream failures can affect results.
- Only public HTTP/HTTPS targets are supported.

### Responsible use

Use the Actor for public websites you are permitted to inspect. It does not bypass authentication or private-network controls.

# Actor input Schema

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

Public HTTP/HTTPS websites to audit.

## `maxSitemapsPerDomain` (type: `integer`):

Maximum number of XML sitemap files or sitemap indexes to fetch for each website.

## `maxUrlsPerDomain` (type: `integer`):

Maximum number of page URLs to collect from XML sitemaps for each website.

## `checkSampleUrls` (type: `integer`):

Number of discovered sitemap URLs to fetch as a lightweight availability sample.

## Actor input object example

```json
{
  "domains": [
    "https://www.python.org"
  ],
  "maxSitemapsPerDomain": 10,
  "maxUrlsPerDomain": 200,
  "checkSampleUrls": 5
}
```

# Actor output Schema

## `results` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("quanmatrix/robots-sitemap-seo-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("quanmatrix/robots-sitemap-seo-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 '{}' |
apify call quanmatrix/robots-sitemap-seo-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quanmatrix/robots-sitemap-seo-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/cH9xlaFEyRX9i32sS/builds/mHQLb2cWY8y6oYFwV/openapi.json