WordPress Theme Functions: The Hooks Worth Knowing

WordPress's hook system (actions and filters) lets themes and custom code modify behavior without editing core files. Understanding the most useful hooks unlocks customization that doesn't require template overrides.

The hooks worth knowing for typical customization are a small subset of the hundreds WordPress provides. Knowing this subset handles most common needs.

wp_enqueue_scripts

The action where you add CSS and JavaScript to the front-end. Themes and plugins register their assets here.

add_action('wp_enqueue_scripts', function() {
    wp_enqueue_style('custom-style', get_stylesheet_directory_uri() . '/custom.css');
});

The function runs during page rendering, before assets are output. The right place to add or remove site assets.

the_content

The filter that modifies post content before it's displayed. Useful for: adding elements to the end of every post, replacing specific patterns, transforming content programmatically.

add_filter('the_content', function($content) {
    return $content . '<p>Subscribe to our newsletter for more!</p>';
});

The filter affects the_content() output everywhere it's called.

wp_footer and wp_head

Actions for adding content to the page's head or footer. The most common hooks for inserting tracking scripts, analytics, custom HTML.

add_action('wp_head', function() {
    echo '<meta name="custom-tag" content="value">';
});

Most plugins that add tracking code use these hooks.

save_post

The action when a post is saved. Useful for: triggering side effects when content changes, validating content, updating related records.

add_action('save_post', function($post_id) {
    // Custom logic when posts are saved
});

The hook runs on every post save, including auto-saves and revisions.

init

The action that runs early in WordPress's request handling. Used for registering custom post types, taxonomies, shortcodes.

add_action('init', function() {
    register_post_type('case_study', $args);
});

Code that needs to run on every request before content is generated belongs here.

admin_enqueue_scripts

The admin-side equivalent of wp_enqueue_scripts. Adds CSS and JavaScript to admin pages.

Used when custom admin pages need their own assets or when existing admin pages need additions.

pre_get_posts

Modifies queries before they execute. Useful for: changing post per page on specific pages, filtering posts on archives, customizing search behavior.

add_action('pre_get_posts', function($query) {
    if ($query->is_main_query() && $query->is_search()) {
        $query->set('posts_per_page', 20);
    }
});

The hook is powerful but needs care; affecting the main query unintentionally produces unexpected behavior.

wp_nav_menu_items

Filter that modifies menu output. Useful for adding dynamic items to navigation menus.

login_url and home_url

Filters that modify WordPress's various URLs. Useful for redirecting login, customizing site URLs in specific contexts.

The honest framing

Knowing 8-12 useful hooks handles most theme customization needs. The hook system is preferable to template overrides because: hooks survive theme updates; hooks compose with other plugins; hooks are documented in WordPress's developer documentation.

For sites with custom code in functions.php, review whether the customizations use hooks. Code that modifies behavior directly (overrides functions, edits core) is fragile; code that hooks is durable.

The investment in learning hooks pays off across years of WordPress customization work.