A quick orientation: this page covers what hreflang reciprocity is, how to use the connector tool above to audit and fix broken hreflang relationships, a deep dive into why connections break, the common errors that wreck reciprocity, and how this tool compares to manual auditing.
What is an alternate page connector?
An alternate page connector is a tool that validates, visualizes, and repairs the bidirectional relationships between localized pages in a hreflang implementation. Every hreflang annotation creates a connection: page A says "my Spanish version is page B." For that connection to work, page B must say "my English version is page A" in return. This two-way requirement is called reciprocity, and it is the single most common point of failure in international SEO.
A hreflang tag generator produces correct hreflang from scratch. An alternate page connector starts with what you already have — your live site's existing hreflang annotations — and tells you what's broken. It crawls or imports your current hreflang sets, builds a relationship graph, checks every connection for reciprocity, and highlights the specific links that need fixing.
The tool above accepts hreflang data from multiple sources: paste raw HTML <link> tags, upload an XML sitemap with xhtml:link annotations, or enter URLs for the tool to fetch and parse. It produces a visual graph of page relationships, a reciprocity report listing every broken connection, and corrected hreflang output you can deploy directly. Everything runs in your browser.
How to use this alternate page connector
Follow these steps to audit your site's hreflang implementation and fix broken connections:
-
Import your existing hreflang. Choose your input method:
- Paste HTML: copy the
<link rel="alternate" ...>tags from a page's<head>section. - Upload XML sitemap: provide a sitemap file that contains
xhtml:linkannotations. - Enter URLs: list the URLs you want to check. The tool fetches each page (client-side via CORS where available, or you paste the source) and extracts the hreflang tags from the HTML.
- Bulk import: paste or upload a CSV where each row contains a URL and its declared hreflang attributes.
- Paste HTML: copy the
-
Let the tool build the relationship graph. The connector parses every hreflang annotation and constructs a directed graph. Each node is a URL; each edge is a declared alternate relationship with a locale label. The graph view shows all connections at a glance.
-
Review the reciprocity report. The tool checks every edge for a matching reverse edge. If page A declares page B as
hreflang="es"but page B doesn't declare page A ashreflang="en", the connection is flagged as non-reciprocal. The report groups issues by severity:- Missing reverse link: A references B, but B doesn't reference A at all.
- Locale mismatch: A references B as
es, B references A asfr— the locale labels disagree. - Missing self-reference: A page doesn't include itself in its own hreflang set.
-
Inspect individual connections. Click any edge in the graph or any row in the report to see the exact hreflang declarations on both sides. The tool shows what page A says about page B and what page B says about page A, side by side.
-
Apply fixes. For each broken connection, the tool suggests a correction: add the missing reverse link, correct the locale label, or add the missing self-reference. You can apply fixes individually or in bulk. The corrected hreflang output reflects all applied fixes.
-
Export corrected output. Download the fixed hreflang annotations in your preferred format. You can also export the reciprocity report as a CSV for your development team to implement the fixes in your CMS or templating system.
Deep dive: why hreflang connections break
Reciprocity failures don't happen because someone deliberately broke them. They happen because of structural problems in how multilingual sites are built and maintained.
Independent deployments. When different locale versions of a site are managed by different teams — the English site ships on Tuesday, the Spanish site ships on Thursday — the hreflang annotations can get out of sync. The English site might reference a new Spanish page that doesn't exist yet, or the Spanish site might still reference an English page that was recently deleted. The connector catches these temporal mismatches.
CMS template divergence. Some CMS platforms generate hreflang tags from a translation relationship table. If the table is updated in the English admin panel but not the Spanish one, the annotations diverge. This is especially common in WordPress multisite setups and Drupal with domain access modules.
Partial site migrations. When a site migrates from HTTP to HTTPS, from one domain to another, or from a subdirectory structure to subdomains, the hreflang annotations often reference a mix of old and new URLs. Page A (migrated) references page B at its new URL, but page B (not yet migrated) still references page A at its old URL. The connector detects protocol mismatches, domain mismatches, and path mismatches within hreflang sets.
Deleted pages without cleanup. When a page is removed from one locale but its hreflang references remain on other locale versions, those references point to 404 pages. Search engines silently drop hreflang annotations that point to non-200 URLs, which means the remaining pages lose their reciprocal connections without warning.
The graph view. The visual graph is not just decorative — it reveals structural patterns that a line-by-line audit misses. A healthy multilingual site's graph looks like a set of fully connected clusters (one cluster per page, with edges between all locale versions). Broken reciprocity shows up as clusters with missing edges. Orphan nodes indicate pages that reference alternates but are not referenced by any other page.
Canonical and hreflang interaction. A subtle failure mode: if page A has a canonical tag pointing to page C, but page A's hreflang references page B, the canonical and hreflang signals conflict. Search engines generally follow the canonical and ignore the hreflang. The connector flags pages where the canonical URL differs from the page's own URL, which suggests the hreflang annotations on that page may be ignored.
Common errors and how to fix them
Here are the five reciprocity errors this tool catches that auditors encounter most frequently.
-
One-way hreflang declarations. Page A lists page B as an alternate, but page B's hreflang set doesn't mention page A. Google silently ignores the one-way link. The fix: add page A to page B's hreflang set with the correct locale. The connector generates the exact
<link>tag to add. -
Missing self-references. A page lists its alternates but doesn't include itself. The hreflang spec requires every page to appear in its own alternate set. Without the self-reference, the entire set is technically malformed. The connector detects missing self-references and adds them to the corrected output.
-
Locale label mismatches. Page A references page B as
hreflang="es", but page B references page A ashreflang="en-US"instead ofhreflang="en". The inconsistency doesn't break reciprocity directly — they're different attributes — but it signals sloppy implementation that likely has other issues. The connector reports locale inconsistencies across the pair. -
Circular x-default references. If two pages both declare themselves as x-default for the same translation group, search engines can't decide which is the true fallback. The connector detects multiple x-default declarations within a translation group and asks you to designate one.
-
Stale references to redirected or deleted pages. If page A references page B but page B now redirects to page C, the hreflang connection between A and B is effectively broken — search engines follow the redirect and find that page C's hreflang set may not reference page A. The connector flags URLs that appear in hreflang declarations but not in the set of known live pages.
How this tool is different
Four things set this alternate page connector apart from generic hreflang validators:
- Graph-based visualization. Instead of a flat list of errors, you see the relationship structure visually. Broken connections, orphan pages, and incomplete clusters are immediately obvious in the graph view.
- Bidirectional validation. Most validators check hreflang syntax on one page at a time. This connector checks relationships between pages — it verifies that every declared connection is reciprocated, which requires analyzing pairs, not individual tags.
- Fix generation. The tool doesn't just tell you what's broken — it produces the corrected hreflang markup. Export the fixed annotations and hand them to your development team as a ready-to-deploy specification.
- Audit-ready reporting. The reciprocity report exports as a CSV with columns for source URL, target URL, declared locale, issue type, and suggested fix. Drop it into a project tracker or share it with a client as a structured audit deliverable.
Everything runs in your browser. There is no server that sees your URLs or hreflang data, no account required, and no limit on the number of pages you can audit. The tool is a premium resource for international SEO professionals debugging and maintaining multilingual hreflang implementations.