Hreflang Checker & International SEO Auditor

Check public URLs for hreflang tags, reciprocal links, locale coverage and cluster consistency, with optional repeat-run drift monitoring for international SEO.

Quick start

Start with this working example and replace the target values with your own:

{
  "urls": [
    "https://www.wikipedia.org"
  ],
  "validateReciprocity": true,
  "previousSnapshots": {}
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• urls — Localized page URLs: Public pages whose hreflang locale clusters and international SEO coverage should be analyzed.
• previousSnapshots — Previous locale snapshots: Optional prior snapshots keyed by input or final URL to detect added or removed locales and canonical drift.
• validateReciprocity — Validate reciprocal hreflang: Fetch alternate locale pages and check whether they link back to the source cluster.
• maxAlternatesPerPage — Maximum alternate pages: Maximum alternate locale pages fetched for reciprocity evidence per source page.
• maxUrls — Maximum source pages: Maximum localized source pages processed in one run.
• concurrency — Concurrency: Maximum source pages processed in parallel.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include dataset.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.003500 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Detailed documentation

Give public URLs. Validate hreflang alternates, reciprocity, canonicals and locale coverage, returning structured international SEO issues.

Turn hreflang validation into international SEO intelligence. This Actor maps the locale cluster around each page, checks reciprocal alternate links, evaluates canonical consistency, measures market coverage and compares the cluster with previous snapshots to detect expansion or regression.

Why use this Actor

Global sites rarely fail because one tag is missing in isolation. They fail because locale clusters become inconsistent: one country disappears, reciprocal links break, canonicals point elsewhere, x-default is lost or a new market launches without complete technical coverage. This Actor gives SEO teams and agents one decision-ready result per source page.

Key features

• Extract hreflang alternates and x-default.
• Validate language and language-region codes.
• Detect duplicate locales and missing self-reference.
• Check canonical consistency with the source page.
• Optionally fetch alternate locale pages and measure reciprocity.
• Calculate clusterHealthScore, marketCoverageScore and marketOpportunityScore.
• Compare reusable snapshots to detect added and removed locales.
• Surface international expansion or localization regressions with agentAction.
• HTTP-first 256 MB runtime with no Search Console or paid SEO API.

Input

Provide localized public page URLs. Reciprocity checks can be enabled or capped for predictable runtime. Add previous snapshots for recurring market-coverage monitoring.

{"urls":["https://www.wikipedia.org"],"validateReciprocity":true,"maxAlternatesPerPage":12}

Output

Each page produces locale counts, locale codes, x-default evidence, reciprocity percentage, canonical evidence, coverage and opportunity scores, snapshot changes, added/removed locales and a recommended action.

Example

If a previous cluster contained en-us, de-de and fr-fr and the current run loses de-de, the result can surface removedLocales, lower cluster health and recommend REVIEW_LOCALE_COVERAGE_DRIFT.

Use cases

International ecommerce, global publishers, SaaS localization, market launches, country expansion, multilingual migrations, agency audits, weekly global SEO monitoring and AI-agent market coverage checks.

Pricing

Pay per result. The base configured price is $0.0035 USD per localized source-page result, with tiered discounts where supported.

Limitations

Analysis uses public HTML and optional alternate-page fetches. Very large locale clusters are capped for predictable runtime. Results describe technical international SEO evidence and do not guarantee rankings, indexing or commercial demand in a market.