Technical SEO check
Missing reciprocal hreflang
A reciprocal hreflang problem is a relationship failure. Reporting only one URL hides which side and which language mapping needs repair.
Complete evidence✦Explicit boundaries✦Verifiable outcomes
What this finding means
Page A declares page B as a language or regional alternate, but page B does not return a compatible declaration to page A.
Evidence to preserve
- Declaring URL, target URL, and expected language
- Target's actual hreflang declarations
- Target response path, canonical, and indexability
- Failure class: no hreflang, missing our language, or points elsewhere
How to repair the cause
- Add the correct return declaration to the target page
- Repair the shared language-cluster generator
- Remove stale alternates that should no longer participate
- Correct canonical or redirect behavior before repairing the pair
How to verify the fix
Fetch both pages and validate the pair against their freshly delivered declarations and public response paths.
The audit reports the public language graph. It does not invent which translations the editorial team should publish.
Private beta
Turn the next crawl into a repair system.
Bring a recurring technical SEO workflow. We will show how Amplitera keeps the evidence, handoff, and verification connected.
Request early access →