Localisation report
Finder
finder.com.au
Product: www.finder.com.au
Localisation score
40/100
PoorSignificant localisation gaps are affecting the experience.
- 56Technical Audit
- 58Linguistic Audit
- 50Contextual Audit
- 58Visual Audit
Sampled 1 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits
How you compare
Rank #21 of 22 public audits
Fix first
- criticaltechnical · 100% confidence
Could not inspect page language
No successful HTML pages were available to check html lang.
Found here
Document head · <html lang>
What we saw
The crawl returned no successful HTML pages to inspect.
How to fix it
Make the sampled localisation URLs return 200 HTML so html lang can be checked.
- hightechnical · 100% confidence
Page returned HTTP 403
A sampled localisation URL did not return a successful HTML response.
Found here
Sampled page · document
https://www.finder.com.au/What we saw
HTTP 403
How to fix it
Fix the localized URL so it returns a successful HTML response.
- mediumtechnical · 90% confidence
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Found here
Sampled pages · document
https://www.finder.com.au/What we saw
Detected locale signals: en-us
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
Audit criteria
2 passed · 16 to fix · 17 not applicable
Needs attention (16)
Locale detection
Fail0technicalPages should declare a correct html lang that matches the URL and content locale.
- criticaltechnical · 100% confidence
Could not inspect page language
No successful HTML pages were available to check html lang.
Found here
Document head · <html lang>
What we saw
The crawl returned no successful HTML pages to inspect.
How to fix it
Make the sampled localisation URLs return 200 HTML so html lang can be checked.
Locale routing
Fail60technicalLocalized pages should use a consistent URL structure and resolve successfully.
- hightechnical · 100% confidence
Page returned HTTP 403
A sampled localisation URL did not return a successful HTML response.
Found here
Sampled page · document
https://www.finder.com.au/What we saw
HTTP 403
How to fix it
Fix the localized URL so it returns a successful HTML response.
- mediumtechnical · 90% confidence
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Found here
Sampled pages · document
https://www.finder.com.au/What we saw
Detected locale signals: en-us
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
Canonical URLs
Fail72technicalCanonical URLs should represent the localized page, not a different locale.
- mediumtechnical · 95% confidence
Canonical URLs are missing
Sampled pages did not declare a canonical URL.
Found here
Document head · <link rel="canonical">
What we saw
No <link rel="canonical"> was found on sampled pages.
How to fix it
Add a canonical URL that points at this locale’s own page.
International formatting
Fail50technicalDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 88% confidence
Formatting examples unavailable
The page returned a security-verification interstitial, so dates, numbers, currencies, and calendar formatting could not be assessed.
Found here
What we saw
"status":403 ... "reason":"no_formatting_examples"
How to fix it
Provide an accessible page capture or crawl result containing representative localized dates, numbers, and currency values.
Accessibility localisation
Fail55technicallang, aria-label, and alt text should match the page locale.
- infotechnical · 90% confidence
Locale metadata is present
The document declares the expected English US locale and left-to-right direction.
Found here
Document root · <html>
https://www.finder.com.au/What we saw
"htmlLang":"en-US","dir":"ltr"
- infotechnical · 90% confidence
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.
Found here
What we saw
"buttons":[],"reason":"no_accessible_names"
How to fix it
Provide rendered page markup so interactive labels and image alt text can be reviewed.
Terminology consistency
Fail50linguisticImportant concepts should not be translated differently across pages.
- infolinguistic · 88% confidence
Cross-page terminology unavailable
Only a security-verification interstitial was returned, with no clear product or navigation term clusters to compare.
Found here
What we saw
"reason":"no_clear_term_clusters"
How to fix it
Provide accessible localized page content covering repeated product and navigation terms.
Translation accuracy
Fail50linguisticTarget copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 88% confidence
Translation accuracy cannot be assessed
The response contains only security-verification copy and no source-target content or product actions for comparison.
Found here
What we saw
"status":403 ... "title":"Just a moment..."
How to fix it
Provide both source and localized rendered copy for comparison of meaning, numbers, and actions.
Fluency
Fail50linguisticCopy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 88% confidence
Localized copy unavailable
The accessible response is a bot-verification interstitial rather than the localized website copy, so fluency cannot be evaluated.
Found here
What we saw
"text":"www.finder.com.au Performing security verification This page is displayed while the website verifies you are not a bot."
How to fix it
Provide the rendered localized content instead of the security-verification response.
Brand voice
Fail50linguisticLocalized copy should preserve the intended tone of the source.
- infolinguistic · 88% confidence
Brand voice unavailable
No representative website copy was returned, so the localized tone cannot be compared with the intended brand voice.
Found here
What we saw
"status":403 ... "title":"Just a moment..."
How to fix it
Provide accessible localized marketing and interface copy for brand-voice review.
Grammar and style
Fail50linguisticLocale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 88% confidence
Grammar and style unavailable
The response does not contain the site's localized content needed to assess punctuation, capitalization, formality, or agreement.
What we saw
"status":403 ... "reason":"no_formatting_examples"
How to fix it
Provide the rendered localized page text for locale-specific grammar and style checks.
Cultural adaptation
Fail50contextualCurrency, dates, addresses, and local examples should fit the market.
- infocontextual · 88% confidence
Cultural signals unavailable
The blocked response contains no currency, date, address, or market-specific examples to assess cultural adaptation.
Found here
What we saw
"reason":"no_cultural_signals"
How to fix it
Provide accessible page content containing Australian market examples and conventions.
Localized images and assets
Fail88visualLanguage-specific images and alt text should match the page locale.
Visual hierarchy
Fail50visualLocalization should not make headings or CTAs lose scanability.
- infovisual · 72% confidence
Rendered hierarchy unavailable
Only the security-verification interstitial was captured, so localized heading and CTA scanability cannot be assessed.
What we saw
"reason":"no_long_headings"
How to fix it
Provide screenshots or rendered HTML of the localized page to assess heading and CTA hierarchy.
Text overflow
Fail50visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
- infovisual · 72% confidence
Overflow cannot be assessed
No rendered layout or localized navigation was captured, so clipping and text overflow cannot be verified.
Found here
What we saw
"reason":"no_rendered_layout"
How to fix it
Provide screenshots or viewport-specific rendered captures for overflow testing.
Layout breakage
Fail50visualLocalized pages should not overlap, break grids, or overflow modals.
- infovisual · 72% confidence
Layout rendering unavailable
The 403 response provides no rendered page layout from which overlap, grid, modal, or overflow issues can be assessed.
Found here
What we saw
"status":403 ... "reason":"no_rendered_layout"
How to fix it
Provide rendered desktop and mobile captures or accessible HTML for layout inspection.
Responsive localisation
Fail50visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 72% confidence
Responsive behavior unavailable
No rendered layouts at mobile, tablet, or desktop widths were provided, so responsive localization cannot be assessed.
Found here
What we saw
"reason":"no_rendered_layout"
How to fix it
Provide captures or test results at mobile, tablet, and desktop viewport widths.
Passed audits (2)
Not applicable (17)
Detected locales
Full findings
- criticaltechnical · 100% confidence
Could not inspect page language
No successful HTML pages were available to check html lang.
Found here
Document head · <html lang>
What we saw
The crawl returned no successful HTML pages to inspect.
How to fix it
Make the sampled localisation URLs return 200 HTML so html lang can be checked.
- hightechnical · 100% confidence
Page returned HTTP 403
A sampled localisation URL did not return a successful HTML response.
Found here
Sampled page · document
https://www.finder.com.au/What we saw
HTTP 403
How to fix it
Fix the localized URL so it returns a successful HTML response.
- mediumtechnical · 90% confidence
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Found here
Sampled pages · document
https://www.finder.com.au/What we saw
Detected locale signals: en-us
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
- mediumtechnical · 95% confidence
Canonical URLs are missing
Sampled pages did not declare a canonical URL.
Found here
Document head · <link rel="canonical">
What we saw
No <link rel="canonical"> was found on sampled pages.
How to fix it
Add a canonical URL that points at this locale’s own page.
- infotechnical · 88% confidence
Formatting examples unavailable
The page returned a security-verification interstitial, so dates, numbers, currencies, and calendar formatting could not be assessed.
Found here
What we saw
"status":403 ... "reason":"no_formatting_examples"
How to fix it
Provide an accessible page capture or crawl result containing representative localized dates, numbers, and currency values.
- infotechnical · 90% confidence
Locale metadata is present
The document declares the expected English US locale and left-to-right direction.
Found here
Document root · <html>
https://www.finder.com.au/What we saw
"htmlLang":"en-US","dir":"ltr"
- infotechnical · 90% confidence
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.
Found here
What we saw
"buttons":[],"reason":"no_accessible_names"
How to fix it
Provide rendered page markup so interactive labels and image alt text can be reviewed.
- infolinguistic · 88% confidence
Cross-page terminology unavailable
Only a security-verification interstitial was returned, with no clear product or navigation term clusters to compare.
Found here
What we saw
"reason":"no_clear_term_clusters"
How to fix it
Provide accessible localized page content covering repeated product and navigation terms.
- infolinguistic · 88% confidence
Translation accuracy cannot be assessed
The response contains only security-verification copy and no source-target content or product actions for comparison.
Found here
What we saw
"status":403 ... "title":"Just a moment..."
How to fix it
Provide both source and localized rendered copy for comparison of meaning, numbers, and actions.
- infolinguistic · 88% confidence
Localized copy unavailable
The accessible response is a bot-verification interstitial rather than the localized website copy, so fluency cannot be evaluated.
Found here
What we saw
"text":"www.finder.com.au Performing security verification This page is displayed while the website verifies you are not a bot."
How to fix it
Provide the rendered localized content instead of the security-verification response.
- infolinguistic · 88% confidence
Brand voice unavailable
No representative website copy was returned, so the localized tone cannot be compared with the intended brand voice.
Found here
What we saw
"status":403 ... "title":"Just a moment..."
How to fix it
Provide accessible localized marketing and interface copy for brand-voice review.
- infolinguistic · 88% confidence
Grammar and style unavailable
The response does not contain the site's localized content needed to assess punctuation, capitalization, formality, or agreement.
What we saw
"status":403 ... "reason":"no_formatting_examples"
How to fix it
Provide the rendered localized page text for locale-specific grammar and style checks.
- infocontextual · 88% confidence
Cultural signals unavailable
The blocked response contains no currency, date, address, or market-specific examples to assess cultural adaptation.
Found here
What we saw
"reason":"no_cultural_signals"
How to fix it
Provide accessible page content containing Australian market examples and conventions.
- infovisual · 72% confidence
Rendered hierarchy unavailable
Only the security-verification interstitial was captured, so localized heading and CTA scanability cannot be assessed.
What we saw
"reason":"no_long_headings"
How to fix it
Provide screenshots or rendered HTML of the localized page to assess heading and CTA hierarchy.
- infovisual · 72% confidence
Overflow cannot be assessed
No rendered layout or localized navigation was captured, so clipping and text overflow cannot be verified.
Found here
What we saw
"reason":"no_rendered_layout"
How to fix it
Provide screenshots or viewport-specific rendered captures for overflow testing.
- infovisual · 72% confidence
Layout rendering unavailable
The 403 response provides no rendered page layout from which overlap, grid, modal, or overflow issues can be assessed.
Found here
What we saw
"status":403 ... "reason":"no_rendered_layout"
How to fix it
Provide rendered desktop and mobile captures or accessible HTML for layout inspection.
- infovisual · 72% confidence
Responsive behavior unavailable
No rendered layouts at mobile, tablet, or desktop widths were provided, so responsive localization cannot be assessed.
Found here
What we saw
"reason":"no_rendered_layout"
How to fix it
Provide captures or test results at mobile, tablet, and desktop viewport widths.
Pages sampled
- 403 · https://www.finder.com.au/ · lang=en-US
Email me a summary
Optional. Enter your work email and we will send a concise summary of this public report.
Next step
Critical gaps showed up. Create a workspace to run a deeper registered audit, or book a review with our team.