How to Publish a Blog Post: CMS Workflow and SEO Checklist

Key takeaways

Move an approved draft into the correct CMS destination before publishing.
Check the URL, author, language, cover, and public links.
Verify the live page; a CMS success message is only part of the release.
Use DEX to connect content review, CMS publishing, and later page checks.

To publish a blog post, add the approved article to your CMS, check its URL and page settings, preview it, and publish or schedule it. Then open the public page and test it. A saved draft, a preview, and a live page are three different things.

This guide takes you from a reviewed draft to a working page on your own site. It covers the steps that matter across CMSs, with WordPress as a practical example. It also explains what to check when a connected CMS says “published” but your website still shows no article.

DEX connects content work with publishing. The aim is to spend less time moving text between tools while keeping control over what reaches your readers.

What Do You Need Before Publishing a Blog Post?

Start with an approved version of the article. Decide which file or draft is the final one. Publishing from an old copy can put errors back into a text that someone already checked.

Have these items ready:

The final title, article, and short page description.
The correct author and someone who can approve release.
A cover image you own or have permission to use.
The intended URL, language, and topic group.
The sources and internal pages that the article needs.
One useful next step for the reader.

If the draft still needs sources, examples, or a clear answer, finish that work first. Our guide to writing articles with AI covers the move from brief to reviewed draft. The SEO content audit guide helps you assess an article before release.

Choose an owner for the last check

A writer may approve the copy while an editor handles the CMS. Agree who checks the live page. Otherwise, each person may assume someone else confirmed the image, links, and public URL.

Keep a small release note: article name, version, owner, target site, and planned date. It does not need to be a new tool. A row in your existing content plan can be enough.

How to Prepare Your Post in a CMS

A CMS is the system that stores and manages your website content. The editor holds the post. Your website template decides how much of that content readers see and how it looks.

Create a post in the correct site or content area. Paste the title into the title field and the article into the body. Check the structure after pasting. Text from a document or AI tool can bring extra spacing, stray styles, or broken lists. The Google Docs to WordPress guide shows how to clean up a pasted draft.

Keep the structure clear

Use headings for sections, rather than bold text that only looks like a heading. A subsection should sit beneath the section it explains. Check how the template displays the title before adding another main heading inside the body.

Use a numbered list for steps in order. Use bullets for a set of items. Add a table when the reader needs to compare things. Read the result at a narrow width; a table that looks fine in the editor may be hard to use on a phone.

Do not turn a short paragraph into several blocks just to make the page longer. Each section should help the reader make a decision or finish a step.

Check what the template adds

Your site may add an author box, table of contents, cover, summary, or related links. Look for repeats. An image set as both the cover and the first body image may appear twice. A manually typed contents list can repeat an automatic one.

Fix these issues in the right place. If every article has the same display fault, the template may need a change. Editing one post will not solve a shared layout problem.

How to Set the URL, Author, Category, and Language

These fields give the post a home. Check them before release, when a change is easiest to manage.

Choose a clear, stable URL

The slug is the readable part of the post address. For example, a guide about publishing might use how-to-publish-a-blog-post. Choose words that describe the page. Avoid adding a date unless the date is central to the subject.

Look at the whole URL, not just the slug field. Your site may add a blog folder, category, or language prefix. Check that the result is the address readers should share.

Keep an established URL when you update a live article unless there is a clear reason to change it. If a move is needed, plan the redirect and update links that point to the old address.

Set the author and topic group

Select the person or team responsible for the content. Do not leave an unrelated account as the author simply because that account created the draft.

Choose an existing category when it fits. A category should help readers browse a useful group of articles. Avoid making a new category for each post. Tags can add another way to find related subjects, but they should also have a purpose.

For a broader plan, see our guide to topic clusters. The publishing step should follow that plan rather than create a new topic structure by accident.

Confirm the language and destination

A translated article needs the right language setup as well as translated text. Check its category, public path, linked pages, and language switcher where your site uses one.

CMSs handle languages in different ways. Your site may use separate posts, localized items, or another setup. Follow your site’s model. Do not assume a field that links translations also sets the page language.

How to Add Images and Check Your Links

Set the cover image and preview the actual crop. Keep the main subject and any useful text away from the edges. Blog cards, article headers, and social previews can use different shapes. If the post includes a video, the video embed guide covers how to add it and check playback.

Use alt text to explain the purpose of an informative image in context. A chart needs a useful description of what it shows. A decorative shape does not need a list of keywords. Also check captions, image credit, and rights where they apply.

Open every important link. An internal link should reach a public page on your site. It should not send readers to an admin screen, private preview, or CMS-only address.

For a translated post, prefer a relevant page in the same language when one exists. Make the link text explain what readers will find. “See our publishing checklist” gives more context than a string of “click here” links.

Check the next-step link as well. A useful article can lose a ready buyer if its trial, plan, or contact link leads to the wrong place.

What Changes Between WordPress, Shopify, Webflow, Wix, and Framer?

The goal stays the same: publish the right content at the right public address. The content model and release controls vary. DEX lists connectors for these five platforms. A connector does not mean every platform has identical fields or permissions.

CMS	Where the article lives	What to check
WordPress	A post, with fields shaped by the theme and plugins.	Post status, public visibility, slug, author, category, and cover.
Shopify	A post within a blog.	The target blog and whether to publish now or schedule the post.
Webflow	A CMS Collection item.	Whether the item is published now, scheduled, or queued for a later site publish.
Wix	A Wix Blog post.	The post’s content, cover, categories, SEO settings, and release settings.
Framer	A CMS item displayed through a page template.	The item fields and how the shared template displays them on the website.

These differences are described in the official guides for WordPress post settings, Shopify blog posts, Webflow item publishing, Wix Blog, and Framer page types.

When you connect a CMS, agree on the destination and fields before the first release. Which blog or Collection receives the article? Which field supplies the cover? Who can publish? Where does the live page appear?

Do not solve a field mapping problem by copying the article into several places. That can create duplicate drafts and make it hard to know which version is live.

How to Preview, Publish, or Schedule Your Post

Save the draft, then open the preview. Read it as a visitor would. Check the top of the page, section breaks, images, links, and final call to action. Preview on a phone as well as a large screen.

The preview may require your login. It shows how a draft looks; it does not prove the public page is available.

A practical WordPress example

In the block editor, open the post settings and check the status, date, URL, author, and categories. The available controls depend on your setup and permissions. Confirm the featured image and read the preview before you release the post.

Choose public visibility for an article meant for all visitors. If you schedule it, check the site’s time zone and the chosen date. If you publish now, finish any final confirmation and wait for the success message.

A pending review status means someone still needs to approve the post. The WordPress user roles guide explains who can publish and who must submit for review. A private or password-protected page serves a different purpose from a public blog article.

Keep a record of the release

Note the final public URL and who approved it. For scheduled content, check again after the release time. If the post did not go live, the missed schedule guide explains how to recover it. An entry in a calendar is a plan; the live page is the evidence that the release worked.

Your editorial plan can hold that record alongside the brief, owner, and next review date.

Which SEO Checks Should You Run on the Live Page?

Open the public URL outside the editor. For content meant for everyone, also test access while signed out. Confirm the page loads and shows the approved version.

Check the visible page and search settings

The title and main heading describe the article.
The page description fits the content and gives a clear reason to read.
The image loads, has a useful crop, and does not hide key details.
The article is readable on a phone and has no broken tables or stray text.
Links reach the intended public pages.
The blog index and relevant topic page include the post.
The intended search settings do not block indexing by mistake.
The canonical, where used, points to the intended preferred URL.

Check what the live site outputs. A field in the editor can be correct while a template displays a fallback value. Google also uses several sources for its result titles, so the text it shows can differ from your chosen title. See Google’s title link guidance.

Separate publication, indexing, and ranking

A public page can exist before Google discovers it. An indexed page can exist without ranking well for the query you want. These are separate stages.

Use Search Console to inspect the URL when you need evidence about Google’s view of it. Google’s guide to getting a site on Google explains common discovery and access issues. Publishing a post or submitting a URL does not guarantee a search position.

DEX Health can help you review page issues after release. Treat its findings as checks to investigate. A content edit can fix unclear copy; a shared template fault may need work on the website itself.

Why Is a Published Post Missing From Your Website?

First define what “missing” means. Does the direct URL fail? Does the page load but stay out of the blog list? Or does the page work on your site but not appear in Google?

Each case needs a different check. Use this order to avoid changing a sound article while the real issue sits elsewhere.

What you see	What to inspect next
The post is visible only in the editor.	Draft, review, scheduled date, and public visibility.
The CMS page works but the main site URL fails.	Content destination, connector status, route mapping, and the site’s release process.
The direct page works but the blog list omits it.	Category, language, list filters, and whether the site needs a refresh or rebuild.
The site shows an older version.	Whether the changes were published and whether a cache or build still serves the old copy.
The public page works but Google does not show it.	Indexing evidence in Search Console, rather than the CMS publish button.

Some sites use a CMS for storage and a separate system to build public pages. In that setup, a CMS success message is one step in a longer process. Check the site’s actual release behavior before you assume a fixed delay.

An example of a useful release check

Imagine a small store that publishes a guide in its CMS. The editor shows “published.” The direct public page loads, but the blog list has no card for it.

The next useful check is the list’s category or language filter. Rewriting the introduction will not make a filtered card appear. Once the list includes the post, the editor records the public URL and checks the links. This is a hypothetical example, not a reported customer result.

How DEX Publishes Through Your Connected CMS

DEX brings research, content production, review, and publishing into one workflow. Its public site lists WordPress, Shopify, Webflow, Wix, and Framer as supported connections. It also describes reviewing content before release or using an automatic mode.

Set the destination and approval approach to match your team. Keep an owner for facts, brand claims, and the final page. Review of facts and competing pages should help the article answer the search need before it reaches the CMS.

The handoff should make the outcome clear: this approved article, in this language, goes to this content area on this site. The same check applies whether a person clicks the publish button or a connected workflow handles the transfer.

Confirm the public result after release. A connector reduces manual steps; it does not make a wrong category, missing image, or blocked page harmless.

DEX also revisits pages that have not ranked after 30–60 days, as part of its follow-up workflow. That is a review window, not a promise of results within that period. Use the content audit guide to understand how later checks lead to a useful next action.

Blog Post Publishing Checklist

Use this short checklist for each release:

Approve: confirm the final copy, facts, sources, image rights, and owner.
Place: choose the right site, blog or Collection, category, and language.
Prepare: set the title, URL, author, cover, description, and links.
Preview: check the actual template on a large screen and a phone.
Release: publish now or set a checked date and time.
Verify: open the public URL and confirm the article appears where readers expect it.
Record: save the final URL and plan a review based on page evidence.

Ready to connect the work from draft to live page? Explore DEX plans and choose a publishing workflow that fits your site and review process.

FAQ

How do I publish a blog post?

Add the approved post to your CMS, set its URL and page details, preview it, and publish or schedule it. Then check the public page.

Does publishing a blog post put it on Google straight away?

No. Publication, discovery, indexing, and ranking are separate stages. Use Search Console to inspect the public URL.

Why is my published post missing from the blog?

Check its status, public visibility, target blog or Collection, language, category, and the website release process.

Does DEX only connect to WordPress?

DEX lists connectors for WordPress, Shopify, Webflow, Wix, and Framer. Confirm the destination and supported fields for your setup.

Sources

Post settings · WordPress
Writing blog posts · Shopify
Save and publish Collection items · Webflow
Wix Blog composer · Wix
Using pages · Framer
Get your website on Google · Google
Title links · Google
DEX workflow and connectors · DEX

Dex SEO

Dex SEO is an AI SEO agent for small businesses. Every article here is planned from search data, drafted by Dex, fact-checked against the sources it cites, and reviewed by the team before it is published.

How this article was made: planned and drafted by Dex from search data, fact-checked by Dex (8 claims checked), then approved by the Dex SEO team.