Frequently Asked Questions

WP SiteLauncher is designed to help web designers, developers, and agencies streamline collaboration, manage tasks, and centralize communication directly on their WordPress sites. Whether you’re an individual freelancer, a small agency, or a growing team, our tools are built to simplify your workflow and save time.

For a more detailed comparison and insights to help you decide, check out this page where we break down how WP SiteLauncher compares to similar tools and fits different needs.

Yes, we are proud to say that all features are included in every plan! We want to ensure all users can fully utilize the suite of interconnected tools we’ve created. While we do limit the number of sites, users, and storage for each plan, these are the only differences between plans. This means that you get the complete experience, regardless of the plan you choose.

Yes! It sounds crazy, but it's true. Every WP SiteLauncher plan includes unlimited users at no extra cost. We believe real collaboration involves real people. Whether you’re working with a team, contractors, bringing in clients, or looping in specialists, we’ll never charge you extra just to get the job done. Other platforms might treat users as a pricing tier, but we treat them as the heart of the system.

In WP SiteLauncher, a “site” is any WordPress website you’ve added to your account, whether currently connected or disconnected. Each plan includes a maximum number of sites you can manage at once: 10 for Hobby, 100 for Freelancer, and Unlimited for Agency. The site limits are specific to your WP SiteLauncher account and do not affect your actual WordPress sites.

When you connect a new WordPress website by installing the plugin and logging in, a "site" is created in your account. You can uninstall or deactivate the plugin, but it will remain listed and still count toward your plan until you delete it from your WP SiteLauncher account.

It’s important to note that disconnecting or deactivating the plugin does not remove the site from your account. To stop it from counting toward your site total, you’ll need to delete it from your account. Before doing so, you can export all site data to back it up on your own server if needed.

You can keep a site connected to your WordPress website even after it goes live, which is common for ongoing feedback, change requests, or general site-related communication. Alternatively, you could delete it from your account when a project is complete to free up a slot for a new site. 

Yes, you can switch between Individual, Freelancer, and Agency plans, as well as monthly and yearly billing, at any time from your account. It's incredibly easy! Just navigate to your customer dashboard, click on the 'Plans' tab, and select your desired plan. Your payment will be prorated accordingly.

Yes, all features are included in the 15-day free trial. The trial's terms are based on the plan you select, so the number of sites, users, and storage will reflect your chosen plan. Otherwise, there are no limitations on features during the trial period; it functions like a regular subscription.

The storage limit is essential because our plugin generates data that needs to be stored on our cloud servers for your connected app, which incurs costs to us. We've set generous storage limits per plan, which should cover more than enough expected usage for most sites and what's financially feasible for us. Rather than limiting features (all plans have full access to all features), we've chosen to implement caps on sites, users, and storage instead. Please choose a plan based on your anticipated site and user needs, and this should also cover any storage needs. You can always upgrade to a higher later plan if additional storage is required.

Yes, WP SiteLauncher is fully committed to data privacy and GDPR compliance. To ensure the highest standards, we have strategically placed our app account servers in the Netherlands, within the European Union. This means your data is stored in accordance with strict GDPR regulations. Additionally, we use Digital Ocean servers, a trusted provider that adheres to stringent data security protocols. Your privacy and data security are at the core of our service, and we continuously monitor and update our infrastructure to meet GDPR requirements. 

Your chosen plan determines the limits for sites and storage. If you need more sites or storage, you can upgrade to a higher plan.

If you need anything beyond what our agency plan offers, don't hesitate to get in touch with us for a custom solution.

An active subscription is required to use and access the WP SiteLauncher plugin and app. Without an active license, the plugin and app functionality will cease to function. To avoid interruption, please ensure your payment card information is up-to-date and watch for important renewal emails to continue using and accessing WP SiteLauncher.

After completing the checkout for your desired plan, you will be prompted to proceed to our Getting Started Guide, which is very thorough and helpful. We strongly recommend following this guide step-by-step.

From there, you can log in to your customer dashboard, download the plugin files, and access the app where you can manage your sites. After some initial account setup in the app, go ahead and install the plugin on your WordPress website, log in through the plugin interface to connect the app, and you're ready to start collaborating on your WordPress website!

Yes, WP SiteLauncher is compatible with WordPress Multisite, but each child site operates independently within the network. This means that WP SiteLauncher does not function as a single installation across the entire multisite network. Instead, it runs separately on each child site, just like it would on standalone WordPress websites.

Do I need to use a separate site from my WP SiteLauncher plan for each child site in a WordPress Multisite network?

Yes, each child site in the network counts as a separate site in your WP SiteLauncher plan. Since each site in a multisite setup has its own database, WP SiteLauncher needs to store its data separately for each child site. This ensures that tasks, requests, and other features work correctly within each site.

For example, if your network consists of:

• Main site: example.com
• Child site 1: abc.example.com
• Child site 2: xyz.example.com

Each of these sites would count as a separate site in your WP SiteLauncher plan. You would need to have enough sites available in your plan to use WP SiteLauncher on all the sites where it’s needed.

Why isn't WP SiteLauncher a network-wide installation

Because WP SiteLauncher integrates deeply with each WordPress site’s frontend and backend, it needs to store data and user roles separately for each site. Allowing a single site allocation across multiple child sites could lead to unintended use across multiple projects, which is why each site in the network is treated as a separate site in your WP SiteLauncher plan.

WP SiteLauncher is designed to work seamlessly with staging sites and live sites, depending on how you structure your workflow. There are two main approaches:

1. The Recommended Staging Workflow

If you’re building a new website at a staging URL (like staging.example.com), you can install and connect the WP SiteLauncher plugin there and begin using all the features like tasks, feedback, approvals, client communication, etc. as usual. This setup is ideal for collaboration during development.

When the website is ready to go live, you’ll typically use a migration plugin or your hosting provider’s built-in staging tools to move the site to the live domain (e.g., from staging.example.com to example.com).

After the migration:

• The live site (example.com) will have the WP SiteLauncher plugin installed and activated, but not connected to your app account. You can safely uninstall the plugin at this point, or leave it disconnected until you’re ready to start using it.
• The staging site (staging.example.com) will remain the connected site where all your WP SiteLauncher data like  tasks, comments, and communication continues to live.

This lets you keep building and collaborating in the staging environment without cluttering the live site with in-progress work or WP SiteLauncher elements.

2. Replacing the Staging Site with the Live Site

If you decide to shut down the staging site and continue working only on the live site, you can easily transfer all your WP SiteLauncher data to the new domain.

Here’s how:

• Log into your WP SiteLauncher app and go to Sites page to the Site Settings.
• In the Advanced tab, update the connected site URL from the staging domain to the live domain.
• All tasks, feedback, comments, and other WP SiteLauncher data will now point to your live site (example.com) instead of the staging site.

Once that’s done:

• Log in to the WP SiteLauncher plugin on the live site.
• You’ll be able to continue working right where you left off with the same interface, same tools, and all your data.

If the live site has the same structure (same page builder and pages), everything will appear in the same places. If pages have been deleted or major structural changes were made, or if you switched page builders, some comments may no longer be anchored to specific page elements. In that case, you can still find all your comments under Toolbox → Comments.

WP SiteLauncher supports multiple languages for both the WordPress plugin interface and the web app interface, so you and your clients can use the platform in your preferred language.

Currently Supported Languages

We currently offer full support for:

• English
• French
• Spanish
• German

How Translations Work

In the WordPress Plugin:

The plugin follows standard WordPress translation practices. The interface language is determined by the “Language” setting in your WordPress User Profile Settings—the standard way WordPress handles plugin and theme translations.

If a supported translation is available for the selected language, WP SiteLauncher will automatically display the plugin interface in that language.

In the Web App:

The app interface (dashboard) also supports multiple languages. You can change the app language by clicking your profile name in the top-right corner and selecting your preferred language from the language switcher.

Requesting a New Language

If your language isn't available yet, you can request it. We’re happy to add new languages for both the plugin and the app, and we welcome your help in confirming translations.

For the plugin:

• You can use the provided .pot file to create your own translation file (.po/.mo).
• This allows you to use your preferred language even before we officially add it.

For the app:

• All translations must be added by our team, but we’ll work with you to make sure everything is accurate and user-friendly.

WP SiteLauncher combines the best of modern and traditional web technologies to deliver a seamless experience. The frontend of both the WordPress plugin and the web app is built with React.js, ensuring a dynamic and interactive user interface. The plugin’s backend is powered by WordPress, meaning it leverages WordPress’s core framework, including its REST API, hooks, and database systems, to handle server-side logic and ensure seamless integration with the WordPress ecosystem. It is developed with standard WordPress plugin code, primarily using PHP and JavaScript, to ensure compatibility with WordPress sites. The web app’s backend is built with Laravel, providing robust and scalable server-side performance. This hybrid design blends flexibility, reliability, and performance across platforms.

No, WP SiteLauncher has minimal impact on your website's performance. Here’s how:

• No Dependency on Your WordPress Database
  WP SiteLauncher doesn’t store data in your WordPress database, which means there’s no extra load on your database, no slower query times, and no risk of unnecessary database growth.
• Optimized Frontend
  The plugin’s frontend is built with React.js, which is designed for speed and efficiency. React uses a virtual DOM to handle updates smoothly, so it minimizes changes to your site’s actual DOM and keeps page load times fast.
• Efficient Backend Integration
  On the backend, WP SiteLauncher uses WordPress’s framework for compatibility while keeping resource usage light. It avoids heavy processes and unnecessary database queries to ensure your server runs efficiently.
• Asynchronous Processes
  For app-side operations, the plugin relies on a Laravel backend. This separates more demanding tasks, like API calls or data processing, from your WordPress environment, keeping your site’s performance unaffected.
• Small Footprint
  The plugin is designed to load only the scripts and styles it needs, and it does so conditionally to avoid unnecessary global resource usage.

Real-World Testing:
In performance tests, WP SiteLauncher has shown no noticeable impact on page load times or server response times for typical WordPress sites. Its lightweight design ensures it integrates seamlessly without compromising performance.

WP SiteLauncher is designed to be theme-agnostic, meaning it works independently of your website’s theme or page builder. It does not modify or interfere with your theme’s design, making it compatible with virtually all WordPress themes and page builders.

We have tested WP SiteLauncher with several popular themes and page builders to ensure seamless functionality, including:

Themes:

• Twenty Twenty-Four
• Twenty Twenty-Five
• Divi
• Astra
• Hello
• GeneratePress
• Bricks
• Kadence
• OceanWP

Page Builders:

• Divi Builder
• Elementor Pro
• Breakdance

While WP SiteLauncher functions on the frontend of your website, its interface does not currently open within page builder editing modes (such as Divi Visual Builder or Elementor’s editor) or in the WordPress admin area. We are currently working to expand compatibility to these areas for a future update.

If you use a different theme or page builder, WP SiteLauncher should still work as expected. However, if you experience any issues, let us know so we can investigate. We continuously test and improve compatibility based on user feedback.