# Hreflang Cluster Check (`garnet_precipice/my-actor`) Actor

Audit hreflang return links and language mappings from existing crawl data before multilingual launches or migrations. JSON input; up to 1,000 pages per run. Missing pages are marked unverified. $1 per 1,000 page results plus a small start fee. No live crawling.

- **URL**: https://apify.com/garnet\_precipice/my-actor.md
- **Developed by:** [Garnet Tools](https://apify.com/garnet_precipice) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 page audits

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?

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 Check

Check return links and language mappings using annotations from your existing crawler. This Actor accepts JSON and does not fetch websites or call AI models.

### When to use it

Run a repeatable check before adding a language, launching a multilingual site, or migrating localized URLs. Supply the complete language cluster from your crawl or build pipeline to catch one-sided annotations and inconsistent mappings.

### Input

Supply `pages`, an array of objects containing `url` and `alternates`, where each alternate has `hreflang` and `href`. Include all language variants for complete checks. Missing target records are unverified, not broken links.

```json
{"pages":[{"url":"https://example.com/en","alternates":[{"hreflang":"en","href":"https://example.com/en"},{"hreflang":"fr","href":"https://example.com/fr"}]},{"url":"https://example.com/fr","alternates":[{"hreflang":"fr","href":"https://example.com/fr"}]}]}
```

This synthetic example detects a missing return link from the French page, plus inconsistent mappings. It is not a customer case.

Limits: 1–1000 pages, 100 annotations per page, 5 MB input. URLs must be absolute HTTP(S), at most 4096 characters after normalization, with no credentials or fragments.

### Output

The default dataset contains one row per supplied page. The OUTPUT key-value record contains summary and results. Each page includes status, issueCounts, issues, and detailsTruncated.

Findings: missing\_return\_link, missing\_self\_reference, duplicate\_language, invalid\_language\_syntax, invalid\_alternate\_url, cluster\_mapping\_mismatch, target\_not\_in\_input, no\_annotations. Empty annotations alone are informational, not an SEO error. Duplicate language labels retain the first mapping for subsequent checks.

At most 100 detailed findings per page and 1000 overall are retained. Total counts and page statuses remain accurate when details are truncated. Split large inputs into complete language clusters for more detail.

### Pricing

$0.001 per page result ($1 per 1,000 results), plus $0.00005 per Actor start at up to 1 GB memory. The start fee scales with higher memory. Platform usage is included in these event prices. At 1 GB, a successful 100-page run producing 100 results costs $0.10005; the two-page example costs $0.00205. These are list-price calculations, not evidence of customer payments. Check the Pricing tab for current rates and set a maximum total charge before running.

### Scope

This checks supplied annotations, not live website state. It does not check status codes, redirects, canonicals, content equivalence, assigned ISO codes or indexing. Language labels receive syntax checks only. A checked status is not SEO certification.

See [Google localized versions documentation](https://developers.google.com/search/docs/specialty/international/localized-versions) for reciprocal annotation requirements.

# Actor input Schema

## `pages` (type: `array`):

1–1000 objects: url and alternates \[{hreflang,href}]. Include every language variant for complete return-link checks. URLs are not fetched.

## Actor input object example

```json
{
  "pages": [
    {
      "url": "https://example.com/en",
      "alternates": [
        {
          "hreflang": "en",
          "href": "https://example.com/en"
        },
        {
          "hreflang": "fr",
          "href": "https://example.com/fr"
        }
      ]
    },
    {
      "url": "https://example.com/fr",
      "alternates": [
        {
          "hreflang": "fr",
          "href": "https://example.com/fr"
        }
      ]
    }
  ]
}
```

# Actor output Schema

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

One record per supplied page, with status, findings and truncation flags.

## `report` (type: `string`):

Summary and page findings for supplied annotations only.

# 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 = {
    "pages": [
        {
            "url": "https://example.com/en",
            "alternates": [
                {
                    "hreflang": "en",
                    "href": "https://example.com/en"
                },
                {
                    "hreflang": "fr",
                    "href": "https://example.com/fr"
                }
            ]
        },
        {
            "url": "https://example.com/fr",
            "alternates": [
                {
                    "hreflang": "fr",
                    "href": "https://example.com/fr"
                }
            ]
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("garnet_precipice/my-actor").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 = { "pages": [
        {
            "url": "https://example.com/en",
            "alternates": [
                {
                    "hreflang": "en",
                    "href": "https://example.com/en",
                },
                {
                    "hreflang": "fr",
                    "href": "https://example.com/fr",
                },
            ],
        },
        {
            "url": "https://example.com/fr",
            "alternates": [{
                    "hreflang": "fr",
                    "href": "https://example.com/fr",
                }],
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("garnet_precipice/my-actor").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 '{
  "pages": [
    {
      "url": "https://example.com/en",
      "alternates": [
        {
          "hreflang": "en",
          "href": "https://example.com/en"
        },
        {
          "hreflang": "fr",
          "href": "https://example.com/fr"
        }
      ]
    },
    {
      "url": "https://example.com/fr",
      "alternates": [
        {
          "hreflang": "fr",
          "href": "https://example.com/fr"
        }
      ]
    }
  ]
}' |
apify call garnet_precipice/my-actor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,garnet_precipice/my-actor"
        }
    }
}
```

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/C3CDkRlTLFQn0BNn4/builds/RIjDaFBvFiUa9vyIg/openapi.json