# Hreflang Cluster Auditor (`junipr/hreflang-cluster-auditor`) Actor

Audit hreflang clusters, language and region codes, reciprocal return links, x-default coverage, and canonical conflicts.

- **URL**: https://apify.com/junipr/hreflang-cluster-auditor.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.90 / 1,000 hreflang cluster auditor page auditeds

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/platform/actors/running/actors-in-store#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

## Hreflang Cluster Auditor

### Store Positioning

**Store title:** Hreflang Cluster Auditor

**Short description:** Audit hreflang clusters, language and region codes, reciprocal return links, x-default coverage, and canonical conflicts.

**SEO title:** Hreflang Cluster Auditor — technical SEO, web, and domain audit

**SEO description:** Audit hreflang clusters, language and region codes, reciprocal return links, x-default coverage, and canonical conflicts. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.

**Categories:** SEO\_TOOLS, ECOMMERCE

**Keywords:** hreflang, cluster, auditor, web/domain audit

### Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

- Tier: W1 — Web/domain audit
- Primary event: `page-audited` at $0.00490 base
- Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

- `actor-start`: base $0.00500, GOLD $0.00400. Hreflang Cluster Auditor: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `page-audited`: base $0.00490, GOLD $0.00392. Hreflang Cluster Auditor: charged when page audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `rule-parsed`: base $0.00372, GOLD $0.00298. Hreflang Cluster Auditor: charged when rule parsed is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `finding-emitted`: base $0.00372, GOLD $0.00298. Hreflang Cluster Auditor: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `audit-report-generated`: base $0.05000, GOLD $0.04000. Hreflang Cluster Auditor: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

### Public Task Concepts

- Audit Hreflang Cluster controls on a capped public sample
- Find high-priority Hreflang Cluster issues before release
- Validate Hreflang Cluster evidence from supplied pages
- Prioritize Hreflang Cluster fixes with severity and proof
- Export Hreflang Cluster QA rows for client review

Audit hreflang clusters, language and region codes, reciprocal return links, x-default coverage, and canonical conflicts.

### Inputs

This actor accepts the locked fields for actor 255: startUrls, sitemapUrls, htmlInputs, allowedDomains, maxPages, maxDepth, validateReturnLinks, checkAlternateStatus, requireSelfReference, requireXDefault, includeSitemapAlternates, requestDelayMs, timeoutMs. URL and sitemap inputs use production fetch paths; supplied HTML, JSON, header, or XML records are offline inputs for controlled runs.

### Output

Dataset rows use the approved fields: sourceUrl, canonicalUrl, hreflang, alternateUrl, alternateStatus, clusterId, clusterSize, languageCodeValid, regionCodeValid, hasSelfReference, hasReturnLink, xDefaultPresent, duplicateLanguageTarget, canonicalConflict, issueCode, severity, recommendation. The actor also writes these local report artifacts: hreflang-cluster-audit.md, hreflang-page-results.csv, hreflang-clusters.json, missing-return-links.csv, invalid-hreflang-codes.csv, x-default-coverage.json.

### Public source provenance

Bounded reciprocal hreflang snapshot from https://www.apple.com/ and https://www.apple.com/fr/, observed 2026-07-12. Both pages published en-US and fr-FR alternates; the bounded pair did not include x-default.

### Local run

```bash
npm test
APIFY_LOCAL_STORAGE_DIR=storage CRAWLEE_STORAGE_DIR=storage npm run smoke
```

### Billing and cost controls

This actor uses pay-per-event pricing. It charges `actor-start`, then `page-audited` before each dataset row, and `audit-report-generated` before report artifacts. `maxChargeUsd` is enforced locally and in Apify runs; when the limit is reached, uncharged rows and reports are withheld. Platform usage pass-through remains off.

# Actor input Schema

## `startUrls` (type: `array`):

Public or supplied values for startUrls; keep first runs bounded.

## `sitemapUrls` (type: `array`):

Public or supplied values for sitemapUrls; keep first runs bounded.

## `htmlInputs` (type: `array`):

Bounded supplied htmlInputs records for deterministic saved-page analysis.

## `allowedDomains` (type: `array`):

Public or supplied values for allowedDomains; keep first runs bounded.

## `maxPages` (type: `number`):

Maximum maxPages processed in one bounded run.

## `maxDepth` (type: `number`):

Maximum maxDepth processed in one bounded run.

## `validateReturnLinks` (type: `boolean`):

Include or validate validateReturnLinks when enabled.

## `checkAlternateStatus` (type: `boolean`):

Include or validate checkAlternateStatus when enabled.

## `requireSelfReference` (type: `boolean`):

Include or validate requireSelfReference when enabled.

## `requireXDefault` (type: `boolean`):

Include or validate requireXDefault when enabled.

## `includeSitemapAlternates` (type: `boolean`):

Include or validate includeSitemapAlternates when enabled.

## `requestDelayMs` (type: `number`):

Maximum requestDelayMs processed in one bounded run.

## `timeoutMs` (type: `number`):

Maximum timeoutMs processed in one bounded run.

## `maxChargeUsd` (type: `number`):

Stop before paid output would exceed this pay-per-event PPE limit.

## Actor input object example

```json
{
  "startUrls": [],
  "sitemapUrls": [],
  "htmlInputs": [
    {
      "sourceUrl": "https://www.apple.com/",
      "html": "<title>Apple</title><link rel=\"canonical\" href=\"https://www.apple.com/\"><link rel=\"alternate\" href=\"https://www.apple.com/\" hreflang=\"en-US\"><link rel=\"alternate\" href=\"https://www.apple.com/fr/\" hreflang=\"fr-FR\">"
    },
    {
      "sourceUrl": "https://www.apple.com/fr/",
      "html": "<title>Apple (France)</title><link rel=\"canonical\" href=\"https://www.apple.com/fr/\"><link rel=\"alternate\" href=\"https://www.apple.com/\" hreflang=\"en-US\"><link rel=\"alternate\" href=\"https://www.apple.com/fr/\" hreflang=\"fr-FR\">"
    }
  ],
  "allowedDomains": [
    "www.apple.com"
  ],
  "maxPages": 2,
  "maxDepth": 0,
  "validateReturnLinks": true,
  "checkAlternateStatus": false,
  "requireSelfReference": true,
  "requireXDefault": false,
  "includeSitemapAlternates": true,
  "requestDelayMs": 0,
  "timeoutMs": 10000,
  "maxChargeUsd": 1
}
```

# 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("junipr/hreflang-cluster-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("junipr/hreflang-cluster-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 junipr/hreflang-cluster-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/hreflang-cluster-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/WttLcYzu3vqsFj9XB/builds/cb9qjdnbDxxAmMCEu/openapi.json