If I were to build a blog system I would not store the blog posts in a local merkle tree. Why not? Because a regular database has more benefits. Now why would I want to store the data on a decentralized public merkle tree (blockchain)? I don't want my blogs data to be public, I want *an adjustable view" into non-public, editable and deletable data, which is what we have now. This is one case where the status quo is not only totally fine as you phrased it, but it is superior (to me at least).
The issue I have with web3 is not that it is a new idea, it is that to me it sounds like yet another solution in search of a problem. People who have/are invested in crypto-tokens have a huge incentives to fool themselves into believing you actually can/should solve every problem using the technology of the blockchain.
If it is an problem that people can delete things use an append-only-log/merkle tree. If it is an problem that you want to have a centrally agreed upon public state, open a public API to that append-only-log. If it is a problem that people can neither trust you, nor each other to be a faithful keeper of logs, decentralize it wit consesus algorithms and end up with something like a block chain.
Now this chain of problems is something that fails at the first step for many things. There is not a lot of things that you want to be append-only, typically for very good reasons.
But let's say I want my blog append-only for some reason. One solution would be to just do it instead of forcing myself technically. But lets say I want to force others, then it would make sense.
Now it does not make a lot of sense to make that literal log public, but let's say I also offer an API to it and ignore all the real world problems it would bring (illegal content that needs to be deleted which I could do by rolling the merkle tree back to the latest non-illegal version.
Now I run that sote, why would I like to decentralize that data? So I can claim I don't need to delete anything?