Check your WordPress environment, install the correct StagLingo edition, activate Premium access when applicable, run Diagnostics, and complete a small test before using the plugin on a live multilingual workflow.
StagLingo works at the WordPress and TranslatePress workflow level. Confirm the minimum platform requirements first, then use Diagnostics to inspect the parts that depend on the configuration of your own website.
These components must be available for normal StagLingo operation.
Some capabilities depend on other products or services.
Free and Premium use the same StagLingo product identity. Install the edition
that matches your access, then open the same administration area under
Tools → StagLingo.
In WordPress, open Plugins → Add New.
Search for StagLingo when its WordPress.org directory listing is available.
Select the plugin published by Stag at Last, then click Install Now and Activate.
Open Tools → StagLingo and continue to Diagnostics.
If WordPress.org search does not yet return StagLingo, the directory package is not currently available. Do not download a ZIP from an unofficial source; contact hello@stagatlast.com.
Sign in to My Account using the email associated with the purchase.
Open Downloads and download the current official StagLingo Premium ZIP. Do not extract it.
In WordPress, open Plugins → Add New → Upload Plugin, upload the ZIP, and install it.
Activate StagLingo Premium, then complete license activation when prompted.
If StagLingo Free is already active, activating the official Premium package automatically deactivates the Free build. Existing TranslatePress translations and retained StagLingo data are not removed by that switch.
Premium features and update delivery require an active license. Freemius provides the licensing and account connection used by the official Premium package.
Tools → StagLingo → License.
Installation success only confirms that WordPress loaded the plugin. Use the Diagnostics page to check the environment StagLingo will actually use before exporting or importing multilingual content.
If it is inactive, export and import remain disabled.
Check the configured locales and published language state.
Resolve a reported dictionary problem before testing an import.
Ask the hosting provider to enable it if rendered-content export reports it missing.
This check matters when the workflow includes translated page slugs.
Do not begin with the largest page or every configured language. A short page makes it easier to confirm extraction, file handling, storage, cache clearing, and the actual translated frontend.
Choose one short test page and one target language. Keep the first package small enough to inspect manually.
Use the documented manual or automatic workflow without mixing steps from different modes during the first test.
Open the real target-language URL in a private browser window and confirm what visitors receive, not only what an import status reports.
Use the normal WordPress update or official package replacement process. Deactivation and in-place updates are designed to retain StagLingo records and existing TranslatePress translations.
Once the WordPress.org edition is available, install its updates from the normal WordPress Plugins screen.
An active license provides Premium update delivery through Freemius. You can also obtain the current official ZIP from My Account when a manual replacement is required.
Continue to licensing and account management, select the correct translation workflow, or open troubleshooting if an environment check is not ready.
Browse the complete documentation by setup, workflow, operation, quality control, troubleshooting, or release history.