If a published WordPress post opens at its own URL but does not appear on the blog page, inspect the archive's configuration and query before assuming publication failed. The homepage, assigned posts page and a page-builder post grid can be three different content lists.
First open the post's public URL while signed out. If that URL is unavailable too, investigate its status, visibility and routing. This guide covers a post that is publicly accessible but missing from the expected listing.
Confirm the record and expected position
Review the publication date, timezone, content type and category. A page is not automatically a blog post. A backdated post may appear several pagination pages earlier, while a sticky post or custom ordering rule can alter the top of the list.
Record a nearby post that does appear and compare their relevant fields. Avoid changing dates just to force a result to the top. That can obscure the actual rule and misrepresent the publishing history.
Identify who owns the listing
In Settings > Reading, review whether the site uses latest posts or a static homepage with a separate posts page. The Reading settings reference explains those assignments. Do not assume that editing content inside the page assigned as the posts page controls its archive output.
If the listing is a builder widget or Query Loop, inspect that element's source and filters. Category, author, post type, manual selection and offset can all explain an omission. Record the intended editorial rule before removing restrictions.
Accessible URL: Separate publication from listing problems. Query excludes it: Inspect categories, types, offset and language. Query includes it: Inspect rendering and pagination. Finished: Correct position; drafts stay private. Original explanatory guide, not a customer test result.
Compare query output with rendered output
On staging, use a harmless test post that clearly matches the intended filters. If the query excludes it, inspect the template or plugin that modifies the query. If the query includes it but no card appears, examine rendering conditions, pagination and frontend errors.
The on-site search guide covers a related but separate listing problem. A post appearing in search does not guarantee that a category-filtered blog grid should include it, and rebuilding a search index will not fix an archive template.
Ask a developer to inspect custom filters in a child theme, custom plugin and must-use plugins. Keep the test fixture constant while isolating one rule at a time. Do not remove every filter from a live site, because some may protect private records or enforce language and membership boundaries.
Check caching after the origin is correct
Compare the logged-out page with current origin output using the host's approved diagnostic method. Logged-in administrators may bypass a cache and see a different list. A stale browser or CDN response can persist even when the database and template are correct.
Purge the specific listing and related pagination entries after confirming the underlying query. Then inspect the normal public URL without relying exclusively on a cache-busting query string. Keep the existing post URL and canonical intact.
Verify the editorial workflow
Confirm the missing post appears in the correct position on desktop and mobile, pagination remains usable, and drafts or private content are not exposed. Recheck a second relevant category if the template serves several archives.
Request blog-listing troubleshooting with the public post URL, listing URL, expected rule and one working comparison. Document which template owns the list so editors know whether the next change belongs in Reading settings, a builder query or custom code.
Sources checked October 1, 2026. Instructions and visuals are explanatory, not claims of customer tests.