WordPress sticky posts are most useful when you treat them as a small, maintained editorial priority rather than a permanent badge. A sticky standard post is placed at the top of the front page of posts; it is not automatically promoted in every archive, static page, or custom query. You can make the feature more useful by curating which posts qualify, setting the correct behavior in each Query Loop, designing a clear repeated layout, and using a scoped theme query or style when the block controls are not enough.
The methods below use documented WordPress editor and theme APIs. They are configuration and editorial recommendations, not promises of higher traffic, clicks, or engagement.
What a WordPress sticky post actually does
WordPress defines the feature plainly: “A Sticky Post is the post will be placed at the top of the front page of posts.” See the Theme Handbook explanation of sticky posts. The built-in behavior applies to the standard post post type, not custom post types.
That scope matters. A sticky flag does not guarantee that a post moves above other content in every category archive, search result, static front page, REST-powered display, or custom WP_Query. A Query Loop, theme template, or plugin can choose a different ordering. Always verify the actual page where readers will see the loop.
Sticky status is metadata attached to a post. It does not rewrite the post, alter its publication date, or create a separate copy. Removing the status returns the post to the normal ordering used by the relevant query.
How do I make a post sticky in WordPress?
Block editor
- Open Posts > All Posts and edit the standard post you want to prioritize.
- In the post settings sidebar, open the Status or Post panel. WordPress releases and themes can present the label slightly differently.
- Enable the option labeled Stick to the top of the blog (or the equivalent sticky setting).
- Update or publish the post, then open the posts front page in a logged-out browser window and confirm its position.
Classic Editor
- Open the post in the classic editor.
- In the Publish box, locate Visibility and choose Edit.
- Select Stick this post to the front page, then save the visibility change and update the post.
- Check the front page of posts rather than assuming that every archive will reorder it. The official Sticky Posts documentation describes this classic-editor workflow.
You can reverse the process at any time by clearing the same setting. Use the standard post type; a custom post type needs its own query and display logic.
As an Amazon Associate I earn from qualifying purchases.
Way 1: Choose sticky posts deliberately and review them
Sticky space is a scarce editorial signal. Reserve it for a post that deserves priority for a clear reason, such as a durable introduction for new readers, a current service announcement, or a carefully maintained reference guide. The feature itself does not establish an ideal number of sticky posts or a guaranteed performance benefit, so set a limit that your design can explain and maintain.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesUse a qualification test
- Audience value: A first-time visitor can understand why the post matters without knowing your internal publishing history.
- Time sensitivity: If the post is an announcement, its date and expiration are obvious.
- Maintenance owner: Someone knows when links, screenshots, prices, regulations, or instructions must be checked.
- Destination fit: The post makes sense on the posts front page where sticky behavior is defined, not only in a private campaign or category.
- Distinct purpose: It adds a useful priority instead of duplicating another pinned item.
Schedule a review, not a permanent pin
Set a recurring editorial review—monthly, quarterly, or around the end of each announcement—based on how quickly your content changes. At review time, open Posts > All Posts, inspect the current sticky items, remove stale status, and replace it only when another post has a stronger current claim. Record an owner and a review date in your editorial calendar so a temporary announcement does not remain indefinitely.
Do not confuse “sticky” with “evergreen.” An evergreen guide may remain useful for years but still need updates; a short-lived notice may be the right choice for one week. The status controls placement, while your editorial process controls accuracy.
Way 2: Set the right behavior in each Query Loop
The Query Loop block is “an advanced block that allows you to display posts based on specified parameters, like a PHP loop without the code,” according to the WordPress.org Query Loop documentation. Its sticky setting is a per-loop decision. A loop on a landing page can make a different choice from the loop in a theme template.
Configure a custom Query Loop
- Insert a Query Loop block, or select the existing loop you want to change.
- In the block toolbar or settings, choose the loop’s query controls. Select Custom query when you need explicit sticky handling; the Default query type relies on the template.
- Set the post type, order, display count, and any taxonomy or other filters required for that page.
- Open the Sticky posts control and choose the outcome that matches the page’s purpose.
- Preview the published URL at desktop and mobile widths. Confirm the result with more than one sticky post, with no sticky posts, and on a later page of results if pagination is enabled.
WordPress documents four choices. Their meaning is about the result set, not a universal promise that every theme will visually move an item.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Setting | Result for the loop | Use it when |
|---|---|---|
| Include | Sticky posts are included in the result and can receive the loop’s sticky treatment. | The page should show priority posts along with regular posts. |
| Exclude | Sticky posts are removed from this result set. | You have already displayed a featured or pinned area and want the regular feed to avoid duplicates. |
| Ignore | The query does not give sticky status special treatment. | The loop should follow its ordinary ordering and filters without sticky-based handling. |
| Only | The result set contains sticky posts. | You are building a dedicated announcements, “start here,” or featured-resources list. |
Available controls can vary with the theme, WordPress version, and your permissions. If a setting is missing, check whether the loop is using a custom query and whether the active theme exposes that control.
#1 Best Overall
How do I show only sticky posts in a Query Loop?
Select the Query Loop, switch its query type to Custom, and set Sticky posts to Only. Keep the post type as the standard post unless you have another documented implementation. Then check the loop’s other filters: a category, author, date range, or low display count can make the result appear empty even when sticky posts exist. Publish or preview the page and test a case with at least one known sticky post.
How do I exclude sticky posts from a WordPress query?
For a block-based loop, choose Exclude in the same custom-query control. This is useful when a top “featured” loop and a lower chronological feed appear on one page; the lower feed will not repeat the pinned items. If the page is powered by PHP instead of a Query Loop, use the theme-level method in Way 4 and test pagination, filters, and empty results.
Way 3: Make the repeated post layout explain the feature
A sticky flag changes which posts qualify for a loop; it does not explain why a reader should open one. The Query Loop’s repeated Post Template controls the information shown for every item. The documentation lists elements such as Title, Excerpt, Date, Featured Image, Read More, Author, Categories, and Tags, and supports list or grid presentation.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Build a readable information hierarchy
- Lead with the title. Use a descriptive, specific title that can stand alone when the card is viewed without surrounding copy.
- Add a short excerpt. Write or edit an excerpt that states the post’s purpose, audience, and time sensitivity rather than repeating the first sentence.
- Show context. Include the date for announcements or changing guidance. Include author, category, or tags when that information helps a reader judge relevance.
- Use a purposeful image. Add a featured image only when it conveys subject or status; provide meaningful alternative text and avoid decorative repetition.
- Make the action explicit. A consistent Read More link or an accessible linked title gives keyboard and screen-reader users a clear destination.
Choose list or grid intentionally
A list gives each sticky item more room for an excerpt and supporting metadata. It is often easier to scan when the posts have different lengths or urgency. A grid can show several comparable cards compactly, but keep titles, image ratios, and action placement consistent so the visual hierarchy does not hide the date or qualification.
Do not label every card “Featured” if the entire loop is already an only-sticky collection. In a mixed loop, a visible label, category, or short introductory sentence can clarify why one item is prioritized. These are communication choices, not guarantees of a particular engagement outcome.
Check the edge cases
- Preview a sticky post with no featured image and another with a very long title.
- Check an excerpt containing a link, quotation, or unusual punctuation.
- Verify that dates, labels, and Read More links remain understandable when CSS is disabled or text is enlarged.
- Confirm that the mobile layout does not place a large image above the title and push the reason for priority below the fold.
Way 4: Use a theme query or scoped styling for custom behavior
Classic themes and custom templates can work with the sticky ID list directly. WordPress documents get_option( 'sticky_posts' ) for retrieving selected sticky post IDs and WP_Query for querying them. The WP_Query API reference documents the query arguments used by these patterns.
Select and limit sticky posts in PHP
This example retrieves the IDs, preserves the order you choose, limits the list, and asks WP_Query for those standard posts:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
<?php
$sticky_ids = get_option( 'sticky_posts', array() );
$sticky_ids = array_slice( (array) $sticky_ids, 0, 3 );
$featured_query = new WP_Query( array(
'post_type' => 'post',
'post__in' => $sticky_ids,
'orderby' => 'post__in',
'posts_per_page' => 3,
) );
?>An empty ID list should be handled before rendering a heading or wrapper for the section. If you sort the IDs by date, menu order, or another editorial rule, make that choice explicit rather than assuming the option’s stored order is meaningful. Apply your normal escaping, pagination, and loop-reset practices around the query.
Exclude sticky IDs from another query
To keep a regular feed from repeating the items already shown, pass the sticky IDs to post__not_in:
<?php
$sticky_ids = (array) get_option( 'sticky_posts', array() );
$regular_query = new WP_Query( array(
'post_type' => 'post',
'post__not_in' => $sticky_ids,
'posts_per_page' => 10,
'paged' => max( 1, get_query_var( 'paged' ) ),
) );
?>Exclusion interacts with pagination: removing several posts can change how many results remain on a page and may leave a later page short. Test the first and last pages, category filters, search, and the no-results state on the real site. A plugin or another filter can also modify the final query after your arguments are applied.
Style the documented sticky class carefully
The theme handbook notes that post_class() adds a sticky class in the first-page posts-home context—when is_home() is true and is_paged() is false. It is not a universal class on every sticky post in every loop. Scope your CSS to the markup and context you control:
.posts-home > .sticky {
border-inline-start: 0.25rem solid currentColor;
padding-inline-start: 1rem;
}
If you need a visual treatment in a custom Query Loop, add your own class or block style to that specific section instead of assuming the handbook’s class will be present. Inspect the rendered HTML, test a paginated URL, and confirm that the style does not accidentally mark ordinary posts as featured.
Verification and troubleshooting checklist
- The post does not appear at the top: Confirm it is a standard
post, is actually marked sticky, and that you are viewing the posts front page rather than a category, static page, or custom query. - A Query Loop shows the wrong items: Inspect whether it uses Default or Custom query, then review post type, taxonomy, author, date, order, count, and Sticky posts settings together.
- “Only” returns nothing: Check that at least one eligible sticky post exists and that another filter is not excluding it.
- Cards repeat the featured posts: Set the lower loop to Exclude, or pass the sticky IDs through
post__not_inin PHP. - The sticky style is missing: Inspect the context. The documented
stickyclass is limited to the first posts-home page, so a custom loop may need its own class. - Editors cannot see a control: Check permissions, the active theme, and the WordPress version; documented options can differ by environment.
A practical decision framework
Use the built-in status alone when one maintained post should lead the standard posts front page. Use a custom Query Loop when different sections need different treatment—such as an Only-sticky announcement strip above an Exclude-sticky chronological feed. Use PHP when a classic theme or bespoke template must control IDs, limits, ordering, or exclusion beyond the block settings. Add styling only after confirming the rendered context, because the built-in class is narrower than the word “sticky” suggests.
Whichever method you choose, keep the editorial owner, the intended audience, and the destination page explicit. WordPress supplies the placement and query controls; your selection, layout, and maintenance rules determine whether that priority remains useful.
Quick Recap
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
