Before you install

StagLingo Requirements and Compatibility

Check your WordPress environment, understand what depends on TranslatePress, and test the content that matters to your site.

01 / Environment

Start with the right foundation.

StagLingo adds a translation-management workflow to a WordPress site using TranslatePress. It does not replace WordPress, TranslatePress, your hosting, or your AI provider.

Core requirements and feature-specific dependencies
ComponentRequirementWhat to check
WordPress5.8 or laterChoose a maintained release compatible with your full plugin stack. The minimum version is not a recommendation to stay on an old release.
PHP7.4 or laterUse a maintained PHP version that also meets WordPress and TranslatePress requirements. A minimum version alone does not establish compatibility with every newer release.
TranslatePressInstalled, active, and configuredSet your source and target languages and confirm the target-language URLs work before starting a StagLingo translation workflow.
StagLingo editionThe edition needed for your workflowExport, Review Export, Import, Incremental, and Auto Translation require Premium access. See Free vs Premium.
PHP extensionsDOM for rendered-content export and inspectionAsk your host to confirm DOM is available. If you use ZIP workflows, also check the archive support and messages shown by your installed plugin.
Server accessWorking WordPress requests and file handlingCheck uploads, downloads, temporary storage, permissions, and the requests used by your selected workflow. Security rules must not block legitimate plugin operations.
API-powered AIYour own provider credentials and accessOnly needed for in-plugin API features. Your server must reach the selected provider, and your account must have access to the chosen model.
Admin browserA current desktop browser with JavaScript enabledUse an up-to-date Chrome, Edge, Firefox, or Safari for administration. This is usage guidance, not a certification matrix for every browser version.

Apply the requirements of all components. If your TranslatePress version, theme, or another dependency needs a newer WordPress or PHP version, that higher requirement also applies. Check the StagLingo package you install if minimum versions change.

02 / Content coverage

The content matters more than the page builder.

StagLingo is not tied to Elementor or a specific editor. Coverage depends on what TranslatePress can recognize and what the selected StagLingo workflow can capture from the page.

Start with a representative page

Check ordinary rendered content.

Posts, pages, and public custom post types are useful test cases when their text is available to TranslatePress.

  • Headings, paragraphs, lists, and visible links.
  • Buttons, navigation, and reusable page sections.
  • Block-editor, classic-editor, theme, or builder output.
  • Shared text that may appear on more than one URL.
Needs a separate test

Do not assume every string is captured.

Content may depend on interaction, permissions, external services, or specialized storage.

  • AJAX results, JavaScript-only content, and personalized text.
  • Member-only pages, carts, checkout, and account states.
  • Third-party widgets, embedded frames, and external apps.
  • Text inside images, PDFs, video, emails, or admin screens.

Visible on a page does not always mean exportable. Test the exact URL and state, inspect the exported content, and verify the translated result. StagLingo is not an OCR, document-translation, or universal plugin-string translation service.

03 / AI & external services

Choose how translation work gets done.

AI configuration, provider access, and Premium workflow access are separate requirements. Saving a model setting does not unlock a Premium feature.

Use API-powered features.

Configure OpenAI, Google Gemini, Anthropic, or a supported OpenAI-compatible endpoint in the plugin's AI settings.

  • Bring credentials for the provider and model you select.
  • Check billing, quotas, rate limits, and regional availability.
  • Allow the required outbound HTTPS requests from your WordPress server.
  • Test a small request before starting a larger translation job.

Translate outside WordPress.

The manual Premium workflow lets you export content, translate and review it with your chosen external tool, then import the reviewed file.

  • An in-plugin AI API connection is not required for manual export and import.
  • Your external translation tool has its own terms and costs.
  • Keep identifiers, placeholders, markup, and import structure intact.
  • Review the live translated page after import.

AI services are not included. StagLingo does not include an AI chat subscription or API credits. A provider's chat subscription is not the same as API access. An endpoint described as “OpenAI-compatible” still needs a request test; that label does not guarantee every model or feature will work. See edition and cost details.

04 / Hosting & delivery

Make sure requests reach the right content.

No single hosting specification can guarantee every workload. File size, language count, page complexity, provider latency, and server limits all affect a run.

Uploads, storage & time limits

Check upload and POST limits, memory, request timeouts, available disk space, and writable working directories. Start with a small batch. If a request fails, use the actual error and hosting logs to identify the limit rather than increasing every setting.

Page cache & CDN

After an import, clear the relevant page and language caches before checking the result. Confirm your cache setup keeps language versions separate. An old cached page is not reliable evidence of a failed translation write.

Security plugins & firewalls

Check whether authorized admin requests, file uploads, server-side page fetches, or provider connections are being blocked. Use narrow, documented exceptions where appropriate. Do not disable site security permanently to make a workflow run.

SEO plugins & index control

Review robots directives alongside your SEO plugin, TranslatePress settings, server headers, and cache. StagLingo index controls are not a replacement for a multilingual SEO configuration. Confirm the final output before changing indexability.

Separate TranslatePress features

The languages, SEO fields, and translated URL features available to your site depend on your TranslatePress configuration and any relevant add-ons. StagLingo Premium does not include a TranslatePress license or unlock its separately licensed features.

05 / Special setups

Test complex environments before committing.

The situations below are not blanket compatibility promises. Ask about your exact configuration if it is central to your purchase decision.

WooCommerce & membership sites

Test product and public content separately from checkout, account, logged-in, and personalized states. Do not assume customer data, order emails, or every extension's strings are included in a page-translation workflow.

WordPress Multisite

Do not assume network-wide activation, cross-site jobs, shared settings, or network-wide licensing. Confirm the intended workflow and license scope with support before purchasing for a Multisite network.

Staging, local & protected sites

Authentication, maintenance mode, private DNS, and blocked outbound requests can prevent page fetches or licensing. A development-site activation uses a license slot under the current site-based policy; deactivate it before moving that activation.

Other translation systems & custom code

StagLingo is designed around TranslatePress. Do not assume it manages WPML, Polylang, Weglot, or another translation system's data. Custom database tables, headless frontends, and unusual routing need their own assessment.

06 / Preflight checklist

Prove one small workflow first.

Before a full-site job, use one representative page and one target language. Include your real layout, shared sections, and any content type you rely on.

  1. Back up and record your environment.

    Keep a current database and file backup. Record WordPress, PHP, TranslatePress, StagLingo, theme, and relevant plugin versions. Use a safe test environment for changes.

  2. Check TranslatePress before StagLingo.

    Confirm the source language, target language, translated URL, and language switcher behave as expected. Resolve the underlying language setup before testing export or import.

  3. Test the feature you actually need.

    Free can help you evaluate its available controls, settings, and scoring. A complete export/import or Auto Translation test needs Premium access; testing Free alone does not validate those workflows.

  4. Inspect the file and the live result.

    For a Premium file workflow, inspect the export, translate and review it, then import the small batch. Clear relevant caches and compare the live target-language page with the intended result.

  5. Report a reproducible issue before scaling up.

    Send the affected URL and language, exact error, versions, steps, and a sanitized screenshot or log. Remove API keys, passwords, license keys, customer data, and private content. Do not send a full database backup unless specifically requested through an agreed secure process.

Common questions

Compatibility, without the guesswork.

Does StagLingo work without TranslatePress?

No. StagLingo's translation workflows are designed for WordPress sites with TranslatePress installed, active, and configured. It is a workflow layer, not a standalone replacement for TranslatePress.

Do I need Elementor or a particular theme?

No. Elementor is not required, and StagLingo is not tied to a particular page builder. However, the actual text must be accessible to TranslatePress and the selected workflow. Test a representative page rather than assuming every builder widget is covered.

Does Premium include TranslatePress paid features?

No. StagLingo and TranslatePress are separate products. Any TranslatePress plan or add-on required for your languages, SEO fields, or translated URLs must be obtained separately.

Do I need an AI API key for every workflow?

No. Manual Premium export and import can be used with translation and review performed outside WordPress. In-plugin API features require credentials and access for your chosen provider. AI subscriptions and API usage are not included in a StagLingo license.

Is every WooCommerce or membership page supported?

There is no blanket guarantee. Public page text, logged-in content, checkout states, and emails are different surfaces. Test the precise page and state you need, including any relevant extensions, before relying on the workflow.

Is WordPress Multisite compatibility confirmed?

This page does not certify network-wide support or a network license. Contact support with your network setup and intended activation and workflow before purchasing for Multisite.

Why does a translated page still show old text?

First confirm you are viewing the intended target language and clear the relevant page, language, and CDN caches. Then check the import result and whether the text was part of the captured content. Old text alone does not identify the cause.

Does meeting the minimum requirements guarantee compatibility?

No. Minimum versions establish a baseline, not certification for every host, browser, theme, plugin, endpoint, or custom implementation. Test the workflow you need and contact support with reproducible evidence if a problem appears.

For setup, licensing, and broader product questions, visit the StagLingo FAQ.

Your next step

Check the setup.
Then choose the workflow.

Compare editions, follow the documentation, or ask about a specific compatibility concern before you purchase.