Step one
Private preview
Generate a private localized preview for one public page before production decisions.
- No code installed for preview
- Public URLs only
- Visible copy, metadata, and structure review
Rollout scoping
Scope WebLingo after a private preview
Public pricing and self-serve checkout are not launch promises yet. Generate a private preview first, then talk through a pilot for public pages.
One account and subscription covers one website; agencies or additional websites are scoped separately.
Rollout paths are scoped manually
Each self-serve account and subscription covers one website. Additional websites need separate scoping or an agency arrangement.
Step two
Production pilot
Scope a limited rollout for public page groups after preview review.
- Path allowlists and exclusions
- Glossary, overrides, and placeholder validation where enabled
- Serve toggle and rollback path planning
Manual scoping
Agency design partner
Evaluate a real client public page without agency billing or workspace promises.
- Unsupported-site checklist
- Readiness report option
- Feedback call before pilot decisions
FAQ
Common questions before you generate a private preview or scope a production pilot.
What pages are in scope?
Public landing pages, docs, pricing, policies, tourism pages, and SEO pages are in scope. Checkout, booking, account, app UI, personalized, and real-time flows are excluded.
Can checkout activate production automatically?
No. Public checkout activation is not promised until billing and backend runtime entitlement authority are connected and tested.
Is there an agency package?
Agency design-partner previews can be scoped manually, but centralized billing, client workspaces, rebilling, team management, and support SLAs are not launch promises.
Will localized pages stay live-updated?
Refreshes run through crawl and translate workflows from approved source snapshots. Avoid treating this as always-on source mirroring or auto-publish.
Ready to see your site in a new market?
Generate a private preview of one public page and see how WebLingo handles localized copy, SEO metadata, and page structure before you publish.