Smartling

À examiner (6)

• Language switcher

  Échec58technique

  Visitors should move between locales without losing the current page.

  • hightechnical · 95 % de confiance

    Language links return to the homepage

    Locale links were found, but they appear to drop the current page path.

    Trouvé ici

    Header · <nav> language links

    https://www.smartling.com/privacy/

    Ce que nous avons constaté

    <a href="https://help.smartling.com/hc/en-us">Help Center Find articles, walk-throughs, and tutorials on a variety of Smartling topics</a> drops the current page path

    Comment le corriger

    Point language-switcher links at the equivalent localized path, not the locale homepage.

• Sitemap

  Échec18technique

  Like Lighthouse: a valid XML sitemap must be discoverable, robots.txt should reference it with an absolute Sitemap: URL, and localized URLs should appear for published locales.

  • hightechnical · 100 % de confiance

    Valid sitemap not found

    No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.

    Trouvé ici

    Sitemap · sitemap.xml

    https://www.smartling.com/sitemap.xml

    Ce que nous avons constaté

    robots.txt references https://www.smartling.com/sitemap.xml, but no sitemap returned usable <loc> entries

    Comment le corriger

    Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.

• Structured data

  Échec20technique

  JSON-LD inLanguage should match the page locale when structured data is present.

  • lowtechnical · 95 % de confiance

    Structured data omits inLanguage

    JSON-LD is present but does not declare inLanguage on sampled pages.

    Trouvé ici

    JSON-LD · <script type="application/ld+json">

    https://www.smartling.com/

    Ce que nous avons constaté

    FAQPage is present but inLanguage is missing

    Comment le corriger

    Set JSON-LD inLanguage to match each page locale.

• Terminology consistency

  Échec50linguistique

  Important concepts should not be translated differently across pages.

  • infolinguistic · 18 % de confiance

    Localized terminology cannot be verified

    The supplied evidence lists multiple locales but exposes only English page content, so terminology consistency across localized pages cannot be assessed.

    Trouvé ici

    https://www.smartling.com/

    Ce que nous avons constaté

    "locales":["da","de","en","es-mx","fr-ca","it","nl","pt","se","zh"] and the shown page has "htmlLang":"en" with headings such as "Transform translation into a growth engine".

    Comment le corriger

    Provide equivalent localized page extracts for comparison of recurring product and business terms.

• Localized images and assets

  Échec88visuel

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

• Visual hierarchy

  Échec55visuel

  Localization should not make headings or CTAs lose scanability.

  • lowvisual · 80 % de confiance

    Heading is excessively long

    A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.

    Trouvé ici

    Page body · heading

    https://www.smartling.com/

    Ce que nous avons constaté

    Smartling can handle your entire enterprise, from marketing to learning and development. Seen on 5 pages, e.g. https://www.smartling.com/, https://www.smartling.com/software/translation-analytics/, https://www.smartling.com/software/cat-tool/

    Comment le corriger

    Shorten the heading so it does not crowd the visual hierarchy.