user107: I brought this up on JLU a while ago too. I have some potential questions that I could easily find on other sites just by Googling. For example, the chronological order of a bunch of series/movies in a franchise.
Should these questions not be asked since it's easy to find the answer? Or should we ask them anyway in order to boost what our SE has to offer?

user2159: There's no stupid question, just stupid people asking question... joking.
In all seriousness, Jeff Atwood said one and hundred times that newb questions are allowed and welcomed. Stack Exchange aims to be an authoritative library of information, which users comes and get their questions answered.
Now, don't expect us to upvote a question that lacks research.

user15: If the question is really easy, please no. We shouldn't be aiming at repeating available information in the internet. 
If you want to treat something that is simple but you think that the internet lacks proof or back up for that, then it's a different matter. But asking things like "What's Naruto's last name?" (a stupid example) is really... meh. :)
It's also true that not all information is easy the same way for everybody but let's aim up rather than down.

user107: I think we should allow them. Even if you can find the answer on another site, we want people to come here. By asking these questions here (and providing answers), we are potentially drawing more visitors to the site when they Google the same question which in turn leads to more views and possibly more members if they like the site so much.
These questions should be within reason, though. For example, simply asking "Who is the author of Bleach?" is not a very good question and should not be encouraged just because we allow questions that you can answer with some Googling.

user27: Yes. If a question is good, on-topic question, which is worth asking, why not?
Moreover!
If you know the answer to said question, you can even answer it yourself! 

user62: Yes.
"Too Simple" is something which has been discussed on Stack Exchange before, and was implemented on other sites with a General Reference close reason. It was considered a failure though, since all it results in is users drawing arbitrary lines in the sand for when a question is "too simple", and what sites are considered general reference. 
Furthermore, a tool already exists for questions which are too simple, it's called a downvote. 

This question does not show any research effort; it is unclear or not useful (click again to undo)

As you can see, the case of a question which is too simple is covered by does not show any research effort. With this in mind, there's really no reason to close these questions as well, because down votes are already a sufficient way of dealing with them. 

107: <p>I brought this up on JLU a while ago too. I have some potential questions that I could easily find on other sites just by Googling. For example, the chronological order of a bunch of series/movies in a franchise.</p>

<p>Should these questions not be asked since it's easy to find the answer? Or should we ask them anyway in order to boost what our SE has to offer?</p>
 2159: <p>There's no stupid question, just stupid people asking question... joking.</p>

<p>In all seriousness, Jeff Atwood said one and hundred times that newb questions are allowed and welcomed. Stack Exchange aims to be an authoritative library of information, which users comes and get their questions answered.</p>

<p>Now, don't expect us to upvote a question that lacks research.</p>
 15: <p>If the question is really easy, please <strong>no</strong>. We shouldn't be aiming at <em>repeating</em> available information in the internet. </p>

<p>If you want to treat something that is simple but you think that the internet lacks proof or back up for that, then it's a different matter. But asking things like <em>"What's Naruto's last name?"</em> (a stupid example) is really... meh. :)</p>

<p>It's also true that not all information is easy the same way for everybody but let's aim up rather than down.</p>
 107: <p>I think we should allow them. Even if you can find the answer on another site, we want people to come here. By asking these questions here (and providing answers), we are potentially drawing more visitors to the site when they Google the same question which in turn leads to more views and possibly more members if they like the site so much.</p>

<p>These questions should be within reason, though. For example, simply asking "Who is the author of Bleach?" is not a very good question and should not be encouraged just because we allow questions that you can answer with some Googling.</p>
 27: <p>Yes. If a question is good, on-topic question, which is worth asking, why not?</p>

<h3>Moreover!</h3>

<p>If you know the answer to said question, you can even answer it yourself! </p>
 62: <h1>Yes.</h1>

<p>"Too Simple" is something which has been discussed on Stack Exchange before, and was implemented on other sites with a <strong>General Reference</strong> close reason. It was considered a failure though, since all it results in is users drawing arbitrary lines in the sand for when a question is "too simple", and what sites are considered general reference. </p>

<p>Furthermore, a tool already exists for questions which are too simple, it's called a <strong>downvote.</strong> </p>

<blockquote>
  <p>This question does not show any research effort; it is unclear or not useful (click again to undo)</p>
</blockquote>

<p>As you can see, the case of a question which is too simple is covered by <code>does not show any research effort</code>. With this in mind, there's really no reason to close these questions as well, because down votes are already a sufficient way of dealing with them. </p>
