MB Admin Columns

MB Admin Columns changes the information shown in WordPress post and page lists, replacing a fixed set of admin columns with a layout built around the data you manage. It supports posts, pages and custom post types, and brings custom field values into the list table so an editor can inspect important details without opening each item. The same approach extends to taxonomies and user data, giving the back end a more useful view of structured content.

Columns with purpose

The main strength is the choice of information placed beside each post. Instead of treating the list table as a simple title-and-date index, you can add fields that describe the content itself. A catalogue entry, for example, can show a selected value or checkbox state next to its title, while an editorial list can expose another custom field used to track content. The result is a list shaped around the site’s content model rather than WordPress’s default view.

Layouts are customisable for posts, pages and custom post types. MB Admin Columns also includes a drag-and-drop interface for rearranging columns, which keeps the ordering task separate from the field configuration. That is useful when the most important information needs to sit at the start of the table and secondary values should remain available without dominating the screen.

Structured data in view

The plugin covers more than plain text field output. Its stated data-type support includes images, checkboxes and select fields, so the admin table can represent different kinds of metadata rather than reducing every value to the same format. Taxonomies and user data are also part of the feature set. Term data requires MB Term Meta, and user data requires MB User Meta, making those integrations relevant to sites already using the corresponding Meta Box extensions.

Sorting and filtering options add another layer to the list view. They are aimed at finding and organising entries by the information displayed in the columns, rather than relying only on post title, date or status. The vendor also lists integration with Advanced Custom Fields and WooCommerce, which positions the plugin for sites where content fields or product information are central to day-to-day administration.

Migration between sites

Column arrangements are not limited to one manually configured screen. MB Admin Columns includes export and import settings, allowing a layout to be moved between sites. That is a practical inclusion for agencies and developers maintaining similar content structures, as well as for a site owner who wants to preserve an established admin arrangement during a rebuild. The value of this feature rests on the receiving site having compatible post types and data available, but it gives the configuration a clearer path beyond a single installation.

What to weigh

MB Admin Columns focuses on the WordPress back end. Its purpose is to improve the tables used to manage content, not to alter how custom fields, taxonomies or user data appear on the public-facing site. It is therefore a specialised administration tool rather than a complete content-management layer.

There are also dependencies around the wider data model. Term and user columns require MB Term Meta and MB User Meta respectively, so those functions are not self-contained in MB Admin Columns. The range of supported fields, layouts, sorting and filtering also means there are more configuration decisions than with the default list table; the benefit comes after choosing which columns are genuinely useful for each content type.

Who it suits

This plugin fits administrators and content creators who manage structured WordPress content from list screens. It is particularly relevant to sites with custom post types, field-heavy editorial workflows, WooCommerce data or a need to inspect metadata while browsing entries. Developers and agencies gain a way to standardise column layouts and transfer settings between sites, while editors get a more informative table for routine content management. Sites that only use the default title, author and date columns will find its scope less compelling, but teams working with custom fields have a clear reason to consider it.