Over the past four years, I’ve worked on a variety of WordPress projects, ranging from simple business websites and personal portfolios to more complex websites and eCommerce stores. Throughout these projects, I’ve used different plugins to meet different requirements and simplify my development workflow.
I probably have around 100 WordPress plugin names in my head, but there are some that I find myself using much more frequently than others.
So, I decided to create a series featuring the WordPress plugins I regularly use in my projects, along with a few thoughts on how and why I use them.
Let’s start with Part 1!
1. UpdraftPlus — Backup and Restore
UpdraftPlus is probably the most frequently used plugin in my WordPress toolkit. I install it on almost every project because having a reliable backup solution is essential when working with WordPress websites.
It makes creating and restoring backups straightforward, allowing me to back up website files and database content before making significant changes. It’s especially useful before updating plugins, modifying themes, or performing other potentially risky operations.
For me, this is one of those plugins that should be part of almost every WordPress developer’s toolkit.
2. iThemes Security (Now Solid Security) — Website Security
Formerly known as iThemes Security and originally Better WP Security, Solid Security is another plugin I use on many of my projects.
It offers several security features and hardening options, including login protection, two-factor authentication, and tools to reduce common attack risks.
Depending on the configuration, it can also help hide the default login URL and apply other WordPress security tweaks. These measures can help reduce certain automated login attempts, although hiding the login URL alone does not prevent DDoS attacks or guarantee website security.
I find it useful for adding an extra layer of protection to client websites, alongside regular updates, strong passwords, and reliable backups.
3. Hide My Site — Password-Protecting a Website During Development
When a website is under construction, I sometimes prefer to keep it hidden from visitors while allowing my clients to review the progress.
Instead of displaying a generic Coming Soon page, I use a password-protection plugin such as Hide My Site to let selected visitors access the website using a simple password.
This allows my clients to see the actual website as it develops, rather than just a placeholder page. I usually prefer this approach unless my clients have a different choice.
Note: Check the plugin’s current availability and compatibility before installing it on a new project.
4. Child Theme Configurator — Creating Child Themes
Whenever I need to modify theme files, creating a child theme is generally the safer approach. Otherwise, changes made directly to the parent theme may be overwritten when the theme is updated.
Before discovering Child Theme Configurator, I used to go through the entire process of creating child themes manually.
This plugin simplifies the process by helping generate and configure a child theme without requiring me to perform every step myself.
Once the child theme has been created and verified, I can remove the plugin if I no longer need it. The child theme will continue to work independently.
5. Simple Custom CSS — Quick Styling Changes
Not every styling adjustment requires editing a theme stylesheet or creating a custom plugin.
For small CSS changes, I prefer using a dedicated custom CSS plugin. It provides a convenient place to add styling without modifying the original theme files.
This is particularly useful for minor design adjustments, spacing fixes, typography changes, and other quick visual improvements.
For larger projects, however, I prefer keeping custom code organized and maintainable rather than allowing snippets to accumulate without structure.
6. WP Clone by WP Academy — Website Cloning and Migration
For copying or migrating smaller WordPress websites, I’ve used WP Clone by WP Academy.
I found it convenient for transferring relatively lightweight websites between environments. However, it isn’t my first choice for larger or more complex projects, where migration tools may encounter limitations related to website size, hosting configuration, or server resources.
For larger websites, I generally prefer Duplicator, which offers a more structured approach to packaging and migrating WordPress installations.
7. Duplicate Page — Reusing Existing Layouts
In almost every project, I encounter pages with similar layouts. For example, a business website might have several service pages that share the same structure but contain different content.
Instead of rebuilding each page from scratch, I use a duplication plugin such as Duplicate Page.
It allows me to create copies of existing pages or posts so I can reuse their layouts and make the necessary changes. This saves time, particularly on projects with many similar pages.
After duplicating a page, I always make sure to update its title, URL slug, content, metadata, and internal links before publishing it.
8. File Manager — Accessing Website Files
Sometimes, I need to access the WordPress installation’s root directory or work directly with website files.
My preference is to use FTP or SFTP because it provides direct access to the file system without relying on a WordPress dashboard plugin. However, FTP/SFTP access isn’t always readily available when working with a client’s hosting environment.
In those situations, a WordPress File Manager plugin can be a convenient alternative.
That said, file management plugins should be handled carefully because they can expose sensitive website files if misconfigured or compromised. I use them only when necessary and avoid leaving unnecessary file access tools installed.
9. Duplicator — Website Migration and Deployment
When I need to migrate a larger website or move a project between hosting environments, Duplicator is one of my preferred tools.
It helps package a WordPress website for migration, making it useful for moving projects between domains or hosting providers and creating copies for staging environments.
Compared with the lightweight cloning workflow I use for smaller websites, Duplicator is often my choice when a project requires a more structured migration process.
As with any migration tool, I recommend keeping a separate backup and checking the destination website carefully after the transfer.
Final Thoughts
These are some of the WordPress plugins I’ve found useful throughout my four years of working on different projects.
Of course, no single plugin is necessary for every website. The right choice depends on the project’s requirements, hosting environment, security needs, and maintenance workflow. I also try to avoid installing unnecessary plugins, especially when the same functionality can be achieved cleanly with existing tools.
I still have plenty of other plugins to share, including tools for performance optimization, SEO, forms, development, and eCommerce.
This is just Part 1 of the series. I’ll cover more of the plugins I frequently use in upcoming posts.
What WordPress plugins do you find yourself using on almost every project? Let me know in the comments. I’d love to hear which tools other WordPress developers rely on.
Stay tuned for Part 2!
