Behavior of taxonomy-term classified paths
/admin/config/search/path/patterns is an admin page for the module Pathauto, URL alias - Patterns. And the default pattern for Taxonomy terms just happens to be [term:vocabulary]/[term:name].



You can also see that each "vocabulary" of taxonomy terms can have it's own pattern.

To confirm if Views is handling the display of any of the taxonomy terms pages we need to find a view that takes over the default Taxonomy term path and is already enabled. Meaning, the modules View and Views UI must be enabled. If only Views is enabled, enabling Vies UI at this point makes this easier, plus we will need it later to change the "Sort criteria". With install of the of the Views module the Taxonomy term view is created. This view has a path of 'taxonomy/term/%' the same as the Taxonomy modules default path and when the view is enabled it overrides the Taxonomy module's handling of the display of the taxonomy terms pages.



For a final conformation that this taxonomy vocabulary's term pages are being handled by views lets look at the final HTML that is out generated.



For a views generated page you will see a few key classes in the content's wrapping elements (unless heavenly custom themed).

&lt;div class="content"&gt;
  &lt;div class="view view-taxonomy-term view-id-taxonomy_term view-display-id-page view-dom-id-36a8..."&gt;
    &lt;div class="view-content"&gt; 


vs the generated page you will see from the taxonomy module.

&lt;div class="content"&gt;
  &lt;div class="term-listing-heading"&gt;&lt;div id="taxonomy-term-1" class="taxonomy-term vocabulary-tags"&gt;
    &lt;div class="content"&gt;


Bonus tip: The classes added by the view let us know the machine names of the view being used. view-id-taxonomy_term tell you the "taxonomy_term" view is using used, while view-display-id-page tell you it is the "page" display in current view.