How to create content directories in WordPress

Write down the information every directory entry will contain. For a staff directory, this might be name, role, department, email, telephone number and photograph. For a resource library, it might be title, topic, author, file and publication year.

Keep fields consistent. If one entry stores a location as “London” and another stores it as “London, UK”, filtering and grouping will become unreliable later.

For a small directory, use regular posts and organise them with categories or tags. WordPress includes these taxonomies by default, and the Query Loop block can filter posts by taxonomy, author and keyword. This is the simplest manual route and is usually enough for a short list of articles, resources or links.

For a larger or more specialised directory, use a custom post type such as “People”, “Documents” or “Locations”. Custom post types keep directory entries separate from blog posts and can have their own archive and single-entry templates. If you create one with code, put it in a plugin or must-use plugin rather than the theme, otherwise changing themes can make the content type disappear from the admin.

Add each directory item as a post or custom post. Give every item a descriptive title, a short summary, a featured image where useful and a consistent body layout. Create categories or custom taxonomies for the things visitors will actually browse, such as department, subject, location or year.

Custom taxonomies must be registered and attached to the relevant post type before they will work properly in queries and filters. A common mistake is registering the taxonomy but forgetting to connect it to the custom post type, which can make terms appear to exist while filtering returns no results.

Create a page called “Directory” and add a Query Loop block. Change its Query Type to Custom, select the posts or custom post type you are using, choose a list or grid layout, and add the Title, Featured Image, Excerpt, Categories and Read More blocks inside the repeating Post Template.

Use the Query Loop settings to set the order, number of entries per page, keyword filter and taxonomy filters. Add the Pagination block so visitors can move through longer lists, and turn on the title and image links so each entry opens its own page.

WordPress core handles posts, pages and taxonomies well, but a polished directory often needs fields such as phone number, address, price, file type or opening hours. You can code those fields and write a custom query and template, but that becomes a maintenance job rather than a simple page setup.

Native keyword and taxonomy filtering is suitable for a small directory. It does not automatically provide a table with sortable custom-field columns, instant multi-filter controls or a convenient way to display large content collections. Search can also omit a custom post type if the query or search configuration restricts the post types being searched.

Open the directory while logged out and test the search, category links, pagination, mobile layout and individual entry links. Check an entry with no image, no excerpt and several taxonomy terms, because empty fields often break an otherwise tidy layout.

If a custom post type or taxonomy has just been added and its archive URL returns a 404, visit Settings > Permalinks and click Save Changes to refresh the rewrite rules. If entries are missing from a filter, check that they are published, assigned to the expected term and included in the query.

For a directory that needs searchable rows, sortable columns, filters and automatic updates, install Barn2 Media Posts Table Pro. Select the content type, choose the columns and insert the resulting table with its Gutenberg block or shortcode. It can display posts, pages, custom post types, custom fields, taxonomies and media without manually entering every row.

This is faster than building a custom archive and filter system, particularly for document libraries, resource directories, member lists, event listings and article indexes. It is also easier to maintain because newly published or edited content can appear in the table automatically.