Phrase States

When viewing the Phrases tab, you can filter your site's content based on each phrase's current status:

Pending Phrases

After refreshing and visiting each page of your site, Localize will detect your content and pull it into your Pending bin. Pending phrases are not yet translated and awaiting action.

In-Progress Phrases

Needs Review

Contains phrases that were translated by your own translators (or were machine translated) and are now awaiting an Admin to approve the phrases to be published.

Needs Translation

Contains phrases that were approved for translation, but have not yet had a translation added by a translator.


Contains translated phrases that were submitted for review, but were rejected by an admin.

(Please note that the In-Progress status is only available on Growth Plans and higher.)

Published Phrases

Published phrases are phrases with live translations that are published on your application.

Archived Phrases


Phrases that have not been detected on your site for over 2 weeks are automatically moved to the Archive: Deprecated bin. If that deprecated content is found again on your website, it will be reactivated automatically, with all of its translations.

Depending on your website traffic patterns (e.g. plenty of infrequently-visited pages), you may consider disabling the "Archive unused phrases" option.


You may also choose to block phrases from being translated. Blocking a phrase prevents that phrase from ever populating into your Pending bin again. If you change your mind, simply go to your Archive: Blocked bin and retrieve the phrase by moving it back to Pending or Published.


Phrases that are moved to Trash will only remain in your Archive: Trash until the next time someone visits or refreshes the page with the phrase. Once that page is revisited, Localize will detect the phrase again and automatically pull it back into your Pending bin.

Updated 3 months ago

Phrase States

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.