SiteTran
Start free
Atlassian Statuspage One footer snippet

Translate your Statuspage, incident updates included

When your service is down, customers in Madrid, Munich and Tokyo need to understand your status page right away. SiteTran makes your Statuspage multilingual: components, uptime history and the subscribe form are translated, and each new incident update can be machine translated and published automatically.

Translate my status page free Check your Statuspage plan
  • Free plan, no card needed
  • Unlimited languages on every plan
  • AI + human review
187+languages, including right-to-left
~5 minto install from your Statuspage dashboard
0extra status pages to keep in sync
$0to start on the Free plan

Driving growth for companies with millions of users

Alignment Neil Patel Exomonitor Cyfe Instructified
Before you start

Statuspage plans with Custom HTML

SiteTran goes into Statuspage's Custom HTML field. Here's where you'll find it, so you can get set up in minutes.

Ready for SiteTran

Business and Enterprise

$399 and $1,499 per month

Public pages on these plans include Custom CSS/HTML/JS. Use your custom domain, such as status.yourcompany.com, which is where Statuspage shows custom HTML.

Ready for SiteTran

Private pages

Private Growth, Corporate and Enterprise

Private pages on these plans include Custom CSS/HTML/JS, so signed-in customers and teams can read your page in their language too.

Ready for SiteTran

Audience-specific pages

From $300 per month

Audience-specific pages include Custom CSS/HTML/JS, so each audience sees its own components and updates in its own language.

Quick upgrade

Free, Hobby or Startup

$0 to $99 per month

Moving up to Business adds the Custom HTML field that script-based translation tools use, along with your custom domain.

Plan names, prices and features from atlassian.com/software/statuspage/pricing and Atlassian's "Use custom HTML on a status page" article, checked October 20, 2026.

How it works

Add SiteTran to Statuspage in three steps

You paste three lines into Statuspage's Custom Footer HTML and one CSS rule into Custom CSS. Your components, incidents and subscribers stay exactly as they are.

1

Create your SiteTran site

Sign up free, add your status page address, such as status.yourcompany.com, and pick your languages. SiteTran gives you your Widget Code with your site ID.

2

Paste it into Custom Footer HTML

In Statuspage, open Your page, then Customize page and email, then Customize HTML & CSS. Paste the three lines into Custom Footer HTML and the CSS rule into Custom CSS.

Your page›Customize page and email›Customize HTML & CSS›Custom Footer HTML
3

Translate and publish

Open your status page in a private window and pick a language. SiteTran discovers your components and incidents as they're viewed. Translate them with AI, your own reviewers, or both.

Custom Footer HTML
<script>var sitetran = {site_id: your_site_id};</script>
<script src="//c.sitetran.com/widget/v3.js"></script>
<div id="sitetran_translate_element"></div>

SiteTran gives you your own ready-to-paste code, with your site ID already in it. The div is where the language dropdown is created. Then add this to Custom CSS so the dropdown stays in view instead of sitting below your footer:
#sitetran_translate_element { position: fixed; right: 16px; bottom: 16px; z-index: 50; }

Why the footer and not the header? Atlassian says anything in Custom Header HTML replaces your page's default header, the area that holds your logo and the Subscribe to Updates button. Custom Footer HTML is added after your content, so nothing disappears. If you already build your own header, you can put the div there instead, next to <div id="replace-with-subscribe"></div>, which Statuspage swaps for its subscribe button. Then leave out the CSS rule. See Positioning the Language Dropdown on your Site for more placement options.

During an outage

What happens when you post a new incident update

Your on-call engineer writes in English, under pressure, with no time to wait for a translator. Turn on Machine Translation, Machine Translation Auto Translate and Machine Translation Auto Approve once, and each new update follows these steps on its own.

  1. You post the update in Statuspage

    Write and publish it as usual. Nothing about your incident process changes, and nobody on the incident has to touch SiteTran.

  2. The new text is discovered first view

    With Public Phrase Discovery on, the first time anyone opens the page in another language, SiteTran finds the sentences it hasn't seen and adds them to your site, ready to translate.

  3. Machine translation drafts it Auto Translate

    DeepL, Google Translate or OpenAI translates it into each language, following your Glossary and Translation Rules, so component and product names stay the way you want them.

  4. It's approved and published Auto Approve

    With Publish Translations Automatically on, which is the default, it goes live right away. Usually that's a minute or two after the text is discovered. Reviewers can still correct it later.

Live within minutes

Published translations reach your page within about 30 seconds. Browsers refresh translation data every 10 minutes by default so pages load quickly, and on a status page you can make that every minute with the setting below. Everything already translated stays translated throughout.

Open it yourself right after posting

Make it part of your runbook: after each update, open your status page in one of your languages. That discovers the new text straight away, instead of waiting for the first customer to do it. If you keep Public Phrase Discovery off, this is how new text gets in: teammates with Verified Phrase Discovery send it.

Shorten the browser cache during incidents

Widget data is cached in 10-minute intervals by default. On a status page you can shorten that to one minute by adding one setting to the first line of your Widget Code:

var sitetran = {site_id: 12345, expiration_interval_seconds: 60};
Incident templates

Translate your incident templates before you need them

Most incident updates reuse the same few sentences. Statuspage keeps them as incident templates, and SiteTran matches text exactly, so wording that's already translated shows up translated with no waiting at all.

  • Translate once, reuse in every incident

    "A fix has been implemented and we're monitoring the results." only needs translating and reviewing once. Every later incident that uses the same words is translated right away, using your reviewers' approved version.

  • Variables for component names

    Turn the changing part of a template into a variable, such as {{component}}. When a component name like Webhooks is also a translated phrase, SiteTran uses that translation inside the sentence.

  • Add them ahead of time

    Paste your templates into a Page Doc in Pages & Phrases, with Add New Page, and translate them before your next incident. Text that matches your page exactly, spaces included, is used on your status page too.

Engineers can still edit a template during an incident. Edited sentences are simply new text, and Machine Translation Auto Translate handles them like any other update. See Adding Variables to Phrases.

Built for Statuspage

What happens to each part of your status page

SiteTran translates what Statuspage renders in the visitor's browser, including tooltips and the subscribe form that appear after the page loads. Here's what that covers.

Translated once, reused

Components and statuses

Component names, group names, descriptions and the five statuses, from Operational to Major Outage, plus banners such as All Systems Operational. They rarely change, so they're translated once.

Translated

Uptime bars and tooltips

"Uptime over the past 90 days", the hover text on each day and the uptime percentage. Use Automatic Number Variables so "99.82 % uptime" and "99.97 % uptime" share one translation.

Translated as viewed

Incidents, maintenance and history

Active incidents, scheduled maintenance, Past Incidents, incident pages and Incident History. Statuspage prints month names such as Oct as their own short text, so dates translate once and work on every day.

Translated

The subscribe form

Subscribe to Updates and its email, SMS, Slack and feed options are on your page, so they're translated too. What subscribers type, like their email address, is never changed.

Translated

Page titles and link previews

The page title, meta description and Open Graph tags switch with the language, so an incident link shared in a customer's Slack or Teams channel previews in their language.

Right to left included

Arabic, Hebrew and more

Right-to-left languages switch the page direction automatically, and you can fine-tune the layout with per-language CSS before you set a language to Live.

Compare your options

Every way to run a multilingual status page

Statuspage has no built-in language setting for visitors. You can connect the Localize app, keep a second page per language, move to a status page tool with built-in languages, or add SiteTran. Here's what each one involves.

Localize appIn Statuspage's Apps menu A page per languageStatuspage, by hand or by API Status tools with languagesBetter Stack, StatusPal, Hyperping, incident.io SiteTranOne footer snippet
How it works Paste your Localize project key into Statuspage. Localize collects phrases as the page loads, and you translate them in Localize. Run a separate status page for each language and post every incident update on each one. Move your status page to a tool that translates its own interface and lets you add languages. SiteTran translates your page as it renders and adds a language dropdown.
Statuspage plan needed Any paid public page with a custom domain, or a private page on Growth or higher. Any plan, for each page you run. Not applicable: you leave Statuspage. Language features may need a higher plan of that tool. Business or Enterprise with a custom domain, private Growth or higher, or audience-specific.
Incident updates Collected when viewed. Optional automatic approval of machine translations. Written again for each language during the incident, by a person or your own API scripts. Mostly typed per language in separate tabs. StatusPal offers AI translation on Business and up. incident.io updates are single-language. Machine translated and published automatically if you choose, or reviewed first. Templates can be translated ahead.
Languages 100+ languages, per Atlassian. As many as the pages you run. Varies: Hyperping lists 7, Better Stack ships 8 ready-made, incident.io offers French, Portuguese and Japanese natively. 187+ languages including right-to-left, unlimited on every plan.
Pricing Localize license, quote-based. Your team's time on every incident. That tool's plans, plus migrating your page and subscribers. Free plan, then from $3/month. Unlimited languages and teammates.

Statuspage and Localize details are from Atlassian's "Translate pages with Localize" and pricing pages and Localize's Statuspage guide. Other tools' details are from their own documentation, checked October 20, 2026. Website translation scripts such as Weglot or ConveyThis need the same Statuspage Custom HTML as SiteTran, and their plans limit how many languages you can add.

Translation quality

Fast during the incident, reviewed after it

During an outage, speed matters most. Afterwards, your support team can polish what customers read. SiteTran lets you have both.

  • Machine translation from DeepL, Google and OpenAI

    Get suggestions for any phrase, or translate new phrases automatically. You choose whether they're approved automatically or reviewed first.

  • Translators and reviewers per language

    Invite support agents in your regional offices or a professional translator, and choose who can approve. Turn on AI Translation Review for a second opinion.

  • Glossary, rules and translation memory

    Keep component names such as API or Webhooks unchanged with the Glossary, set Translation Rules such as "use the formal Sie in German", and reuse past wording with Similar Phrases.

  • A language dropdown that fits your page

    Choose from three dropdown types, with or without flags, and match your Statuspage colors with CSS. Visitors are switched to their browser language automatically.

Translate your status page into 187+ languages

SpanishGermanFrenchJapanesePortuguese (Brazil)KoreanChinese (Simplified)ItalianDutchPolishTurkishArabicHebrewHindiIndonesianVietnamese+ 170 more
SEO for status pages

Multilingual SEO on Statuspage

Most people reach a status page from your app, an email or a search for "is your product down". Here's what's translated as soon as you install SiteTran, and how to add language URLs if you want them.

Included as soon as you install

Everything link previews and browsers read

When a visitor switches language, the page title and description switch with it. That matters when an incident link is shared in a customer's Slack or Teams channel during an outage.

  • Page title and meta description
  • Open Graph and Twitter tags for link previews
  • Image alt text, tooltips, placeholders and ARIA labels
  • The page's lang attribute, set to the selected language
Advanced setup, rarely needed

Language URLs for Google

By default, every language uses your existing status page URL and the visitor's choice is remembered. For a separate, indexable page per language, SiteTran's Static Translation API returns translated HTML that you serve from a language subdomain through a proxy or edge worker you run.

status.yourcompany.comStatuspage, original
es.status.yourcompany.comSubdomain + proxy

Status pages change minute by minute during an incident, so for most teams the same URL with translated titles is the simpler choice. We're happy to talk it through.

Talk to us about your setup

Want the general walkthrough with screenshots?

Custom SiteTran Integration covers creating your site, copying your Widget Code and testing your first language. On Statuspage, paste the code into Custom Footer HTML as shown above.

Read the guide
Troubleshooting

Statuspage translation not working? Check these first

Most Statuspage setup problems come down to the plan, the domain, or which HTML field the code went into.

1The language dropdown doesn't appear

  1. Check your plan: public pages need Business or Enterprise for Custom HTML.
  2. Open your page on your custom domain, not the statuspage.io address. Statuspage hides custom HTML there.
  3. Make sure all three lines are in Custom Footer HTML, including the div.
  4. In SiteTran, make sure the language is both Active and Live. If Hide All Widgets On Site (dev mode) is on, add ?sitetran=on to your URL.
My Language Isn’t Showing Up in the Language Dropdown →

2My logo or Subscribe button disappeared

  1. The code is probably in Custom Header HTML, which replaces Statuspage's header.
  2. Move it to Custom Footer HTML and clear the header field.
  3. Or keep your own header and add <div id="replace-with-subscribe"></div> to bring the button back.

3The newest incident update is still in English

  1. Check that Machine Translation, Machine Translation Auto Translate and Machine Translation Auto Approve are all on, under AI.
  2. Open the page in another language yourself so the new text is discovered. Check Public Phrase Discovery under Settings › Phrase Discovery.
  3. Allow up to 30 seconds after publishing, and up to 10 minutes for a browser's cached data. Try a private window.
My New Translations or Changes Aren’t Appearing on my Website →

4Uptime percentages fill my phrase list

  1. Each different number can arrive as a new phrase, such as "99.82 % uptime".
  2. Open one in Pages & Phrases, click Edit and turn on Enable Auto Numbers, then translate it once.
  3. Use variables when words change too, such as a component name inside a sentence.
Automatic Number Variables →

5Component names were translated oddly

  1. Add product and component names to the Glossary with the translation you want, which can be the name itself.
  2. Or wrap them in your own HTML with translate="no" in component descriptions.
  3. Fix any existing translation once in the translator, and every page uses it.
Glossary →

6The layout looks off in Arabic or Hebrew

  1. Right-to-left languages flip the page direction, and Statuspage's layout was designed left to right.
  2. Add fixes as per-language CSS under Languages › Manage Language, in CSS Styles For Language Pages.
  3. Check the uptime bars and incident timeline in that language before you set it to Live.
Updating CSS Styles by Language and Page →
Pricing

Simple pricing, even when incidents pile up

Every plan includes unlimited languages and teammates, so adding Japanese after Spanish never means a bigger plan. Repeated template wording is stored once, so a busy month of incidents mostly adds the sentences that are new.

Free

$0

For small status pages and testing

  • 7K words in site
  • 3K translated pageviews / month
  • 7K machine translations

Starter

$3/mo

For sites with moderate translation needs

  • 30K words in site
  • 15K translated pageviews / month
  • 30K machine translations
Busy status pages

Pro

$35/mo

For larger sites or several smaller ones

  • 90K words in site
  • 45K translated pageviews / month
  • 90K machine translations

Business

$75/mo

For large-scale international sites

  • 250K words in site
  • 125K translated pageviews / month
  • 250K machine translations
Annual billing: 2 months free · Enterprise plans for 1M+ words See all features
FAQ

Statuspage translation questions

Have another question? Our team is happy to help with your Statuspage setup and your incident templates.

Email support
How do I add SiteTran to my Statuspage status page?
Create a free SiteTran site and copy your Widget Code. In Statuspage, open Your page, then Customize page and email, then Customize HTML & CSS. Paste the three lines into Custom Footer HTML, and add the CSS rule from this page to Custom CSS so the dropdown stays in view. Open your status page on its custom domain and pick a language from the dropdown.
Which Statuspage plan do I need?
For a public page, Business or Enterprise, because those plans include Custom CSS/HTML/JS, and the page must use a custom domain. Private pages on Growth, Corporate or Enterprise and audience-specific pages also include custom HTML. On Free, Hobby, Startup or private Starter, upgrading adds the Custom HTML field that script-based translation tools use.
Why paste the code into Custom Footer HTML instead of the header?
Statuspage replaces its default header with anything you put in Custom Header HTML, and that header holds your logo and the Subscribe to Updates button. Custom Footer HTML is added after your content, so nothing is removed. If you already use a custom header, you can place the dropdown's div there and add the div with the ID replace-with-subscribe to keep the subscribe button.
How fast are new incident updates translated?
With Machine Translation, Machine Translation Auto Translate and Machine Translation Auto Approve turned on, new text is translated and published automatically, usually within a minute or two of being discovered. Discovery happens the first time someone views the page in another language, or when you open it yourself after posting. Published translations reach your page within about 30 seconds, and you can set browsers to refresh translation data every minute during incidents.
Can I translate my incident templates before an outage?
Yes. Paste your templates into a Page Doc in Pages & Phrases and translate them ahead of time. Text that matches your status page exactly, including spaces, is translated there too, with no waiting. Use a variable such as {{component}} for parts that change between incidents.
Does Statuspage support multiple languages on its own?
Not for visitors. Statuspage has no built-in language switcher, and Atlassian's documented route is the Localize app, which needs a separate Localize account. Some teams run a second status page per language instead, which means posting every update twice.
Are component names, statuses and uptime history translated?
Yes. Component and group names, descriptions, statuses such as Operational and Partial Outage, the uptime bars and their tooltips, past incidents and Incident History are all translated as they appear. Use Automatic Number Variables for uptime percentages so one translation covers every number.
Will subscriber emails and SMS messages be translated?
Your status page, including every incident update and the Subscribe to Updates form, is translated, so many teams link each notification back to the status page, where customers read it in their language. Like every website translation tool, SiteTran works on the page itself: email, SMS, Slack and webhook notifications are sent by Statuspage in the language you write the incident in.
Should I use the Localize app in Statuspage instead?
If you are on Hobby or Startup, Localize is the option Statuspage supports, because the app doesn't need Custom HTML. On Business or Enterprise you can choose. SiteTran offers a Free plan and published pricing from $3 per month, 187+ languages, and translators and reviewers per language. Localize pricing is quote-based. Use one or the other on a page, not both.
Can I keep product and component names in English?
Yes. Add product names and component names such as API or Webhooks to the Glossary with the translation you want, which can be the name itself. Translation Rules can also tell AI translation how to handle them.
Do translated status pages get their own URLs for SEO?
By default, every language uses your existing status page URL with a translated title and meta description, and the visitor's choice is remembered. For indexable language URLs, SiteTran's Static Translation API can return translated HTML that you serve on a language subdomain through a proxy you run. Status pages change quickly during incidents, so most teams don't need this. Book a call and we will help you decide.
Does SiteTran work on private and audience-specific pages?
Yes, on plans with custom HTML: private pages on Growth or higher, and audience-specific pages. SiteTran discovers text the same way when signed-in viewers open the page in another language. If those pages contain customer names or other sensitive details, exclude those elements or turn off Public Phrase Discovery.
Can I test translations before customers see them?
Yes. A language stays hidden from visitors until you set it to Live. You can also turn on Hide All Widgets On Site (dev mode) under Settings, then Publishing, and add ?sitetran=on to your status page URL to preview the language dropdown yourself.
Is there a free plan?
Yes. The Free plan includes 7,000 words in your site, 3,000 translated pageviews per month and 7,000 machine translations, with unlimited languages and teammates. Paid plans raise those limits and start at $3 per month. Compare plans.
What happens if I go over my plan's limits?
You will be prompted to upgrade or buy additional credits. Your existing translations remain intact, and new translations are paused until you upgrade.
See all 29 integrations →

Make your status page multilingual before the next incident

Paste one footer snippet, pick your languages, and turn on automatic translation, so customers everywhere can read what's happening when it matters most. Start on the Free plan and upgrade only when you grow.

Start translating free Book a call Free plan · Unlimited languages and teammates