As a WordPress service provider, I was forced to create dozens of sites for various clients. When I started designing sites in a way rather industrial (in particular for PBN), I had to find solutions for accelerate my creation processes.
If it is not yet possible to automate the creation of webdesign (although there is movement with ZipWP), the technical part is perfectly automated.
Indeed, quite quickly, I realized that the technical base that I used was always the same. I then decided to create a WordPress said « Stack » or « Starter Site », including all my set of plugins and configurations.
In this way, I would only have to duplicate this stack in order to earn almost ten hours on each new project.
This is how it was born. OCOPOTM. And it's working like a thunder.
I'm talking about this in this article.
Contents
The need to save time
Saving time when service providers often means earning more. If you knew how true it is for the creation of sites...
Today, there are lots of tools of all kinds to make us win:
- IAA to generate content, see visuals
- Webdesign templates
- cPanel with duplication of sites
But one was missing.
A WordPress ready to use, technically speaking. That is, a WordPress configured, optimized from a performance point of view and secure. They're called « Starter Site », « Site Template », « Stack »…
The loop is closed. We duplicate our starter site, y install Envato template of our choice, Write our content using AI.
Damn, excuse me for the term, but do we realize the time we live in? I think it's extraordinary.
And for me, COPOTM is part of this revolution. For, not only does it actually save a phenomenal time to the one who uses it, but it is also accessible to anyone.
No technical expertise is required, if this is to know how to install a plugin on WordPress.
Now I'd like to talk to you about Financial aspect What makes this kind of solution come out. I told you earlier about saving time and therefore money.
But there is another aspect on which everyone wins. This is the final quality of the project.
Imagine.
Instead of designing a site in 25 hours, you only need 18 hours. But you keep charging the same thing as before, because you can afford it. Your competitors cannot charge less to be profitable for the same project.
You then earn 7 hours of invoiced work, very well. I could stop here that it would be very good already. But I'll go further as far as I'm concerned.
I'm charging the same as before, but I still spend 25 hours on my client's project.
Why?
For I can deliver more on points that can really make a difference for him (and therefore for me). I can pass more time on design, more time on its SEO or more time on the audit of his business in order to help him more.
Do you imagine the surplus value for your customers ? I do, because it's life. They will never stop recommending you to their network, and you will no longer have to prospect.
In short, all of this to tell you that saving time on the technique has allowed to deliver much more successful projects for a budget similar to before COPOTM. And that, when you try to create a sustainable business, it's a blessed bread.
Security at the point
Security's not something to take lightly. A hacked site can blow a business. I've seen too many sites get hit because of security flaws that could easily have been avoided.
So for OCOPOTM, I didn't screw up. I called on a cybersecurity expert to test the installation under all the seams. Result: RAS. It doesn't mean it's infallible, but it's going on good bases.
I have incorporated most of the good practices that are possible and applicable for the largest number of projects. You can read more in this article (I warn you, it's bald): https://wpocopo.com/wordpress/securer-worpdress/
Of course, We're not safe. whether a plugin present on COPOTM is subject to a fault. It is also quite natural that an extension knows about it in its lifetime. What really matters is the speed of the team to take the necessary steps to correct it.
It's a bit the ransom of glory when you have a system as open as WordPress. It's definitely its greatest strength, but it may prove dangerous. Finally, we're not here!
If you are interested, for selecting plugins natively present on OCOPOTM, I helped myself a lot from the section Vulnerabilities Intelligence WordFence : https://www.wordfence.com/threat-intel/vulnerabilities/
Quite simply, I analyzed the frequency of security flaws of each plugin and analyzed if they were plugged quickly. I selected only the strongest ones.
Performance and more simply
I often hear that WordPress is a gas plant, It's slow...let me tell you very frankly. That's bullshit.
When you know how to manipulate the beast, WordPress can be very powerful, even using a builder page like Elementor.
I literally passed a site designed with Elementor on Discover, all metrics of CWV green.
In short, all this to tell you that WordPress is not necessarily slow, but that you must certainly learn to optimize and not do anything.
It starts with a good choice of theme.
By default, always opt for a style theme « starter » as Astra or GeneratePress. They are very light and customizable. The second less than the first if you don't have a basic in dev.
By choosing this kind of theme, you already have a good chance of having good native performances.
Second, we must understand and know how to use tools such as LiteSpeed or WP Rocket. These tools make it possible to apply very extensive optimizations, in fairly simple ways. In particular, it is possible to remove the unused CSS, which is one of the most important optimizations.
Same for the images, for which there is much to do. But I'm not going to eternize on the WebPerf, which would deserve a full dedicated article.
To make this kind of optimization accessible to everyone (which is not easy!), I created configuration files. In these files, the entire configuration of the plugin they are intended for is ready and totally designed to work with OCOPOTM.
So, to sum up, anyone using OCOPOTM to import two clicks these files and so benefit from high performance. This does not concern itself with the technique or with fear of breaking his site, because it is thought specifically for this WordPress.
Ideal for what type of projects?
I believe that this kind of tool is particularly suitable for service providersLike me. But looking more closely, many independent site editors also use for their personal projects.
These independent publishers, however, do not represent the bulk of my clientele, but they are well represented.
So, for me, it's ideal for WordPress site creators. You save time, you deliver a better quality site, your customers are happy, you earn more. The whole chain wins.
Now, if we talk about site typology, I'll say it's still better to use OCOPOTM for serious projects., not for PBN. I find it a shame to use such a pretty base not to make the project visible, although I understand perfectly those who use it for that.
After all, time saving remains a time saving.
Conclusion
Good. In conclusion, I would simply say that this tool allows those who do not necessarily have the skills to design technically robust and reliable sites are delighted.
Same for those who may have them, but had not thought of using such a technique in their process. To those, I would simply say: interested in COPOTM. And if they're not convinced, why not create their own stack?
