# Taxonomy Book Grids Taxonomy Book Grids are special Book Grids that Mooberry Book Manager automatically generates. You do not need to create a page for them. Taxonomy Book Grids are Book Grids for a single, specific taxonomy item. For example, if one of your Genres is “Contemporary” then Mooberry Book Manager will automatically create a Taxonomy Book Grid for just the books in the Contemporary Genre. For more information about Taxonomies, see [About Taxonomies](https://mooberrydreams.gitbook.io/mooberry-book-manager-v5/about-book-grids/mooberry-book-manager.helpscoutdocs.com/article/34-about-taxonomies). Taxonomy Book Grids are always sorted by title, with the exception of series. Taxonomy Book Grids for a series are ordered by the series ordinal. If you need to specify a different sort order, you will need to create a page and add a Book Grid to that page. To access these Taxonomy Book Grids, you have to get the slug for the series, genre, tag, editor, illustrator, or cover artist. To find the slug, click on the Books menu and choose the corresponding page: Series, Genre, Tag, Editor, Illustrator, or Cover Artist. In the list, find the slug for the item you want in the list on the right. Here is an example of the Genre Taxonomy page: ![](//d33v4339jhl8k0.cloudfront.net/docs/assets/594e95b004286305c68d57d3/images/61a8e56bd3efbe495c3b4b37/file-Ge7XlvrwpE.png) The format for the URL for Taxonomy Book Grids is: [**http://www.your-site.com/{taxonomy-url}/{slug}**](http://www.your-site.com/%7Btaxonomy-url%7D/%7Bslug%7D) Where **{slug}** is the specific item (ie, contemporary) in the list on the taxonomy page, and **{taxonomy-url}** is the value set on the [Book Grids Settings](https://mooberrydreams.gitbook.io/mooberry-book-manager-v5/about-book-grids/mooberry-book-manager.helpscoutdocs.com/article/48-book-grid-settings) Page. By default, Mooberry Book Manager uses these values for the **{taxonomy-url}**: * **Tag**: [http://www.your-site.com/book-tag/{slug}](http://www.your-site.com/book-tag/%7Bslug%7D) * **Series**: [http://www.your-site.com/series/{slug}](http://www.your-site.com/series/%7Bslug%7D) * **Genre**: [http://www.your-site.com/genre/{slug}](http://www.your-site.com/genre/%7Bslug%7D) * **Editor**: [http://www.your-site.com/editor/{slug}](http://www.your-site.com/editor/%7Bslug%7D) * **Illustrator**: [http://www.your-site.com/illustrator/{slug}](http://www.your-site.com/illustrator/%7Bslug%7D) * **Cover** **Artist**: [http://www.your-site.com/cover-artist/{slug}](http://www.your-site.com/cover-artist/%7Bslug%7D) So for example, if you had a “Contemporary” genre with a slug of “contemporary” and you haven’t changed Mooberry Book Manager’s default settings, the URL would be: [**http://www.your-site.com/genre/contemporary**](http://www.your-site.com/genre/contemporary) **NOTE**: There is one case where these special URLs will not work: if the Permalinks settings for your WordPress site are set to “Plain”. In this case, you will not be able to use the URLs as formatted above. > You should change your Permalinks setting if it is set to Plain. This is a good practice not just for Mooberry Book Manager, but for WordPress websites in general. When you use the Plain setting the URLs use numbers to determine what page to display. This means that search engines like Google can’t use your URL to determine if your page should be returned as a result. In other words, setting your Permalinks setting to something other than Plain will help search engines find your site. That’s a good thing! Still need help? [Contact Us](broken://pages/MFQgbpokKLpC592Pw2jk) [Contact Us](broken://pages/MFQgbpokKLpC592Pw2jk) Last updated on December 2, 2021 --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://mooberrydreams.gitbook.io/mooberry-book-manager-v5/about-book-grids/taxonomy-book-grids.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.