How to Publish on WordPress: Posts, Pages, and Going Live
Step-by-step guide to publishing in WordPress: the Publish button, draft vs pending vs scheduled, page vs post, and the QA checks to run before going live.
2026-02-13 • 10 min read • 2300 words
How to Publish on WordPress: Posts, Pages, and Going Live
To publish content on WordPress, open the item in the block editor, click the blue Publish button in the top-right corner, and confirm in the pre-publish panel that slides out. That panel is your last checkpoint: it shows the visibility (Public, Private, or Password protected), the publish date (now, or a future date for scheduling), the URL slug, and any tags or categories. Hit Publish again and the page is live. That is the whole mechanical act. The reasons people search "how to publish on WordPress" are usually the surrounding questions: posts versus pages, why the Publish button sometimes disappears, how to schedule for later, and how to make sure the page actually gets indexed by Google afterward.
This guide answers all of those, then extends into the lightweight pre-publish QA that stops the embarrassing post-launch fixes (broken links, missing alt text, mobile overflow) that an extra two minutes would have caught.
The Publish Button: Step by Step
Publishing a single post or page takes five steps in the WordPress block editor, and the only one people get stuck on is the confirmation panel.
- Open the editor. In wp-admin, go to Posts to Add New (for a dated article) or Pages to Add New (for a static page). Add your title and content as blocks.
- Set the URL slug. In the right-hand Settings panel, under the Post or Page tab, edit the slug to be short and keyword-relevant. Do this before publishing; changing it after means setting up a redirect.
- Click Publish. The blue button is top right. On a first publish, WordPress opens a pre-publish checklist panel.
- Confirm the panel settings. Check visibility (Public by default), the date (set a future date here to schedule), categories, tags, and the excerpt. Click the final Publish.
- Verify the live page. Click "View Post" and confirm it renders, then copy the live URL.
Two things confuse first-timers. First, the Publish button can appear greyed out or missing if your user role lacks the publish capability (Contributor accounts cannot publish; their button reads "Submit for Review" instead). Second, if you publish accidentally, you can revert to draft from the same Status panel. The official WordPress.com publishing tutorial covers the hosted-platform flow, which differs slightly from a self-hosted wp-admin install but uses the same Publish-button mechanics.
Posts vs Pages: Which One to Create
WordPress has two main content types, and choosing the wrong one creates structural headaches later. Use a post for dated, chronological content that belongs in a feed; use a page for timeless, standalone content that does not.
| Feature | Post | Page |
|---|---|---|
| Appears in the blog feed / RSS | Yes | No |
| Has a publish date that matters | Yes | Usually no |
| Uses categories and tags | Yes | No (uses parent/child hierarchy) |
| Typical examples | Articles, news, updates | Home, About, Contact, Services |
| Shows in chronological archives | Yes | No |
The practical test: if you would ever say "the latest one" about it, it is a post (the latest article, the latest update). If it is "the one" (the About page, the Contact page), it is a page. Service and landing pages are pages; blog articles are posts. Getting this right matters because posts feed into RSS, archives, and category pages automatically, while pages support a parent-child hierarchy for site structure. Choosing wrong means either an article that never appears in your feed or an About page cluttering your blog archive.
Understanding Draft, Pending, Scheduled, and Published
WordPress post statuses are a built-in lightweight workflow, and knowing the four main ones turns "is this live?" from a guess into a glance at the status label.
Draft is the default for unfinished content: saved, private, invisible to the public. Pending Review marks content finished by the author but awaiting an editor's approval; Contributor-role users land here automatically because they cannot publish. Scheduled means you set a future date in the publish panel, and WordPress publishes it automatically at that time via its cron system (no need to be logged in). Published is live and public. There is also Private (published but visible only to logged-in editors and admins) and Password protected (live but gated behind a password).
To schedule, you simply change the date in the pre-publish panel to a future time; the Publish button changes to read "Schedule." This is how teams spread content across a week instead of dumping everything on Friday afternoon, which helps both crawl scheduling and audience expectations. The status system also doubles as a review queue: filter the Posts list by "Pending Review" and you see exactly what is waiting for sign-off, the foundation of any real WordPress content workflow.
The Pre-Publish QA That Prevents Embarrassing Fixes
The two minutes before you click Publish are the cheapest QA you will ever do, because fixing a live page is always more disruptive than catching the issue in draft. Run this short checklist; it catches the issues that actually matter without becoming a chore.
| Category | Check | Why it matters |
|---|---|---|
| Content | Internal links resolve to live pages, no 404s or staging URLs | A broken link wastes the click and hurts trust |
| Content | No placeholder text left ("Lorem ipsum," "TK," "[quote here]") | Placeholders that ship live are the classic embarrassment |
| Visual | Page renders on mobile (375px), not just desktop | Most traffic is mobile; overflow is the top post-publish bug |
| Visual | Every image has descriptive alt text and is compressed | Alt text aids accessibility and image search; uncompressed images tank LCP |
| SEO | Meta title under ~60 chars, description under ~155 | Truncation in search results kills click-through |
| Technical | Page loads under ~3 seconds | Slow pages lose visitors and rank worse |
The single most-skipped check is mobile rendering, because editors build on desktop and forget to preview narrow. Use the editor's device-preview dropdown (the desktop/tablet/mobile toggle) before publishing, or open the preview link on an actual phone. The SEO-ready theme architecture guide covers structuring templates so many of these checks pass by default, reducing the per-page burden.
After You Publish: Getting Indexed
Clicking Publish makes a page live; it does not make Google aware of it. Run these post-publish steps within fifteen minutes to close the gap between "live" and "findable."
- Visit the live URL and confirm it renders correctly, including any dynamic elements.
- Submit the URL to Google Search Console. Paste the live URL into the URL Inspection tool and click "Request Indexing." This prompts a faster crawl than waiting for Google to find it through your sitemap.
- Confirm it is not accidentally noindexed. If the page does not get indexed within 48 hours, check for a stray noindex directive, a canonical pointing elsewhere, or the page being orphaned with no internal links pointing to it.
- Verify analytics fires. Open your real-time analytics report and load the page to confirm tracking works.
- Add internal links to the new page from related existing pages, so it is discoverable through your site structure and not just the sitemap.
The indexing-confirmation step is the one most teams skip and later regret, because a page that never gets indexed produces zero traffic regardless of how good it is. The internal linking assistant helps plan which existing pages should link to a new one, and the content refresh automation feature flags pages later showing decay (stable impressions but falling clicks) so you know when a published page needs a refresh.
Why the Publish Button Goes Missing: A Diagnostic Map
The most common "how do I publish" frustration is not finding the workflow; it is the Publish button being absent or greyed out. We mapped the documented causes against their fixes, drawn from WordPress core role behavior and editor mechanics rather than guesswork.
| Symptom | Likely cause | Fix |
|---|---|---|
| Button reads "Submit for Review" | User is a Contributor (no publish capability) | An Editor/Admin publishes, or upgrade the role |
| Button greyed out | Required field empty or no changes since last save | Add a title or make an edit |
| No button at all | Editor JavaScript failed to load (plugin conflict) | Disable plugins one by one; check browser console |
| Publishes but not visible | Status is Private or Password protected | Change visibility to Public in the panel |
| Published but not on the blog | Created as a Page, not a Post | Recreate as a Post, or accept it is a standalone page |
The pattern: most "Publish button" problems are a role-capability issue or a status/visibility setting, not a bug. The role case is the most common: a Contributor can create but not publish, so the block editor replaces the Publish button with "Submit for Review," which is expected behavior rather than something broken.
Scaling From One Post to a Publishing Cadence
Publishing one page is mechanical; publishing reliably every week is operational. Three habits turn ad-hoc publishing into a cadence.
Stage before you publish. Once you publish more than a couple of pages a week, build them on a staging environment first (most managed hosts like Kinsta, WP Engine, and Flywheel include one-click staging) so formatting, patterns, and metadata get finalized away from live traffic, then promote with one action. Separate the builder from the QA reviewer. The person who built a page in the editor should not be the person who QAs it, because fresh eyes catch the broken link and mobile overflow the builder stopped seeing. Schedule instead of dumping. Use the Scheduled status to spread publishing across the week rather than all on Friday, which smooths both crawl scheduling and audience expectations.
For teams, these habits formalize into the six-stage pipeline (brief, draft, review, build, QA, publish) covered in the content workflow guide, and the WordPress Publish Workflow feature automates the staging-to-deployment handoff where content most often gets stranded between "approved" and "live." The local business template set is built for batch publishing of multiple location or service pages that share structure but vary in content. For agencies and ecommerce teams, post-publish monitoring matters most, because commercial pages carry direct revenue impact and a page that drops in rank is a pipeline issue, not just a metrics one.
When You Should Not Just Hit Publish
Do not publish straight to production without staging if you are pushing a theme update, a site-wide navigation change, or a batch of pages, because those changes touch every page at once and a mistake is hard to undo live. Skip the immediate-publish instinct, too, for any page with legal, medical, financial, or pricing claims that need a second reviewer; the cost of a wrong number live is far higher than the delay of one review. And if you are on a brand-new site with no traffic yet, do not over-invest in the post-publish indexing dance for every page; Google will crawl a healthy small site through its sitemap, and your time is better spent on the content itself until you have pages worth rushing to index.
FAQ about how to publish on wordpress
How do I publish a post on WordPress?
Open the post in the block editor, add your title and content, then click the blue Publish button in the top-right corner. WordPress shows a pre-publish panel where you confirm visibility, date, categories, and tags. Click Publish again to confirm, then click "View Post" to verify the live page. If your button reads "Submit for Review" instead, your user role is Contributor, which cannot publish; an Editor or Admin completes the publish.
What is the difference between a post and a page in WordPress?
A post is dated, chronological content that appears in your blog feed, RSS, and category archives (articles, news, updates). A page is timeless, standalone content that does not appear in the feed (Home, About, Contact, Services). The quick test: if you would call it "the latest one," make it a post; if it is "the one," make it a page. Posts use categories and tags; pages use a parent-child hierarchy.
Why is the Publish button missing or greyed out?
The most common causes are role capability and post state, not a bug. A Contributor account sees "Submit for Review" instead of Publish. A greyed-out button usually means a required field is empty or nothing has changed since the last save. A completely absent button typically means the block editor's JavaScript failed to load, often a plugin conflict; disable plugins one at a time and check the browser console to find the culprit.
How do I schedule a post to publish later?
In the pre-publish panel (or the Status & visibility section), click the publish date and set a future date and time. The Publish button changes to read "Schedule." WordPress then publishes the post automatically at that time using its built-in cron system, with no need for you to be logged in. This is the standard way to spread publishing across a week instead of releasing everything at once.
Ready to publish WordPress pages without the post-launch scramble? Join wp0 early access and ship content through a workflow built for speed and confidence.