WordPress register_nav_menus Example: Add Theme Menu Locations Cleanly

Last reviewed: May 12, 2026

Theme navigation often starts clean and degrades into hardcoded assumptions once multiple menu areas appear. register_nav_menus() exists to make menu locations explicit, human-readable in the dashboard, and stable enough for front-end rendering code to target by location instead of by accident.

This guide shows how to register multiple theme menu locations cleanly and why the location slugs should be treated like interface contracts.

Register menu locations once during theme setup

<?php
add_action( 'after_setup_theme', 'vulnwp_register_theme_menus' );

function vulnwp_register_theme_menus() {
	register_nav_menus(
		array(
			'primary' => __( 'Primary Navigation', 'vulnwp' ),
			'footer'  => __( 'Footer Navigation', 'vulnwp' ),
		)
	);
}

The theme setup phase is the right place for this because menu locations are part of the theme contract, not request-time behavior.

Keep location slugs stable

The code reference and theme behavior both point to the same operational truth: if you rename a menu location slug, previously assigned menus no longer map automatically to the old location. That means slug changes should be treated like a breaking interface change, not a harmless refactor.

Let the dashboard labels explain purpose, not implementation

The array keys are for code. The labels are for editors and site operators. That distinction helps keep menu management clearer when a theme has multiple placements across header, footer, utility bars, or contextual navigation surfaces.

Common mistakes

• Registering menus too late. Theme setup is the cleaner lifecycle point.
• Renaming location slugs casually. Existing assignments can break.
• Using vague labels. Editors then have to guess which location controls what.
• Treating menu locations as one-off markup details. They are long-lived theme interfaces.

Production checklist

• Register menu locations in after_setup_theme.
• Keep location slugs stable once deployed.
• Use dashboard labels that describe actual placement or purpose.
• Retest menu assignments after theme refactors.
• Render each location deliberately with wp_nav_menu().

Related reading

Pair this with the Walker Nav Menu guide when output markup needs customization and with the wp_get_nav_menu_items article when the menu must also serve headless consumers.

References and further reading

• WordPress Code Reference: register_nav_menus()
• WordPress Theme Handbook: Navigation Menus
• WordPress Code Reference: has_nav_menu()