LIFEHACKS . META . STACKEXCHANGE . COM {}

Analyzed Page
Matching Content Categories
CMS
Monthly Traffic Estimate
How Does Lifehacks.meta.stackexchange.com Make Money
Keywords
Topics
Questions
Schema
Social Networks
External Links
Analytics And Tracking
Libraries
CDN Services

We are analyzing https://lifehacks.meta.stackexchange.com/questions/1256/close-reason-request-they-havent-tried-anything/1262.

Title:
Close reason request: They haven't tried anything - Lifehacks Meta Stack Exchange
Description:
Can we have a close reason such as this: Questions that don
Website Age:
16 years and 0 months (reg. 2009-06-12).

Matching Content Categories {📚}

Cryptocurrency
Social Networks
Video & Online Content

Content Management System {📝}

What CMS is lifehacks.meta.stackexchange.com built with?

Custom-built

No common CMS systems were detected on Lifehacks.meta.stackexchange.com, and no known web development framework was identified.

Traffic Estimate {📈}

What is the average monthly size of lifehacks.meta.stackexchange.com audience?

🚦 Initial Traffic: less than 1k visitors per month

Based on our best estimate, this website will receive around 513 visitors per month in the current month.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Lifehacks.meta.stackexchange.com Make Money? {💸}

We find it hard to spot revenue streams.

While many websites aim to make money, others are created to share knowledge or showcase creativity. People build websites for various reasons. This could be one of them. Lifehacks.meta.stackexchange.com has a secret sauce for making money, but we can't detect it yet.

Keywords {🔍}

question, questions, close, answer, reason, dec, work, scope, problem, solution, commented, answers, site, doesnt, lifehacks, alternative, badges, didnt, people, dont, require, solve, add, sterno, offtopic, method, comment, bad, zach, rule, quality, users, teams, stack, lifehack, share, follow, mooseman, silver, bronze, zachsaucier, made, answered, things, ontopic, solutions, policy, message, person, reasons,

Topics {✒️}

lifehacks stack exchange stack overflow life hacks tumble-dry wet sneakers professional tumble-dry sneakers question tumble-drying sneakers shell echo command user contributions licensed specific close reasons common-sense answers policy saved tumble-dry question bake potential answers paying lip service add additional details main content log pretty unfriendly atmosphere helped improve question improve question quality explicit close reason policy crazy thing works discouraging bad questions downvoting conventional answers official site scope close reasons substitute tool require downvoting bad questions custom close reason topic close reason question makes date modified meta questions require 'solutions conventional tool substitute tool higher quality high quality quality answers quality control teams users running sneakers question official reason main reason duplication works tags require users close reason

Questions {❓}

@ZachSaucier How's that?
Another question I'd ask is what problem(s) you currently see with the sneakers question that you feel would be fixed once the "What have you tried?
Can you point to one or two questions (that weren't obvious trolls) that this policy saved us from?
Does all questions require 'solutions already tried'?
Does phenolphthalein crystallise as sodium salt?
How do we define what is on-topic without requiring the questioner to know the answer to their question?
How does neutron degeneracy pressure fail in the formation of a black hole?
How is an answer determined to be on-topic?
How to improve question quality?
I DO understand the initial reasoning behind this — when someone asks how to get rid of roaches, you want to ask what's wrong with bug spray?
If I want to know what to do with those slivers of soap that are too small to bathe with, rubber-stamping everything with "what have you tried?
In your opinion, has closing questions for this reason actually worked to limit us to only "hacky" questions or improved things in any other way?
Is 'too specialized' a reason to close vote?
Is that not good enough?
Should I post a whole new question, saying I tried that answer and that it didn't work for me, and thus I need a different hack?
Should we be downvoting conventional answers?
Should we be voting to close questions that don't appear to have a hack answer?
Should we require a certain amount of research from people asking questions?
Should you ask questions you already know the answer to?
What does Jesus mean by 'the day of judgment' in Matthew 11:24?
What does it fix?
What happens when people have the same question but tried different things?
What happens when the potentially best answer didn't work for the original asker?
What is the best way to tumble-dry wet sneakers?
What, are you going to come to my house and check that I'm telling the truth?
What, exactly, is the obvious answer to this problem that he should list trying before we allow it to be open?
Why do we use \c (escape c) to end the output of the shell echo command?
Do we now allow a duplicate version of the question, which is the same in all respects except for the "What have you tried that didn't work?

Schema {🗺️}

WebSite:
      context:https://schema.org
      name:Lifehacks Meta Stack Exchange
      url:https://lifehacks.meta.stackexchange.com

Social Networks {👍}(4)

External Links {🔗}(62)

Analytics and Tracking {📊}

Google Analytics
Google Analytics 4
Google Tag Manager

Libraries {📚}

jQuery

CDN Services {📦}

Cookielaw
Sstatic

2.79s.