Public Localization & International SEO Signal Agent
Pricing
Pay per event
Public Localization & International SEO Signal Agent
Analyze public pages for hreflang, x-default, HTML language, canonical alignment, language switcher links, locale matrix evidence, and international SEO risks.
Analyze public pages for international SEO signals: hreflang, x-default, HTML language, content language, Open Graph locale, canonical alignment, language switcher links, locale matrix evidence, risk labels, and stable change hashes.
This Actor is built for AI agents, SEO teams, localization teams, site migration checks, market researchers, and report generators that need compact, source-linked localization evidence without running a browser or crawling an entire website.
What It Returns
hreflangalternate links with locale, language, region, URL, same-site status, and source evidence.x-default,html lang,content-language,og:locale, andog:locale:alternatesignals.- Language switcher links inferred from visible anchors and locale-like URL paths.
- A locale matrix summary with detected language count, region count, same-site alternates, external alternates, and current page locale hints.
- Risk labels for missing
x-default, duplicate locale declarations, missing HTML language, external alternates, and canonical/hreflang alignment issues. missingFields,confidenceScore,completenessScore,localizationScore, recommended next action, evidence snippets, evidence URLs, and a stablelocalizationHash.
Pricing Behavior
The Actor uses pay-per-event pricing and only charges the useful result event when it finds useful public localization SEO evidence.
It does not charge the useful event for:
- invalid or private-network URLs;
- failed fetches;
- pages with no useful localization signals;
focusLocalesmisses;- unchanged records when you pass a previous
localizationHash.
apify-default-dataset-item is intentionally not used.
Scope And Safety
- Public HTTP/HTTPS pages only.
- Private-network hosts, credentials, query strings, fragments, path parameters, and token-like account paths are rejected.
- JavaScript is not executed.
- Sitemap files, Google results, rankings, screenshots, external assets, and alternate pages are not fetched.
- Alternate URLs are recorded as evidence from the current page only.
- Output is evidence-based and should be reviewed before making production SEO changes.
Example Input
{"pageUrls": ["https://www.cloudflare.com"],"focusLocales": ["en","fr","de","ja","zh"],"requestTimeoutSecs": 20}
Best Use Cases
- Check whether a public homepage or localized page declares a healthy
hreflangmatrix. - Find missing
x-defaultor canonical/hreflang alignment risks before migration. - Feed AI agents structured localization evidence instead of raw HTML.
- Monitor international SEO signal changes without paying for unchanged results.