Demander une démo

Rapport de localisation

F

Finder

finder.com.au

Produit: www.finder.com.au

Score de localisation

40/100

Médiocre

Des lacunes importantes en matière de localisation affectent l’expérience.

  • 56Audit technique
  • 58Audit linguistique
  • 50Audit contextuel
  • 58Audit visuel
Audité: 8/15/2026Portée: Échantillon intelligent public · crédits techniques, linguistiques, contextuels et visuelsConfiance: Contrôle indicatif de l’état de santé à partir de pages échantillonnées — il ne s’agit pas d’une exploration complète du site.

1 pages échantillonnées parmi les crédits de localisation techniques, linguistiques, contextuels et visuels. Comment nous évaluons les audits de localisation

Comment vous vous comparez

Rang #21 sur 22 audits publics

Top 9 % des domaines auditésMoyenne publique : 68/100

À corriger en priorité

  • criticaltechnical · 100 % de confiance

    Could not inspect page language

    No successful HTML pages were available to check html lang.

    Trouvé ici

    Document head · <html lang>

    Ce que nous avons constaté

    The crawl returned no successful HTML pages to inspect.

    Comment le corriger

    Make the sampled localisation URLs return 200 HTML so html lang can be checked.

  • hightechnical · 100 % de confiance

    Page returned HTTP 403

    A sampled localisation URL did not return a successful HTML response.

    Trouvé ici

    Sampled page · document

    https://www.finder.com.au/

    Ce que nous avons constaté

    HTTP 403

    Comment le corriger

    Fix the localized URL so it returns a successful HTML response.

  • mediumtechnical · 90 % de confiance

    Only one locale signal detected

    The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).

    Trouvé ici

    Sampled pages · document

    https://www.finder.com.au/

    Ce que nous avons constaté

    Detected locale signals: en-us

    Comment le corriger

    Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.

Critères d’audit

2 réussis · 16 à corriger · 17 non applicable

À examiner (16)

  • Locale detection

    Échec0technique

    Pages should declare a correct html lang that matches the URL and content locale.

    • criticaltechnical · 100 % de confiance

      Could not inspect page language

      No successful HTML pages were available to check html lang.

      Trouvé ici

      Document head · <html lang>

      Ce que nous avons constaté

      The crawl returned no successful HTML pages to inspect.

      Comment le corriger

      Make the sampled localisation URLs return 200 HTML so html lang can be checked.

  • Locale routing

    Échec60technique

    Localized pages should use a consistent URL structure and resolve successfully.

    • hightechnical · 100 % de confiance

      Page returned HTTP 403

      A sampled localisation URL did not return a successful HTML response.

      Trouvé ici

      Sampled page · document

      https://www.finder.com.au/

      Ce que nous avons constaté

      HTTP 403

      Comment le corriger

      Fix the localized URL so it returns a successful HTML response.

    • mediumtechnical · 90 % de confiance

      Only one locale signal detected

      The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).

      Trouvé ici

      Sampled pages · document

      https://www.finder.com.au/

      Ce que nous avons constaté

      Detected locale signals: en-us

      Comment le corriger

      Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.

  • Canonical URLs

    Échec72technique

    Canonical URLs should represent the localized page, not a different locale.

    • mediumtechnical · 95 % de confiance

      Canonical URLs are missing

      Sampled pages did not declare a canonical URL.

      Trouvé ici

      Document head · <link rel="canonical">

      Ce que nous avons constaté

      No <link rel="canonical"> was found on sampled pages.

      Comment le corriger

      Add a canonical URL that points at this locale’s own page.

  • International formatting

    Échec50technique

    Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.

    • infotechnical · 88 % de confiance

      Formatting examples unavailable

      The page returned a security-verification interstitial, so dates, numbers, currencies, and calendar formatting could not be assessed.

      Ce que nous avons constaté

      "status":403 ... "reason":"no_formatting_examples"

      Comment le corriger

      Provide an accessible page capture or crawl result containing representative localized dates, numbers, and currency values.

  • Accessibility localisation

    Échec55technique

    lang, aria-label, and alt text should match the page locale.

    • infotechnical · 90 % de confiance

      Locale metadata is present

      The document declares the expected English US locale and left-to-right direction.

      Trouvé ici

      Document root · <html>

      https://www.finder.com.au/

      Ce que nous avons constaté

      "htmlLang":"en-US","dir":"ltr"

    • infotechnical · 90 % de confiance

      Accessible names cannot be assessed

      The blocked response contains no buttons or accessible-name markup, so aria-label and alt-text localization could not be verified.

      Ce que nous avons constaté

      "buttons":[],"reason":"no_accessible_names"

      Comment le corriger

      Provide rendered page markup so interactive labels and image alt text can be reviewed.

  • Terminology consistency

    Échec50linguistique

    Important concepts should not be translated differently across pages.

    • infolinguistic · 88 % de confiance

      Cross-page terminology unavailable

      Only a security-verification interstitial was returned, with no clear product or navigation term clusters to compare.

      Ce que nous avons constaté

      "reason":"no_clear_term_clusters"

      Comment le corriger

      Provide accessible localized page content covering repeated product and navigation terms.

  • Translation accuracy

    Échec50linguistique

    Target copy should preserve the source meaning, numbers, and product actions.

    • infolinguistic · 88 % de confiance

      Translation accuracy cannot be assessed

      The response contains only security-verification copy and no source-target content or product actions for comparison.

      Ce que nous avons constaté

      "status":403 ... "title":"Just a moment..."

      Comment le corriger

      Provide both source and localized rendered copy for comparison of meaning, numbers, and actions.

  • Fluency

    Échec50linguistique

    Copy should sound natural, without grammar issues or machine-translation artifacts.

    • infolinguistic · 88 % de confiance

      Localized copy unavailable

      The accessible response is a bot-verification interstitial rather than the localized website copy, so fluency cannot be evaluated.

      Ce que nous avons constaté

      "text":"www.finder.com.au Performing security verification This page is displayed while the website verifies you are not a bot."

      Comment le corriger

      Provide the rendered localized content instead of the security-verification response.

  • Brand voice

    Échec50linguistique

    Localized copy should preserve the intended tone of the source.

    • infolinguistic · 88 % de confiance

      Brand voice unavailable

      No representative website copy was returned, so the localized tone cannot be compared with the intended brand voice.

      Ce que nous avons constaté

      "status":403 ... "title":"Just a moment..."

      Comment le corriger

      Provide accessible localized marketing and interface copy for brand-voice review.

  • Grammar and style

    Échec50linguistique

    Locale-specific capitalization, punctuation, formality, and agreement should be correct.

    • infolinguistic · 88 % de confiance

      Grammar and style unavailable

      The response does not contain the site's localized content needed to assess punctuation, capitalization, formality, or agreement.

      Ce que nous avons constaté

      "status":403 ... "reason":"no_formatting_examples"

      Comment le corriger

      Provide the rendered localized page text for locale-specific grammar and style checks.

  • Cultural adaptation

    Échec50contextuel

    Currency, dates, addresses, and local examples should fit the market.

    • infocontextual · 88 % de confiance

      Cultural signals unavailable

      The blocked response contains no currency, date, address, or market-specific examples to assess cultural adaptation.

      Ce que nous avons constaté

      "reason":"no_cultural_signals"

      Comment le corriger

      Provide accessible page content containing Australian market examples and conventions.

  • Localized images and assets

    Échec88visuel

    Language-specific images and alt text should match the page locale.

  • Visual hierarchy

    Échec50visuel

    Localization should not make headings or CTAs lose scanability.

    • infovisual · 72 % de confiance

      Rendered hierarchy unavailable

      Only the security-verification interstitial was captured, so localized heading and CTA scanability cannot be assessed.

      Ce que nous avons constaté

      "reason":"no_long_headings"

      Comment le corriger

      Provide screenshots or rendered HTML of the localized page to assess heading and CTA hierarchy.

  • Text overflow

    Échec50visuel

    Text should not clip, truncate unexpectedly, or overflow buttons and navigation.

    • infovisual · 72 % de confiance

      Overflow cannot be assessed

      No rendered layout or localized navigation was captured, so clipping and text overflow cannot be verified.

      Ce que nous avons constaté

      "reason":"no_rendered_layout"

      Comment le corriger

      Provide screenshots or viewport-specific rendered captures for overflow testing.

  • Layout breakage

    Échec50visuel

    Localized pages should not overlap, break grids, or overflow modals.

    • infovisual · 72 % de confiance

      Layout rendering unavailable

      The 403 response provides no rendered page layout from which overlap, grid, modal, or overflow issues can be assessed.

      Ce que nous avons constaté

      "status":403 ... "reason":"no_rendered_layout"

      Comment le corriger

      Provide rendered desktop and mobile captures or accessible HTML for layout inspection.

  • Responsive localisation

    Échec50visuel

    Localized layouts should hold up across mobile, tablet, and desktop widths.

    • infovisual · 72 % de confiance

      Responsive behavior unavailable

      No rendered layouts at mobile, tablet, or desktop widths were provided, so responsive localization cannot be assessed.

      Ce que nous avons constaté

      "reason":"no_rendered_layout"

      Comment le corriger

      Provide captures or test results at mobile, tablet, and desktop viewport widths.

Audits réussis (2)

Non applicable (17)

Paramètres régionaux détectés

en-us (html_lang)

Résultats complets

  • criticaltechnical · 100 % de confiance

    Could not inspect page language

    No successful HTML pages were available to check html lang.

    Trouvé ici

    Document head · <html lang>

    Ce que nous avons constaté

    The crawl returned no successful HTML pages to inspect.

    Comment le corriger

    Make the sampled localisation URLs return 200 HTML so html lang can be checked.

  • hightechnical · 100 % de confiance

    Page returned HTTP 403

    A sampled localisation URL did not return a successful HTML response.

    Trouvé ici

    Sampled page · document

    https://www.finder.com.au/

    Ce que nous avons constaté

    HTTP 403

    Comment le corriger

    Fix the localized URL so it returns a successful HTML response.

  • mediumtechnical · 90 % de confiance

    Only one locale signal detected

    The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).

    Trouvé ici

    Sampled pages · document

    https://www.finder.com.au/

    Ce que nous avons constaté

    Detected locale signals: en-us

    Comment le corriger

    Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.

  • mediumtechnical · 95 % de confiance

    Canonical URLs are missing

    Sampled pages did not declare a canonical URL.

    Trouvé ici

    Document head · <link rel="canonical">

    Ce que nous avons constaté

    No <link rel="canonical"> was found on sampled pages.

    Comment le corriger

    Add a canonical URL that points at this locale’s own page.

  • infotechnical · 88 % de confiance

    Formatting examples unavailable

    The page returned a security-verification interstitial, so dates, numbers, currencies, and calendar formatting could not be assessed.

    Ce que nous avons constaté

    "status":403 ... "reason":"no_formatting_examples"

    Comment le corriger

    Provide an accessible page capture or crawl result containing representative localized dates, numbers, and currency values.

  • infotechnical · 90 % de confiance

    Locale metadata is present

    The document declares the expected English US locale and left-to-right direction.

    Trouvé ici

    Document root · <html>

    https://www.finder.com.au/

    Ce que nous avons constaté

    "htmlLang":"en-US","dir":"ltr"

  • infotechnical · 90 % de confiance

    Accessible names cannot be assessed

    The blocked response contains no buttons or accessible-name markup, so aria-label and alt-text localization could not be verified.

    Ce que nous avons constaté

    "buttons":[],"reason":"no_accessible_names"

    Comment le corriger

    Provide rendered page markup so interactive labels and image alt text can be reviewed.

  • infolinguistic · 88 % de confiance

    Cross-page terminology unavailable

    Only a security-verification interstitial was returned, with no clear product or navigation term clusters to compare.

    Ce que nous avons constaté

    "reason":"no_clear_term_clusters"

    Comment le corriger

    Provide accessible localized page content covering repeated product and navigation terms.

  • infolinguistic · 88 % de confiance

    Translation accuracy cannot be assessed

    The response contains only security-verification copy and no source-target content or product actions for comparison.

    Ce que nous avons constaté

    "status":403 ... "title":"Just a moment..."

    Comment le corriger

    Provide both source and localized rendered copy for comparison of meaning, numbers, and actions.

  • infolinguistic · 88 % de confiance

    Localized copy unavailable

    The accessible response is a bot-verification interstitial rather than the localized website copy, so fluency cannot be evaluated.

    Ce que nous avons constaté

    "text":"www.finder.com.au Performing security verification This page is displayed while the website verifies you are not a bot."

    Comment le corriger

    Provide the rendered localized content instead of the security-verification response.

  • infolinguistic · 88 % de confiance

    Brand voice unavailable

    No representative website copy was returned, so the localized tone cannot be compared with the intended brand voice.

    Ce que nous avons constaté

    "status":403 ... "title":"Just a moment..."

    Comment le corriger

    Provide accessible localized marketing and interface copy for brand-voice review.

  • infolinguistic · 88 % de confiance

    Grammar and style unavailable

    The response does not contain the site's localized content needed to assess punctuation, capitalization, formality, or agreement.

    Ce que nous avons constaté

    "status":403 ... "reason":"no_formatting_examples"

    Comment le corriger

    Provide the rendered localized page text for locale-specific grammar and style checks.

  • infocontextual · 88 % de confiance

    Cultural signals unavailable

    The blocked response contains no currency, date, address, or market-specific examples to assess cultural adaptation.

    Ce que nous avons constaté

    "reason":"no_cultural_signals"

    Comment le corriger

    Provide accessible page content containing Australian market examples and conventions.

  • infovisual · 72 % de confiance

    Rendered hierarchy unavailable

    Only the security-verification interstitial was captured, so localized heading and CTA scanability cannot be assessed.

    Ce que nous avons constaté

    "reason":"no_long_headings"

    Comment le corriger

    Provide screenshots or rendered HTML of the localized page to assess heading and CTA hierarchy.

  • infovisual · 72 % de confiance

    Overflow cannot be assessed

    No rendered layout or localized navigation was captured, so clipping and text overflow cannot be verified.

    Ce que nous avons constaté

    "reason":"no_rendered_layout"

    Comment le corriger

    Provide screenshots or viewport-specific rendered captures for overflow testing.

  • infovisual · 72 % de confiance

    Layout rendering unavailable

    The 403 response provides no rendered page layout from which overlap, grid, modal, or overflow issues can be assessed.

    Ce que nous avons constaté

    "status":403 ... "reason":"no_rendered_layout"

    Comment le corriger

    Provide rendered desktop and mobile captures or accessible HTML for layout inspection.

  • infovisual · 72 % de confiance

    Responsive behavior unavailable

    No rendered layouts at mobile, tablet, or desktop widths were provided, so responsive localization cannot be assessed.

    Ce que nous avons constaté

    "reason":"no_rendered_layout"

    Comment le corriger

    Provide captures or test results at mobile, tablet, and desktop viewport widths.

Pages échantillonnées

  • 403 · https://www.finder.com.au/ · lang=en-US

Envoyez-moi un récapitulatif par e-mail

Facultatif. Saisissez votre adresse e-mail professionnelle et nous vous enverrons un résumé concis de ce rapport public.

Étape suivante

Des lacunes critiques ont été détectées. Créez un espace de travail pour effectuer un audit enregistré plus approfondi, ou réservez une revue avec notre équipe.