WordPress manage_posts_columns Example: Add Useful Admin List Columns

Last reviewed: May 3, 2026

Admin list tables become more useful when editors can see the right signals without opening every post individually. The manage_posts_columns filter is the core entry point for adjusting the columns shown on the default posts list screen.

This guide shows how to add a focused custom column safely and keep the list table useful instead of overloaded.

Add a new column through the posts columns filter

<?php
add_filter( 'manage_posts_columns', 'vulnwp_add_review_state_column' );

function vulnwp_add_review_state_column( $columns ) {
	$columns['vulnwp_review_state'] = 'Review State';
	return $columns;
}

The filter should always return the full columns array. It is not a fire-and-forget mutation point.

Render the column content in the matching action

add_action( 'manage_posts_custom_column', 'vulnwp_render_review_state_column', 10, 2 );

function vulnwp_render_review_state_column( $column, $post_id ) {
	if ( 'vulnwp_review_state' !== $column ) {
		return;
	}

	echo esc_html( get_post_meta( $post_id, 'vulnwp_review_state', true ) ?: 'Pending' );
}

Define the column and its renderer together. A column without a clear render path is just dead admin chrome.

List screens should surface decisions, not everything

A useful custom column makes triage faster. Ten extra columns usually make the table harder to scan. Add signals that change real editorial behavior, not trivia.

Remember post-type-specific alternatives exist

The WordPress docs note that manage_posts_columns is for the posts screen. If a custom post type needs its own columns, use the more specific hook for that object type.

Production checklist

• Return the full columns array from the filter.
• Pair the new column with a dedicated render callback.
• Keep the added signal editorially meaningful.
• Use post-type-specific hooks when the table is not the default posts screen.
• Test sorting, bulk actions, and narrow admin widths after changes.
• Document custom columns that editorial teams depend on.

Common mistakes

• Adding columns with no renderer. Empty admin cells help no one.
• Overloading the list table. More columns are not always better.
• Using the generic hook for the wrong screen. Scope matters in admin tables.
• Skipping layout tests on smaller screens. Admin tables degrade quickly.
• Surfacing data that does not influence workflow. Noise compounds over time.

Related reading

If the same information should also appear inside the edit screen, pair this with the meta box guide. If the signal belongs on the admin landing screen instead of a list table, continue with the dashboard widget article.

References and further reading

• WordPress Code Reference: manage_posts_columns
• WordPress Code Reference: manage_posts_custom_column
• WordPress Code Reference: get_post_meta()