Short answer
For two complete translations, check accessible URLs, content language, canonical and reciprocal alternates. Hreflang identifies variants rather than translating pages or guaranteeing indexing. Do not automatically canonicalise every version to Spanish: decide from actual content equivalence and retain coherent signals.
Key verification: Both pages expose the same alternate pair and canonicals consistent with their actual published content.
Sources and limitationsAn English page exists under /en/ but canonicalises to the Spanish homepage. Markup exists yet expresses a different relationship from editorial intent. This guide reviews a translated pair without production changes or search-result promises.
Content and pairing first
Check that both pages solve the same task in different languages, including tables, links and disclosures. Avoid pairing an English guide with another Spanish service. Retain a visible selector and avoid redirects preventing deliberate access to another language.
Original example: two head sections
<!-- Spanish page: https://example.invalid/es/service/ -->
<link rel="canonical" href="https://example.invalid/es/service/">
<link rel="alternate" hreflang="es" href="https://example.invalid/es/service/">
<link rel="alternate" hreflang="en" href="https://example.invalid/en/service/">
<!-- English page: https://example.invalid/en/service/ -->
<link rel="canonical" href="https://example.invalid/en/service/">
<link rel="alternate" hreflang="es" href="https://example.invalid/es/service/">
<link rel="alternate" hreflang="en" href="https://example.invalid/en/service/">The .invalid domain is nonoperational: this illustrates fully translated pages rather than untranslated duplicates. Absolute URLs and reciprocal pairing are intentional. Inspect delivered HTML rather than only plugin or generator settings.
Google documentation and limits
Google explains localised versions, self-reference and reciprocal hreflang. Main-content translation matters when distinguishing languages from duplicates. Valid markup and an /en/ path guarantee no search appearance; check access and indexability separately.
Review a Brandify proposal
Brandify presents marketing services. For multilingual review, request paired URLs, issues and before/after evidence without assuming a particular module. CallsIQ has not tested Brandify services. Manual pair review may suffice for a small catalogue.
Sources and limitations
Documentary review: . Content type: Documentation-based guide with original exercise.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- localised versions, self-reference and reciprocal hreflangdevelopers.google.com
- marketing servicesbrandify.io
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
BrandifyAffiliate linkThe labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.