GDPR-compliant organization

ISO 27001 certified organization

SOC II compliant organization

Translate your Strikingly website with AI

Translate the pages, navigation, and contact flow of your Strikingly site with AI, review the wording in context, and publish the languages your visitors need.

Smartcat editor showing translated segments with a translation memory match and reviewer assignments

More than 80 of the world’s largest companies have chosen Smartcat

How to add Smartcat to Strikingly

Create a Smartcat website project from your published Strikingly URL and choose the target languages.

Install the generated Smartcat snippet through the Header custom-code setting (the blog has its own code scope).

Publish the change and open the live site to confirm the snippet is present.

Review the translations in Smartcat’s visual editor and publish the languages that are ready.

Translate a Strikingly site without overlooking the blog

Use the supported Header custom-code setting on a plan that permits it. Review the published site and blog separately: the brief identifies a separate blog code scope, so a working homepage does not prove that posts receive the same snippet.

For a one-page business site, translate the service offer, proof, and contact action as a coherent message. For blog content, preserve author attribution and the meaning of linked resources. Text inside graphics needs a separate asset update.

Strikingly’s own multilingual capabilities are another option; do not present a script as its only translation route.

What changes for visitors, and what stays in Strikingly

Smartcat translates the text your published Strikingly pages render. Your pages, settings, form recipients, and booking or payment logic stay where they are; embedded widgets and text inside images have their own localization settings.

Review before a language goes live

Machine translation gives you a fast first draft. In Smartcat’s visual editor you see each translated string on the page, shorten headings that run long on mobile, and keep product and brand names consistent with a glossary. Assign a reviewer when a page needs approval, and publish only the languages that are ready.

Frequently asked questions

Why is the homepage translated but a blog post is not?

The blog may use a different custom-code scope. Inspect the blog’s published head output and translation scope rather than reinstalling only on the homepage.

Can I edit translations before publishing?

Yes. Refine and confirm the wording in Smartcat’s visual editor, then publish the languages that are ready.

What happens when I add a new page in Strikingly?

New text follows the Smartcat project’s selected translation mode. Choose reviewed translations when every new page requires approval; automatic modes can translate newly encountered text. Neither mode changes your source content in Strikingly.

Publish your Strikingly website in more languages

Install the snippet once, review the translations in context, and publish the languages your audience needs. See all website integrations or read how the Website Translator works.