The first time we tried to update a client’s custom plugin without FTP, we just stared at the screen. Then we found WP Pusher. This guide shows how to use WP Pusher to deploy WordPress themes and plugins straight from GitHub, Bitbucket, or GitLab, with the guardrails we use on real client sites here in our Atlanta studio.
Points clés à retenir
- WP Pusher enables direct deployment of WordPress themes and plugins from GitHub, Bitbucket, or GitLab without requiring FTP access, making it ideal for shared hosting environments and freelancers.
- Enable Push-to-Deploy through webhook configuration to automatically update your site when you push commits to your repository, reducing manual WordPress admin work to seconds.
- Always use WP Pusher with a staging environment first, implement branch protection rules, enable automated backups via UpdraftPlus or similar tools, and maintain a clear rollback strategy before deploying to production.
- Connection to private repositories requires a $39/year license per site, while public repos are free, and OAuth tokens provide secure authentication without exposing raw passwords.
- The installation process takes approximately two minutes—simply download the ZIP from wppusher.com, upload it through the WordPress plugin interface, and activate it without needing command-line access.
What WP Pusher Does (And When to Reach for It)
WP Pusher installs and updates WordPress themes and plugins directly from a Git repository, skipping FTP entirely. You point it at a repo, click install, and the plugin pulls the files into wp-content/.
We reach for it when:
- A client is on shared hosting with no SSH access
- We manage 10+ sites and need version-controlled custom code
- A freelancer wants “push-to-deploy” without setting up CI/CD
For a side-by-side with backup-focused tools, our Total Upkeep comparison breakdown covers where each one fits.
Installing and Activating WP Pusher on Your Site
Grab the ZIP from wppusher.com, then upload it through the WordPress admin. No command line required.
Steps:
- Download the ZIP from the official site
- Go to Plugins > Add New > Upload Plugin
- Select the ZIP, click Install Now, then Activate
- Open the new WP Pusher menu in the sidebar
The install takes about two minutes. Action today: install it on a staging copy first, not production. We’ve seen this save a finance client a frantic Friday rollback. Our WP Pusher review notes cover server requirements in more detail.
Connecting WP Pusher to GitHub, Bitbucket, or GitLab
Public repos work free. Private repos need a license at $39/year per site. Connection happens through OAuth tokens, not raw passwords.
In the WP Pusher settings:
- Click the GitHub, Bitbucket, or GitLab tab
- Use the one-click “Connect” button to generate a token
- Paste the token back into WP Pusher
- Activate your license key under the License tab for private repo access
If the OAuth flow stalls, the open-source mirror on GitHub and threads on Stack Overflow developer Q&A both have working token examples we’ve used to debug auth issues.
Pushing Themes and Plugins From a Repository
In WP Pusher > Install Plugin (or Install Theme), enter the repo owner and name, pick a branch, and click install. The files land in wp-content/plugins/ instantly.
Manual updates are one click from the WP Pusher dashboard, which means a client edit to master is live in under 10 seconds.
Configuring Updates, Branches, and Webhooks
Enable “Push-to-Deploy” per repo to auto-update on every git push. WP Pusher generates a unique webhook URL for each plugin or theme.
Setup:
- Toggle Push-to-Deploy on the plugin/theme detail page
- Copy the webhook URL
- In your repo settings, add it under Webhooks (GitHub), Hooks (Bitbucket), or Integrations > Webhooks (GitLab)
- Set the branch, e.g.,
mainfor production,developfor staging
Which means a git push origin main redeploys without anyone logging into WordPress. For teams running Lighthouse audits before shipping, the Chrome DevTools documentation pairs well with this flow as a pre-push check.
Guardrails: Staging, Backups, and Safe Rollbacks
WP Pusher does not back up your site. You need a separate plugin and a staging environment. This is the part most tutorials skip.
Our standard guardrail stack:
- Staging site with Push-to-Deploy pointed at a
developbranch, our WP Staging walkthrough covers the cloning step, and the WP Stagecoach setup guide is the alternative we use for larger sites - UpdraftPlus for nightly off-site backups to S3 or Google Drive, host-side options are documented across AWS storage and hosting blogs
- Branch protection on
mainso nothing deploys without a pull request review - Rollback path: revert the commit in Git, then click manual update in WP Pusher
Action today: before turning on Push-to-Deploy in production, run it in shadow mode on staging for one week.
Conclusion
WP Pusher turns Git pushes into WordPress deployments, which means hours of FTP drudgery become a 10-second commit. Start with a public repo on staging, add backups, then promote to production. If you’d like us to set the pipeline up for your team, book a free consult with our agency.
Frequently Asked Questions About WP Pusher
What is WP Pusher and what does it do?
WP Pusher is a WordPress plugin that installs and updates themes and plugins directly from Git repositories (GitHub, Bitbucket, or GitLab), eliminating the need for FTP. It enables automated deployments through push-to-deploy functionality, making it ideal for agencies and freelancers managing multiple client sites with version-controlled code.
How do I install and activate WP Pusher on my WordPress site?
Download the ZIP file from wppusher.com, then go to Plugins > Add New > Upload Plugin in your WordPress admin. Select the ZIP, click Install Now, then Activate. Access the WP Pusher menu from your sidebar. Installation takes about two minutes. Always test on staging first before activating on production.
Do I need a license to use WP Pusher with private repositories?
Public repositories are free with WP Pusher. Private repositories require a license at $39 per year per site. Connection uses OAuth tokens for secure authentication, not raw passwords. Activate your license key in the WP Pusher settings to unlock private repo access.
How does push-to-deploy work in WP Pusher?
Enable push-to-deploy per repository to automatically update your WordPress site whenever code is pushed to Git. WP Pusher generates a unique webhook URL for each plugin or theme that you add to your repository settings. A git push to the configured branch (e.g., main or develop) triggers instant deployment without WordPress admin login.
What backup and rollback options does WP Pusher provide?
WP Pusher does not include built-in backups. Use a separate backup plugin like UpdraftPlus for nightly off-site backups. For rollbacks, revert the commit in Git, then click manual update in WP Pusher. Implement branch protection on your production branch to require pull request reviews before deployment.
Can I use WP Pusher on shared hosting with no SSH access?
Yes, WP Pusher is ideal for shared hosting environments with no SSH access. It deploys WordPress themes and plugins without requiring command-line access. This makes it perfect for clients on limited hosting plans who need version-controlled code deployments without SSH or FTP complications.
Certains des liens partagés dans cet article sont des liens d'affiliation. Si vous cliquez sur l'un de ces liens et effectuez un achat, nous percevrons une commission d'affiliation, sans que cela n'entraîne de frais supplémentaires pour vous.
Nous améliorons nos produits et nos publicités en utilisant Microsoft Clarity pour analyser votre utilisation de notre site web. En utilisant notre site, vous acceptez que nous et Microsoft puissions collecter et utiliser ces données. Vous trouverez plus d'informations dans notre politique de confidentialité à l'adresse .
