Find practical answers about requirements, TranslatePress, AI providers, exports, imports, publishing controls, licensing, data handling, refunds, and support.
Answers shown. Search checks both questions and answers.
No matching answer was found. Clear the search or email hello@stagatlast.com.
Each answer links to the full guide when the task needs step-by-step instructions, screenshots, or troubleshooting evidence.
Requirements, TranslatePress, Elementor, installation, and access.
02Manual, automatic, Incremental, providers, model access, and costs.
03Protected fields, warnings, backups, verification, scores, and indexing.
04Free versus Premium, activation, site limits, transfer, renewal, and expiry.
05API keys, direct provider requests, retention, history, and uninstall.
06Eligibility, response target, support scope, evidence, and seven-day policy.
StagLingo is a WordPress workflow extension for sites already using TranslatePress. It is not a replacement translation engine or a page builder add-on.
StagLingo is an export, review, import, verification, Incremental, AI-assisted, and publishing-control workflow for WordPress websites using TranslatePress. It helps administrators manage translations as controlled page-level work rather than editing isolated strings without a portable review package.
No. TranslatePress remains responsible for multilingual storage and serving translated pages. StagLingo extends that environment with extraction, workflow packaging, protected import, read-back, review, diagnostics, and publishing controls.
No. StagLingo is not tied to Elementor or another page builder. It operates at the WordPress, rendered-page, and TranslatePress workflow layers. Content generated by page builders may still require normal compatibility testing.
The current StagLingo 1.1.3 plugin header requires WordPress 5.8 or later and PHP 7.4 or later. TranslatePress must be active for translation workflows. Individual capabilities such as translated URL slugs also depend on the relevant TranslatePress component being available.
Open Tools → StagLingo in the WordPress administrator area. Access to protected operations requires an administrator account with the appropriate WordPress capability.
Install an official StagLingo ZIP through Plugins → Add New → Upload Plugin, or use the WordPress.org directory listing when the Free version is available there. Premium customers download the current package and manage licenses through My Account. Back up the site and test important workflows after an update.
See Getting Started with StagLingo for the complete sequence.
Manual and automatic workflows can create first translations. Incremental is for maintaining translation state that already exists.
Compare them in Choose a Translation Workflow.
Yes. In the manual workflow, export the source package, translate and review it with the tool or team you choose, and upload the reviewed package. StagLingo does not require automatic translation for protected import and verification.
The current plugin has native request formats for OpenAI Responses, Google Gemini GenerateContent, and Anthropic Messages. It also accepts an administrator-defined HTTPS endpoint that implements the supported OpenAI-compatible chat-completions pattern.
No. StagLingo provides the workflow and protected WordPress integration. The website owner supplies and pays for the selected provider account, API access, usage, limits, and any related taxes. A ChatGPT consumer subscription does not automatically include OpenAI API credit.
Use an exact model ID available in your provider account and capable of following structured JSON, long-context, multilingual, and markup-preservation instructions. StagLingo does not silently substitute a different model during updates. Quality, speed, limits, availability, and cost vary by provider and model.
Follow Automatic Translation and AI Models to configure and test it.
No model request is proxied through Stagatlast. Your WordPress server sends the request directly to the selected provider. Depending on the operation, the request can include source text, target locale, structural context, first-pass translations, rendered page text, and verification evidence. The provider’s own terms and retention rules apply.
It stores a limited set of sanitized, reusable trigger and pass-condition rules. The design excludes page copy, translations, URLs, titles, names, row IDs, hashes, filenames, and private model responses from learned examples. An administrator can reset the learned rules.
Package validation, database read-back, and immediate front-end verification answer different questions. Do not treat every warning as interchangeable.
Keep protected identity fields such as post_id, source_url, content_type, exact_english_source, and source_hash unchanged. They allow StagLingo to validate that a reviewed target still belongs to the correct live source.
Dynamic related articles, rotating cards, conditional blocks, personalization, cached fragments, and JavaScript-rendered content may differ between the extracted package and one immediate verification request. If storage read-back succeeded and the message is specifically a front-end-unconfirmed or not-detected warning, clear site/CDN caches and inspect the actual target-language page in a private window.
Validation, protected-field, backup, transaction, rollback, and storage read-back failures cannot be dismissed this way. See History, Backups, and Troubleshooting.
Only after confirming the error belongs to dynamic or unrelated content, the relevant translation storage passed read-back, and the visitor-visible target-language page is correct. Do not use this exception for a genuine validation, backup, transaction, rollback, or storage failure.
After a staged file completes successfully, its temporary staged copy and current queue result can be cleaned up. Successful page-language writes move into History. Use History and the live target-language page as the lasting evidence.
Do not immediately upload a duplicate package. Check server-side status and use Resume saved imports. Incomplete protected jobs can survive refreshes, network interruptions, and in-place plugin updates for up to 48 hours.
Yes. Protected imports create a private pre-import CSV backup of the values about to change. The latest 20 backups are retained. A backup is evidence and a controlled recovery reference; it is not presented as a one-click restore button.
No. Results vary by source quality, language, model, provider limits, reasoning capability, terminology, page structure, and review depth. Scoring is an audit signal, not a warranty. Important content still requires language-appropriate review and live-page verification.
Yes. Language Index Control can add temporary page-language noindex records while work is incomplete. Remove the control only after the target-language page has passed the applicable quality and publishing checks.
No. Automation itself is not a ranking guarantee or an automatic penalty. The practical risk comes from publishing inaccurate, unnatural, duplicated, poorly localized, or unhelpful pages at scale. StagLingo provides review and release controls but cannot guarantee indexing, traffic, or rankings.
Freemius provides checkout, subscriptions, license activation, account management, and update delivery for Premium customers.
The current entitlement design keeps page title/URL export, Language Index Control, AI model settings, and language scoring available in Free. Commercial features include multilingual Export and Review Export, Incremental workflows, reviewed-package Import, and automatic translation. Review the current pricing page because packaging can change in later releases.
Purchase the required website count, install the official Premium package, and activate the license through the StagLingo/Freemius account controls in WordPress. Downloads, license assignments, subscriptions, and invoices are also available through My Account.
One activated website uses one license seat. A development or testing site also occupies a seat while activated. When testing is finished, deactivate that installation and transfer the available seat to the production or replacement domain.
Yes. Deactivate the old website in the plugin or account portal, then activate the new website. If the old site is no longer accessible, manage its assignment through My Account or contact support.
Premium functionality and Premium updates require an active license. StagLingo Free functionality remains available, and translations already written into TranslatePress are not deleted merely because the StagLingo license expires.
Annual licenses renew until cancelled. Manage renewal and cancellation from My Account. The checkout and account portal show the renewal amount, tax treatment, payment method, and any notices controlled by Freemius.
Sign in at stagatlast.com/account/ to access downloads, licenses, assigned websites, subscriptions, invoices, payment methods, and support tools.
The full account guide is Plans, Licenses, and My Account.
The website owner controls the WordPress environment and selects any external AI service. Stagatlast does not operate a translation proxy between them.
A saved key is stored in the site’s WordPress database in encrypted form. The encryption key is derived from that installation’s authentication salts. StagLingo uses AES-256-GCM when available and falls back to Sodium secret-box. If neither supported method is available, a new key is not saved.
No. The saved key is excluded from translation exports, History, normal workflow reports, logs, and learned quality rules. It is decrypted only when the WordPress server needs to authenticate a request to the configured provider.
Important current limits include 30 minutes for diagnostic Preview state, up to 48 hours for incomplete staged/resumable imports, the latest 20 private backups, the latest 200 page-language History records, and the five most recently updated automatic workflow jobs. Hosting and database backups may retain copies longer.
The last five jobs can retain local source snapshots, source identity and URL information, first-pass translations, compact import summaries, scoring results, errors, and resume lineage. They are stored in WordPress options so an interrupted workflow can resume safely.
No. Plugin data is preserved on uninstall by default to avoid accidental workflow loss. Uninstall should not be treated as a guaranteed erasure workflow, especially when WordPress or host-level backups exist. Plan and verify permanent cleanup separately.
Read Data Handling and Security for operational details and the Privacy Policy for the website, plugin, commerce, analytics, and third-party service disclosures.
A useful technical request identifies the plugin version, target locale, affected URL, exact message, relevant History result, Diagnostics state, and whether the live page reproduces the issue.
Free users can email hello@stagatlast.com. Include enough evidence to reproduce a StagLingo issue, but never send passwords, full API keys, payment-card information, or unnecessary private content.
Customers with an active Premium license can submit a support form through My Account or email hello@stagatlast.com. The response target is within one day, although investigation and resolution time depend on the problem and evidence provided.
No new Premium support tickets are accepted for an expired license. An existing ticket opened while the license was active can continue to be handled after expiry.
Support covers StagLingo itself. It does not include general WordPress development, custom theme or page-builder work, hosting administration, database repair unrelated to StagLingo, TranslatePress support, AI-provider account or billing support, custom prompt writing, translation services, SEO guarantees, or third-party plugin debugging unless a reproducible StagLingo compatibility issue is involved.
Do not send a full API key or administrator password.
StagLingo provides a seven-day refund policy for qualifying unresolved product issues, subject to the conditions and exclusions in the current Refund Policy. The policy is not a general seven-day trial or a guarantee that third-party services, hosting, or every website configuration will meet a customer’s expectations.
For Premium support, submit the form in My Account. Free users and customers who cannot access the portal can email hello@stagatlast.com. Never include a password or complete API key.
The FAQ defines boundaries. The workflow guides provide the exact sequence, screenshots, protected-field rules, and verification steps.
