Localisation report

Canva

Design software

canva.com

Product: Canva appears to be a digital design service. The available page indicates users can create designs, but provides no further product details.

Brand voice: reassuring, service-oriented

Localisation score

39/100

Poor

Significant localisation gaps are affecting the experience.

54Technical Audit
62Linguistic Audit
50Contextual Audit
50Visual Audit

Audited: 8/15/2026Scope: Public smart sample · technical, linguistic, contextual, and visual creditsConfidence: Indicative health check from sampled pages — not a full site crawl.

Sampled 2 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits

How you compare

Rank #22 of 22 public audits

Top 5% of audited domainsPublic average: 68/100

See the full leaderboard

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. Affects 2 sampled pages.
Found here
Sampled page · document
https://www.canva.com/
What we saw
HTTP 403 Seen on 2 pages, e.g. https://www.canva.com/, https://www.canva.com/en/help/troubleshoot-cloudflare-error/
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.canva.com/
What we saw
Detected locale signals: en
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.

Audit criteria

2 passed · 15 to fix · 18 not applicable

Needs attention (15)

Locale detection
Fail0technical
Pages 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
Fail48technical
Localized 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. Affects 2 sampled pages.
  Found here
  Sampled page · document
  https://www.canva.com/
  What we saw
  HTTP 403 Seen on 2 pages, e.g. https://www.canva.com/, https://www.canva.com/en/help/troubleshoot-cloudflare-error/
  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.canva.com/
  What we saw
  Detected locale signals: en
  How to fix it
  Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
Canonical URLs
Fail72technical
Canonical 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
Fail50technical
Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 92% confidence
  Formatting examples unavailable
  Both sampled URLs return a Cloudflare verification page, so dates, numbers, currencies, and calendar conventions cannot be assessed.
  Found here
  Page response · <html>
  https://www.canva.com/
  What we saw
  "status":403,"reason":"no_formatting_examples"
  How to fix it
  Review the rendered localized pages and test representative dates, numbers, currencies, and calendar values.
Accessibility localisation
Fail55technical
lang, aria-label, and alt text should match the page locale.
- infotechnical · 88% confidence
  Accessible names unavailable
  The page declares English and left-to-right direction, but the 403 response exposes no buttons, alt text, or ARIA labels for review.
  Found here
  Document root · <html>
  https://www.canva.com/
  What we saw
  "htmlLang":"en","dir":"ltr","buttons":[]
  How to fix it
  Review rendered controls, images, and landmarks to verify that accessible names and alternative text are in English.
Terminology consistency
Fail50linguistic
Important concepts should not be translated differently across pages.
- infolinguistic · 93% confidence
  No term comparison possible
  The available responses contain only a Cloudflare verification message and provide no clear cross-page terminology clusters.
  Found here
  Page body · <body>
  https://www.canva.com/
  What we saw
  "reason":"no_clear_term_clusters"
  How to fix it
  Compare repeated product, navigation, and support terms across accessible localized pages.
Translation accuracy
Fail50linguistic
Target copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 94% confidence
  Source-target accuracy cannot be verified
  Only an English verification message is available; there is no source copy or translated product content to compare.
  Found here
  Page body · <body>
  https://www.canva.com/
  What we saw
  "status":403,"title":"Just a moment..."
  How to fix it
  Restore access to the localized content and compare headings, actions, numbers, and meaning against the source copy.
Fluency
Fail60linguistic
Copy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 72% confidence
  Limited copy sample
  The exposed verification text reads naturally enough, but it is system text rather than representative localized website copy.
  Found here
  Verification message · <h1>
  https://www.canva.com/
  What we saw
  We’ll have you designing again soon
  How to fix it
  Evaluate fluency using the rendered product and help content, not only the access-verification message.
Brand voice
Fail50linguistic
Localized copy should preserve the intended tone of the source.
- infolinguistic · 91% confidence
  Brand voice unavailable
  The responses expose only a generic verification page, so the intended localized brand tone cannot be compared or assessed.
  Found here
  Verification page · <body>
  https://www.canva.com/
  What we saw
  "headings":["We’ll have you designing again soon"]
  How to fix it
  Review accessible marketing, product, and support copy for consistency with Canva’s intended localized voice.
Grammar and style
Fail60linguistic
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 74% confidence
  Insufficient locale copy
  The short English verification message shows no obvious grammar issue, but it is insufficient to assess broader capitalization, punctuation, formality, or agreement.
  Found here
  Verification message · <h1>
  https://www.canva.com/
  What we saw
  We’ll have you designing again soon
  How to fix it
  Check complete localized page content for locale-specific punctuation, capitalization, formality, and grammatical agreement.
Cultural adaptation
Fail50contextual
Currency, dates, addresses, and local examples should fit the market.
- infocontextual · 93% confidence
  Cultural signals unavailable
  No localized currency, date, address, market example, or other cultural content is visible in the 403 responses.
  Found here
  Page body · <body>
  https://www.canva.com/
  What we saw
  "reason":"no_cultural_signals"
  How to fix it
  Review market-specific examples, formats, and references on accessible localized pages.
Visual hierarchy
Fail50visual
Localization should not make headings or CTAs lose scanability.
- infovisual · 70% confidence
  Hierarchy cannot be assessed
  The response exposes only one verification heading and no localized navigation or CTA structure, so hierarchy in the actual site is unknown.
  Found here
  Verification message · <h1>
  https://www.canva.com/
  What we saw
  "headings":["We’ll have you designing again soon"]
  How to fix it
  Inspect the rendered localized pages to verify heading levels, CTA prominence, and scanability.
Text overflow
Fail50visual
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- infovisual · 65% confidence
  Rendered layout unavailable
  No rendered layout or localized controls are available, so clipping and text overflow cannot be verified.
  Found here
  Page layout · <body>
  https://www.canva.com/
  What we saw
  "reason":"no_rendered_layout"
  How to fix it
  Test localized headings, buttons, navigation labels, and form fields at representative viewport sizes.
Layout breakage
Fail50visual
Localized pages should not overlap, break grids, or overflow modals.
- infovisual · 65% confidence
  Layout integrity cannot be assessed
  Both sampled pages return status 403 and provide no rendered localized layout for checking overlap, grids, or modals.
  Found here
  Page layout · <body>
  https://www.canva.com/
  What we saw
  "status":403,"reason":"no_rendered_layout"
  How to fix it
  Load the localized pages successfully and test grids, overlays, modals, and long translated strings.
Responsive localisation
Fail50visual
Localized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 65% confidence
  Responsive behavior unavailable
  The evidence contains no rendered layouts or viewport comparisons, so mobile, tablet, and desktop behavior cannot be assessed.
  Found here
  Responsive layout · <body>
  https://www.canva.com/
  What we saw
  "reason":"no_rendered_layout"
  How to fix it
  Compare accessible localized pages at mobile, tablet, and desktop widths using representative long strings.

Passed audits (2)

Not applicable (18)

Detected locales

en (html_lang)

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. Affects 2 sampled pages.
Found here
Sampled page · document
https://www.canva.com/
What we saw
HTTP 403 Seen on 2 pages, e.g. https://www.canva.com/, https://www.canva.com/en/help/troubleshoot-cloudflare-error/
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.canva.com/
What we saw
Detected locale signals: en
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 · 92% confidence
Formatting examples unavailable
Both sampled URLs return a Cloudflare verification page, so dates, numbers, currencies, and calendar conventions cannot be assessed.
Found here
Page response · <html>
https://www.canva.com/
What we saw
"status":403,"reason":"no_formatting_examples"
How to fix it
Review the rendered localized pages and test representative dates, numbers, currencies, and calendar values.
infotechnical · 88% confidence
Accessible names unavailable
The page declares English and left-to-right direction, but the 403 response exposes no buttons, alt text, or ARIA labels for review.
Found here
Document root · <html>
https://www.canva.com/
What we saw
"htmlLang":"en","dir":"ltr","buttons":[]
How to fix it
Review rendered controls, images, and landmarks to verify that accessible names and alternative text are in English.
infolinguistic · 93% confidence
No term comparison possible
The available responses contain only a Cloudflare verification message and provide no clear cross-page terminology clusters.
Found here
Page body · <body>
https://www.canva.com/
What we saw
"reason":"no_clear_term_clusters"
How to fix it
Compare repeated product, navigation, and support terms across accessible localized pages.
infolinguistic · 94% confidence
Source-target accuracy cannot be verified
Only an English verification message is available; there is no source copy or translated product content to compare.
Found here
Page body · <body>
https://www.canva.com/
What we saw
"status":403,"title":"Just a moment..."
How to fix it
Restore access to the localized content and compare headings, actions, numbers, and meaning against the source copy.
infolinguistic · 72% confidence
Limited copy sample
The exposed verification text reads naturally enough, but it is system text rather than representative localized website copy.
Found here
Verification message · <h1>
https://www.canva.com/
What we saw
We’ll have you designing again soon
How to fix it
Evaluate fluency using the rendered product and help content, not only the access-verification message.
infolinguistic · 91% confidence
Brand voice unavailable
The responses expose only a generic verification page, so the intended localized brand tone cannot be compared or assessed.
Found here
Verification page · <body>
https://www.canva.com/
What we saw
"headings":["We’ll have you designing again soon"]
How to fix it
Review accessible marketing, product, and support copy for consistency with Canva’s intended localized voice.
infolinguistic · 74% confidence
Insufficient locale copy
The short English verification message shows no obvious grammar issue, but it is insufficient to assess broader capitalization, punctuation, formality, or agreement.
Found here
Verification message · <h1>
https://www.canva.com/
What we saw
We’ll have you designing again soon
How to fix it
Check complete localized page content for locale-specific punctuation, capitalization, formality, and grammatical agreement.
infocontextual · 93% confidence
Cultural signals unavailable
No localized currency, date, address, market example, or other cultural content is visible in the 403 responses.
Found here
Page body · <body>
https://www.canva.com/
What we saw
"reason":"no_cultural_signals"
How to fix it
Review market-specific examples, formats, and references on accessible localized pages.
infovisual · 70% confidence
Hierarchy cannot be assessed
The response exposes only one verification heading and no localized navigation or CTA structure, so hierarchy in the actual site is unknown.
Found here
Verification message · <h1>
https://www.canva.com/
What we saw
"headings":["We’ll have you designing again soon"]
How to fix it
Inspect the rendered localized pages to verify heading levels, CTA prominence, and scanability.
infovisual · 65% confidence
Rendered layout unavailable
No rendered layout or localized controls are available, so clipping and text overflow cannot be verified.
Found here
Page layout · <body>
https://www.canva.com/
What we saw
"reason":"no_rendered_layout"
How to fix it
Test localized headings, buttons, navigation labels, and form fields at representative viewport sizes.
infovisual · 65% confidence
Layout integrity cannot be assessed
Both sampled pages return status 403 and provide no rendered localized layout for checking overlap, grids, or modals.
Found here
Page layout · <body>
https://www.canva.com/
What we saw
"status":403,"reason":"no_rendered_layout"
How to fix it
Load the localized pages successfully and test grids, overlays, modals, and long translated strings.
infovisual · 65% confidence
Responsive behavior unavailable
The evidence contains no rendered layouts or viewport comparisons, so mobile, tablet, and desktop behavior cannot be assessed.
Found here
Responsive layout · <body>
https://www.canva.com/
What we saw
"reason":"no_rendered_layout"
How to fix it
Compare accessible localized pages at mobile, tablet, and desktop widths using representative long strings.

Pages sampled

403 · https://www.canva.com/ · lang=en
403 · https://www.canva.com/en/help/troubleshoot-cloudflare-error/ · lang=en

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.

Book an audit review