In WordPress development, you often need to retrieve the 'slug' of the current page or post. Whether you are building a custom navigation menu, adding dynamic CSS classes to your body tag, or setting up conditional logic for specific marketing scripts, knowing how to fetch the page slug accurately is a fundamental skill. While the title is easy to grab with functions like the_title(), the slug (technically stored as post_name in the database) requires a bit more nuance, especially when you are working outside the standard WordPress Loop.
In this guide, you will learn multiple ways to retrieve the current page slug, ranging from simple global variables to robust API functions and even direct database queries for advanced use cases.
1. Using the Global $post Variable
The most common way to access post data is through the global $post object. This object contains all the data for the current post being processed. To get the slug, you simply access the post_name property.
<?php
global $post;
if ( isset( $post->post_name ) ) {
$post_slug = $post->post_name;
echo $post_slug;
}
?>
When to use this: This method is perfect when you are inside a standard template file like single.php or page.php.
The Caveat: Be careful when using this outside the Loop or on pages with multiple custom queries (like a sidebar with recent posts). If a secondary query runs and doesn't call wp_reset_postdata(), the global $post variable might point to the wrong post.
2. The Reliable Way: get_queried_object()
If you want to ensure you are getting the slug of the primary page being viewed—regardless of any secondary loops happening on the page—get_queried_object() is your best friend. This function returns the object that WordPress is currently querying (the main post or page).
// Get the queried object safely
$current_object = get_queried_object();
if ( is_a( $current_object, 'WP_Post' ) ) {
$slug = $current_object->post_name;
echo $slug;
}
For even higher reliability, some developers prefer accessing the global query directly and sanitizing the result:
// Access the global query object directly
$current_page = sanitize_post( $GLOBALS['wp_the_query']->get_queried_object() );
$slug = $current_page->post_name;
This method is considered 99% reliable because it taps into the core query that generated the page, making it much harder for custom plugins or themes to accidentally overwrite it.
3. Utilizing get_post_field() for Clean Code
WordPress provides a highly underused function called get_post_field(). This is a clean, API-driven way to fetch a specific column from the wp_posts table without manually interacting with objects.
// Fetch only the post_name field for the current post
$slug = get_post_field( 'post_name', get_post() );
By passing get_post() as the second argument, you ensure the function targets the current post context. This is often cleaner to read than accessing object properties directly.
4. Extracting the Slug from the URL
Sometimes, you might need the slug before the global $post object is even fully populated, or you might be working with custom routing. In these cases, you can derive the slug from the URL or the WordPress request object.
Using the Permallink
A quick and dirty way to get the slug is to take the permalink and strip everything but the last part of the path:
<?php echo basename( get_permalink() ); ?>
Using the $wp Global
You can also use the $wp global variable, which holds the current request string.
global $wp;
// Explode the request path and get the last segment
$request_args = explode( '/', $wp->request );
$current_slug = end( $request_args );
This approach is particularly useful if you are working with custom routes or complex URL structures where the standard post object might not behave as expected.
5. Creating a Reusable Helper Function
If you find yourself needing the slug frequently across different template files, it is best practice to wrap this logic into a reusable helper function in your functions.php file. This keeps your templates clean and allows you to apply filters if needed.
if ( ! function_exists( 'get_the_slug' ) ) {
/**
* Returns the page or post slug.
* @param int|WP_Post|null $id Post ID or object. Defaults to global $post.
* @return string
*/
function get_the_slug( $id = null ) {
$post = get_post( $id );
if ( ! empty( $post ) ) {
return $post->post_name;
}
return '';
}
}
if ( ! function_exists( 'the_slug' ) ) {
/**
* Displays the page or post slug.
*/
function the_slug( $id = null ) {
echo apply_filters( 'the_slug', get_the_slug( $id ) );
}
}
With this in your theme, you can simply call the_slug(); anywhere in your templates.
6. Fetching the Slug Early via Direct SQL
In extreme cases—such as when you are hooking into mu_plugins_loaded or very early in the init hook before WordPress has parsed the query—you might need to go straight to the database.
Using the $wpdb global, you can fetch post data before the main loop even starts. Note that this is generally overkill for most themes but can be a lifesaver for plugin developers.
global $wpdb;
$table = $wpdb->posts;
$query = "SELECT post_name FROM $table WHERE ID = %d LIMIT 1";
$slug = $wpdb->get_var( $wpdb->prepare( $query, $current_post_id ) );
7. Handling Slugs Outside the Loop with PHP Primitives
If you are working very early in the WordPress lifecycle (e.g., in a plugin before the post has been identified), you can resort to PHP's parse_url to inspect the request URI.
function get_slug_from_uri() {
$path = parse_url( $_SERVER['REQUEST_URI'] ?? '', PHP_URL_PATH );
return basename( $path );
}
Note: This approach works best for posts at the root level. If your site uses a hierarchical structure (e.g., /parent/child-slug/), basename will only return the child part.
Frequently Asked Questions
What is the difference between a Title and a Slug?
The title is the human-readable name of your post (e.g., "My Awesome Post"), while the slug is the URL-friendly version (e.g., "my-awesome-post"). In the database, the slug is stored in the post_name column.
Why does my slug return an ID instead of a string?
This usually happens if the post is not yet published or if you are viewing a preview. WordPress sometimes uses the post ID as a placeholder until a permanent slug is generated and saved.
Can I use these methods for Custom Post Types?
Yes! All the methods mentioned above—especially get_queried_object() and get_post_field()—work perfectly for Custom Post Types (CPTs) as well as standard Posts and Pages.
Wrapping Up
Retrieving the current page slug in WordPress doesn't have to be complicated. For 90% of use cases, using get_queried_object()->post_name is the most reliable and "WordPress-way" to handle the task. However, knowing alternative methods like get_post_field() or extracting the slug from the URL gives you the flexibility to handle edge cases in complex theme and plugin development.
Always remember to check if your code is running inside or outside the Loop, and use wp_reset_postdata() if you are running custom queries to ensure your global variables stay accurate.
