How should spoilers be handled in a work review article?

This blog features articles introducing various games.
My basic stance is to introduce the game to people who haven't played it yet, so I try to keep spoilers to a minimum.
However, I feel that it can be quite difficult to write introductions and reviews without giving away spoilers.
This time, I'd like to share my thoughts on how spoilers should be handled in review articles and other similar content.
(Regarding review articles, since they have an element of sharing opinions and impressions, we will consider them separately from introductory articles.)

conclusion

First, I'd like to present the conclusion.

It's a rather unremarkable conclusion, but I think that's about all I can say.
We will discuss this in more detail in the following sections.

Types of spoilers

I think there are many different kinds of spoilers.
In the context of mysteries, a typical example would be something like, "The culprit is so-and-so."
Generally speaking, the whodunit—the question of "who is the culprit?"—is a crucial element that drives the plot of a mystery.
I think there's probably no disagreement that describing who the culprit is constitutes a spoiler.

So, what about the tricks used in that work?
If revealing the trick to the reader could lead to the crucial question of "who the culprit is," then this could also be considered a spoiler.
In particular, if a narrative trick is used, the mere fact that such a trick is being used could constitute a spoiler.

So, what about the story's development?
Would plot points like "So-and-so dies" or "So-and-so betrays us" be considered spoilers?
In my opinion, this would also be considered a spoiler.
The plot twists, which rely on unexpected elements to surprise the reader, are more enjoyable if you're unaware of them beforehand.
Revealing plot twists that the creators are trying to surprise the readers would definitely be considered a spoiler.

In summary, I think whether something is a spoiler or not depends on whether it falls into one of the following categories.

However, I think how to judge this ultimately depends on the judgment of the person making the statement.

Consideration for spoilers

So, how can we be considerate of spoilers?
I don't think there's anything wrong with writing spoilers.
However, I think the worst thing you can do is unintentionally show spoilers to people who don't want to see them.

For example, tweeting spoilers on Twitter, where you don't know who might see them, is a bad idea for a reviewer.
(However, Twitter is supposed to be a tool for freely tweeting whatever you want, so I have no intention of criticizing people who spoil things.)

I think the best way to prevent spoilers is to clearly indicate "contains spoilers" or "no spoilers" within the article.
That way, I think it's possible to prevent obvious spoilers.

However, the problem lies in the subtle spoilers.
This is a situation where the writer of an article doesn't intend to include spoilers, but the reader perceives it as such.
Since it's difficult to completely prevent this, if you're reading articles other than those on the official website, you'll just have to be prepared for a certain degree of risk of spoilers.
If you really hate spoilers, I recommend avoiding searching for information about the work as much as possible and finishing the game as soon as possible.

My excuse for people who hate spoilers

I think that even on this blog, I sometimes unintentionally include spoilers without realizing it.
Ideally, I'd like to convey the charm of the work without giving away any spoilers, but I don't have the skills to do that.
However, I write these articles assuming that people who search for and read introductory articles are looking for more in-depth information about the work than what is presented in the official introduction.

Incidentally, personally, I'm not too shocked even if I get spoiled.
Even if you get spoiled, there are other ways to enjoy it, and there are works that I became interested in after being spoiled.
(Agatha Christie's "Murder on the Orient Express," for example, is a work that I became interested in after learning about its shocking twist.)
Frankly, if there's a work that I'd be embarrassed to have spoiled, I'll watch it myself right away, so I've never had any problems with spoilers.
Because of my own way of thinking, I may not be very thorough in avoiding spoilers in the articles I introduce on this blog.
I have marked any points that I feel would be considered spoilers for anyone with "Spoilers Included".
For now, I intend to maintain the stance of "We will also be careful not to spoil anything, so please take precautions if you don't want spoilers."