You should have considered what makes the users accidentally delete a website before replacing the whole deletion functionality.
Deleting a website is a 2-step verification, so the action is 100% approved by the user.
So the problem is not whether the users wants to delete something, rather than deleting the right thing.
You should enhance the deletion functionality with screenshots of the project or give more information like when it was last edited, or a sum of what it includes etc.
Perhaps consider changing the access of the deletion and it’s position, maybe inside the information of the website, or inside the editor where the user has access visually to see what they delete so it’ll be unlikely to mistakenly perform their action.
The problem comes with the product and user experience teams, not understanding the needs or have the knowledge to know how to understand a need before a change.
You introduced a new feature “Archive” which is something different, and you removed the feature “Delete”. Each has a different use, but none of those can replace each other.
As a new user, what the archive button does for me, is frustration over the control of my data, stealing or saving information for AI use, extra tickets for your support, extra steps to save a domain link from being trapped forever, etc etc.
So the question in the end is, did this change really work?
For me, (the user) no.