<p>We have several well-established tags that start with "hierarchical":</p>

<ul>
<li><a href="https://stats.stackexchange.com/questions/tagged/hierarchical-bayesian" class="post-tag" title="show questions tagged &#39;hierarchical-bayesian&#39;" rel="tag">hierarchical-bayesian</a> × 278</li>
<li><a href="https://stats.stackexchange.com/questions/tagged/hierarchical-clustering" class="post-tag" title="show questions tagged &#39;hierarchical-clustering&#39;" rel="tag">hierarchical-clustering</a> × 184</li>
<li><a href="https://stats.stackexchange.com/questions/tagged/hierarchical-analysis" class="post-tag" title="show questions tagged &#39;hierarchical-analysis&#39;" rel="tag">hierarchical-analysis</a> $\to$ <a href="https://stats.stackexchange.com/questions/tagged/multilevel-analysis" class="post-tag" title="show questions tagged &#39;multilevel-analysis&#39;" rel="tag">multilevel-analysis</a> × 783</li>
</ul>

<p>In this situation having a generic <a href="https://stats.stackexchange.com/questions/tagged/hierarchical" class="post-tag" title="show questions tagged &#39;hierarchical&#39;" rel="tag">hierarchical</a> tag is just plain confusing; everybody is supposed to be picking one of the more specific tags instead of using the obviously ambiguous generic one. So we should eliminate it.</p>

<p>It would probably require going through all 142 questions and retagging as appropriate. As always, we can manually retag only questions that are <em>not</em> about multilevel-analysis (based on the numbers above, this seems to be the most common usage). After this is done, the rest can be moved to <code>multilevel-analysis</code> via mod action (to save some time &amp; to minimize flooding the front page).</p>

<p><strong>Update (Nov 1, 2017): This has been finished, and the tag is gone.</strong></p>
