# SEO Indexability Audit: Robots, Noindex & Canonical Evidence (`technicaldost/static-indexability-audit`) Actor

Audit public URLs for crawl restrictions, noindex directives, redirects and conflicting canonicals. Evidence-linked JSON with clear unknowns. No browser or Google-indexed claims.

- **URL**: https://apify.com/technicaldost/static-indexability-audit.md
- **Developed by:** [Technical Dost Solutions](https://apify.com/technicaldost) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 eligible url analyses

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

## SEO Indexability Audit: Robots, Noindex & Canonical Evidence

Audit an explicit list of public URLs for common **static technical indexing obstacles**. Get the observed HTTP status, redirect chain, robots.txt crawl permission, applicable meta and HTTP robots directives, canonical declarations, and specific issues in structured JSON.

This is a focused preflight for SEO consultants, migration teams, content operations and developers. It is **not a Google index checker**, a complete SEO score, a site discovery crawler or a rendered-browser audit.

### Pricing

$0.50 per 1,000 eligible URL analyses. $0.005 per run. Standard-run platform usage is included. Only successful eligible rows in the default dataset trigger the result charge. Error, not-found, skipped and robots-denied diagnostics do not trigger a result charge. The run fee, where listed, still applies to empty or failed runs. Memory is limited to 256–512 MB. Set a maximum run cost in Apify; inspect the actual dataset and run charge breakdown after an interruption. Input item limits bound work and do not replace the run spending limit.

### What makes the output useful

- Separate “search crawler disallowed” from “noindex detected.” Robots.txt blocking does not prove a page is absent from an index.
- Keep the evidence behind each issue: raw meta directives, X-Robots-Tag values, canonical declarations and redirect hops.
- Report conflicting directives and multiple canonical targets without pretending to know which canonical a search engine selected.
- Distinguish a fetched empty/non-HTML response from an upstream failure. Failed requests never become a clean audit.
- Export qualifying fetched audits to the dataset and preserve all other diagnostics in the key-value store.

### Input example

```json
{
  "urls": ["https://example.com/"],
  "maxItems": 20,
  "searchBot": "googlebot",
  "requestTimeoutSecs": 15,
  "failOnFetchError": true
}
```

| Field | Behavior |
| --- | --- |
| `urls` | 1–200 explicit public HTTP(S) URLs. Fragments removed and exact normalized duplicates removed. No URL discovery. |
| `maxItems` | Global maximum of 1–200 unique URLs; default 20. Excess URLs are recorded as truncation. |
| `searchBot` | `googlebot` or `bingbot`; default Googlebot. Changes the directives evaluated, not the request user agent. |
| `requestTimeoutSecs` | 3–30 seconds for each DNS resolution and each HTTP request; default 15. A redirect chain can involve several requests. |
| `failOnFetchError` | Default true: any fetch error makes the run fail, retaining completed rows and summary. False permits partial runs; zero completed audits always fail. |

Unknown inputs fail validation rather than being silently ignored.

### Output and interpretation

The default dataset contains only fetched audits with HTTP 200, nonnull evidence, and both `robots.crawlerAllowed` and `robots.searchBotAllowed` equal to true. Useful noindex, canonical-review and non-HTML HTTP diagnostics remain eligible when those conditions hold. `.actor/output_schema.json` links the dataset, `RUN_DIAGNOSTICS` and `RUN_SUMMARY` in the default key-value store. The item JSON Schema is `dataset-item.schema.json`; the Console table is defined in `.actor/dataset_schema.json`.

Main fields:

- `inputUrl`, `finalUrl`, `observedAt`, `httpStatus`, `redirects`.
- `assessment`: the leading diagnosis, listed below.
- `robots`: availability and status of robots.txt, crawl permissions for this Actor and the selected search crawler, matching rule line where available, and declared crawl delay.
- `evidence`: content type, title, raw relevant meta/HTTP directives, combined applicable directives, canonical targets and static meta refresh declarations.
- `issues`: issue code, severity and a concrete explanation. Multiple issues may coexist even when the main assessment shows only one.
- `renderedJavaScript: false` and `googleIndexStatus: "not_checked"` make the scope explicit.

| Assessment | Meaning |
| --- | --- |
| `no_static_blocker_found` | No supported static blocker found in a 200 HTML response. **Not proof of indexing or full indexability.** |
| `noindex_detected` | Applicable static meta or HTTP noindex directive observed. |
| `search_crawl_disallowed` | Robots.txt restricts the selected search crawler. This is a crawl restriction, not a reliable index-exclusion method. |
| `http_status_issue` | Final resource did not return HTTP 200. |
| `review_required` | Canonical or meta-refresh evidence needs review. |
| `non_html_requires_review` | HTTP evidence inspected; non-HTML content may still be indexable. |
| `not_fetched_robots_disallowed` | This Actor's crawler is disallowed. The page was not fetched and page-level evidence is null. |

`RUN_DIAGNOSTICS.rows` preserves the complete non-200, skipped and robots-denied audit rows without adding them to the default dataset. `RUN_DIAGNOSTICS.failures` preserves thrown audit failures; these also appear in `RUN_SUMMARY.failures`. A robots-denied diagnostic row is a completed permission check, not a completed HTML fetch. `RUN_SUMMARY.audited` counts all completed audit rows, `datasetRowsSubmitted` counts qualifying rows handed to resolved SDK push calls, not verified saved rows or charged events, and `diagnosticRows` counts excluded rows. Diagnostic-only runs can succeed with an empty dataset. The JavaScript synthetic-event push returns no saved/charged count, so a spending-limit or storage interruption requires inspection of the actual dataset and run charge breakdown. Diagnostics are checkpointed as they are produced, so an unrelated later storage failure does not discard earlier saved diagnostics. The existing `failOnFetchError` behavior still applies to thrown audit failures. Canonical URLs are never fetched. No messages, alerts or schedules are created by this Actor; use your own Apify task scheduling and integrations.

### Boundaries and responsible operation

Only use URLs you are permitted to audit. Public accessibility is not a grant of redistribution rights. This Actor never logs in, submits forms, follows canonical targets, executes JavaScript, accepts cookies, bypasses access controls or uses proxy rotation.

- Requests use `TechnicalDostIndexabilityBot/1.0`, not a spoofed Googlebot.
- Robots.txt is checked before each page/redirect destination. 404/410 allow crawling; unavailable/error/HTML robots responses fail closed. Cross-origin robots redirects are held for review.
- Declared crawler delays up to 30 seconds are respected. Higher delays stop that URL. Otherwise a minimum one-second delay precedes each page request. Processing is sequential.
- No retry on 401, 403, 407, 429 or server errors. No attempts to evade blocks.
- DNS responses are checked and pinned per request; any private/special-use address rejects the target. Only standard HTTP(S) ports and credential-free URLs are accepted.
- Maximum five page redirects, five same-origin robots redirects, 512,000 robots bytes and 2,000,000 page bytes. Compressed responses despite the identity request are rejected.
- Only static UTF-8 HTML and HTTP metadata are inspected. HTTP Link canonical relations use exact relation tokens; links declaring a different anchor context are ignored. No rendering, canonical-target verification, sitemap membership, Search Console, live Google index status, soft-404 detection, hreflang validation, mobile rendering or Core Web Vitals.
- Complex or nonstandard directives may require manual review. No arbitrary SEO score, ranking prediction or guaranteed indexability claim is produced.

### Source references

- [Google robots meta and HTTP specifications](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag)
- [Apify output schema](https://docs.apify.com/actors/development/actor-definition/output-schema)
- [Apify dataset schema validation](https://docs.apify.com/storage/dataset-schema/validation)

This product is independent of Google, Bing and the audited websites.

# Actor input Schema

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

Explicit HTTP(S) page URLs, not domains for discovery. Maximum 200. No credentials or private network targets.

## `maxItems` (type: `integer`):

Global cap after fragment removal and deduplication. Excess input URLs are reported as truncated.

## `searchBot` (type: `string`):

Evaluate this crawler’s robots and metadata directives. Requests use the transparent TechnicalDostIndexabilityBot user agent.

## `requestTimeoutSecs` (type: `integer`):

Each DNS resolution and request is independently bounded. Redirect chains can use several requests.

## `failOnFetchError` (type: `boolean`):

Recommended. Error details go to RUN_SUMMARY; successful rows remain in dataset. False permits partial success, but zero completed audits always fail.

## Actor input object example

```json
{
  "urls": [
    "https://example.com/"
  ],
  "maxItems": 20,
  "searchBot": "googlebot",
  "requestTimeoutSecs": 15,
  "failOnFetchError": true
}
```

# Actor output Schema

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

Qualifying fetched audits only: HTTP 200, nonnull evidence and both crawler permissions allowed. Not proof of search engine indexing.

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

Requested/selected counts, truncation, completed audits, datasetRowsSubmitted, diagnosticRows and exact failed URLs.

## `diagnostics` (type: `string`):

Non-200, skipped and robots-denied rows plus thrown audit failures. These do not trigger the synthetic default-dataset item event. A start fee, storage and other platform charges may still apply.

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

// Run the Actor and wait for it to finish
const run = await client.actor("technicaldost/static-indexability-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": ["https://example.com/"] }

# Run the Actor and wait for it to finish
run = client.actor("technicaldost/static-indexability-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": [
    "https://example.com/"
  ]
}' |
apify call technicaldost/static-indexability-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,technicaldost/static-indexability-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/bj66ZbPnhLi2WVNBc/builds/KqsucbT6EnSrhq7N3/openapi.json