
An older WordPress.com post can sit above newer posts for two common reasons: it has Sticky status, or the block that displays posts uses a different sort order. WordPress.com normally shows blog posts in reverse chronological order, so the newest post appears first. A sticky post stays above that date-based list until you remove its Sticky status. A Query Loop or Latest Posts block can also show posts from oldest to newest, or alphabetically. WordPress.com’s post-order guide documents those display options.
Check those settings before you change the post’s publication date. Each setting solves a different layout choice.
What the normal post order looks like
A standard WordPress.com blog feed puts the newest published post at the top. An older post appearing first does not automatically mean something is broken. The site may be deliberately pinning that post, or the page may use a custom order.
Start by identifying where you see the unexpected order. Is it the main blog page, a homepage section, a category archive, or a custom page? That distinction matters because WordPress.com documents separate controls for a Query Loop block and a Latest Posts block.
If the posts appear in a normal date-based feed, inspect Sticky status first. If they appear inside a block on a page or template, inspect that block’s order setting as well.
Check whether the older post is Sticky
Sticky status pins one public post above the other posts in a blog list. The post can be older than every item beneath it and still remain first. It stays there for as long as the Sticky checkbox remains selected.
Open the older post in the WordPress.com editor. Find the post settings sidebar on the right. If the sidebar is hidden, use the Settings icon in the upper-right area of the editor to show it. Under Status, look for the Sticky checkbox.
A selected checkbox explains why an old post can stay above recently published posts. WordPress.com states that only public posts can use Sticky status. Private posts are not compatible with the feature.
Themes can also style sticky posts differently. A theme may give the pinned item a colored background or another visual treatment. That appearance depends on the theme, so an older post without a visible label can still be sticky.
Sticky status works best for a small number of posts, such as a welcome message, an event update, or a permanent notice. Pinning every post defeats the normal date order and makes the feed harder to scan.
Remove Sticky status when the post should follow its date
If the older post should return to its usual place in the blog feed, open that post’s settings and clear the Sticky checkbox. Save the post afterward.
WordPress.com says that removing the Sticky selection moves the post back into chronological order. Its publication date does not need to change for this to happen.
This is the narrowest fix when the page should keep its usual newest-first layout and only one older post is in the wrong position.
For example, imagine a public post published in January and a newer post published in March. If the January post has Sticky status, it can remain above the March post. Clearing Sticky returns the January post to the position set by its date and time. This is a fictional example; it describes the documented behavior of Sticky status.
Check the Query Loop block’s order
An older post may appear first because the template uses a Query Loop block with a custom order. In a block theme, WordPress.com says posts commonly display newest first through this block. The block’s settings can reverse that order or sort titles alphabetically.
To inspect it, go to the site dashboard, then open Appearance and Editor. Select Templates in the left sidebar. Open the template that displays the posts, often the homepage or Index template. Use List View to select the Query Loop block.
Look for the ORDER BY control in the block settings on the right. If it does not appear, WordPress.com instructs you to set Query Type to Custom. The available documented choices include:
| ORDER BY setting | What visitors see |
|---|---|
| Oldest to newest | Older published posts appear before newer ones |
| A → Z | Posts appear in alphabetical title order |
| Z → A | Posts appear in reverse alphabetical title order |
Choose the setting that matches the page’s purpose, then save the template. “Oldest to newest” can make an older post appear above a newer one across the whole block. Alphabetical choices can do the same when an older title sorts earlier or later than another title.
This setting changes the block’s display order. It does not pin one individual post above every other post. That difference matters when you decide what visitors should see.
Check the Latest Posts block on a page
Some WordPress.com sites use a Latest Posts block rather than a Query Loop block. The same three documented order choices apply: oldest to newest, A → Z, and Z → A.
Open the page that displays the posts from the dashboard. Use List View in the page editor to select the Latest Posts block. Find the ORDER BY setting in the block sidebar, choose the desired sort order, and save the page.
An older post listed first in this block may reflect the block’s configuration rather than the post’s Sticky status. Review both places if the layout includes a custom page and a standard blog feed. One view can use a different display rule from another.
A simple test helps separate the two causes. If the same older post stays first wherever posts appear, inspect Sticky status. If posts change order only in one homepage section or template, inspect that section’s Query Loop or Latest Posts block.
Check the publication date before editing it
WordPress.com also lets you reorder individual posts by changing their publication date and time. This is a different action from pinning a post or changing a block’s order.
Open the post, locate Publish in the right-hand post settings, click the displayed date to open the calendar, choose a new date or time, and save. WordPress.com explains that changing a published post’s date or time can move it above or below another post.
Date changes are useful when the publication date itself is wrong or when you deliberately want to swap the position of specific posts in a date-based feed. They are a poor first response to an accidental Sticky setting. A pinned post can return to date order simply by clearing Sticky status.
Keep the date change separate from display settings. Changing a post date alters that post’s chronological position. Changing a Query Loop or Latest Posts setting changes how the selected block sorts the posts it shows. Sticky status pins a public post above the rest of the list.
A fictional example makes the difference clearer. Suppose one post was published at 3 p.m. and another at 4 p.m. on the same day. In newest-first order, the 4 p.m. post appears higher. Editing its time to 2 p.m. moves it below the 3 p.m. post in that date-based order. That does not turn either post into a sticky post, and it does not alter a block configured for alphabetical sorting.
Match the setting to the layout you want
Use Sticky status for a public post that should remain at the top until you decide otherwise. Use a Query Loop or Latest Posts order setting when the whole list should run oldest first or alphabetically. Edit a publication date only when the date or time needs correction, or when you deliberately want to reposition an individual post within chronological order.
Check the relevant view after saving. A homepage template, a custom page, and the blog feed can use different display methods. The right setting is the one that produces the intended order in the exact place where visitors see the posts.
If an older post remains above newer posts after you clear Sticky status, does the page use a Query Loop block or a Latest Posts block? If it does, which ORDER BY choice is selected? If neither setting explains the order, is the post’s publication date and time correct?