If your articles are already WordPress drafts, you can use the Posts list to publish approved posts together. If they are still in documents, first create WordPress drafts, check each saved post, and release only the ones that pass review.
Moving five articles into WordPress and publishing five articles are separate actions. A useful batch may include posts you deliberately hold back. The illustrative example below follows five articles through review and releases three while two remain drafts.
Choose the route that fits your starting point
| Where the articles are now | Route | What to do before release |
|---|---|---|
| Existing WordPress drafts | Review the saved posts, then use WordPress bulk editing for the approved drafts. | Identify the exact posts and exclude unfinished ones. |
| Finished documents or files | Create WordPress drafts from the source articles, then review and release them. | Match each source to a saved draft and verify its content and settings. |
| Migration files from another site | Use an appropriate import route for the migration file. | Check what the import created before deciding which posts to release. |
This guide focuses on the first two routes, not the mechanics of site migration. It covers publishing articles on your WordPress site, not sharing already published posts to social networks.
For document-based work, Tenwrite supports Google Docs, Word documents, and local Markdown or text files. A local batch can include supported files in different formats, such as DOCX and Markdown; a Word file does not need to become a Google Doc first. See the Tenwrite features overview and current plans to assess the service for your work.
Set the release decision before touching the batch
Choose whether the articles should appear together, at different times, or not yet. This prevents a convenient bulk action from becoming the reason for an unintended publication.
- Publish together when every selected post is approved and can go live now. Use the bulk edit procedure below after reviewing each draft.
- Schedule separately when articles need different release dates or times. Assign and verify the intended time for each post; do not assume that the order in which documents were imported creates a release schedule.
- Keep reviewing when approval, an asset, or a publishing detail is still missing. A draft can wait even if other posts in the same batch are ready.
For individually scheduled posts, check the saved date, time, and status on each post, including the site’s time zone. When the intended time arrives, verify the public result. If a specific launch depends on coordination with other work, publishing one post at a time may make the final checks easier.
Build a five-post release ledger
A simple ledger makes the final selection less dependent on memory. Before importing or editing anything, list the approved source for each article and the intended site. Then add the WordPress post ID or edit link once you have found the saved draft. An ID or edit link distinguishes two similarly named posts; a title alone may not.
The following batch is illustrative, not a recorded Tenwrite test. All five articles are intended for the same example site. The public paths are placeholders, not real URLs. The table shows the ledger after review and release so you can see the whole decision from source to result.
| Source reference | Intended site and saved post | Review result | Release decision | Final status / public URL |
|---|---|---|---|---|
garden-basics.docx | Example site; post 101 | Pass | Publish | Published; https://example.com/garden-basics/ |
watering-guide.md | Example site; post 102 | Pass | Publish | Published; https://example.com/watering-guide/ |
soil-guide.docx | Example site; post 103 | Pass | Publish | Published; https://example.com/soil-guide/ |
planting-guide.md | Example site; post 104 | Intended inline image missing | Hold | Draft; no public URL recorded |
seed-guide.docx | Example site; post 105 | A subsection is incorrectly marked as a top-level section | Hold | Draft; no public URL recorded |
Before release, the final-status cells for the first three would say pending, not published. Fill them in only after checking the saved and public results. The two held rows stay in the ledger so they do not disappear from the job just because they were excluded from the immediate release.
The missing-image post becomes eligible after the intended image is added, its placement and alternative text are checked, and the rest of the post passes review. The heading-error post becomes eligible after its heading level is corrected against the source and the resulting structure is checked again. Neither correction automatically approves the post: record a new release decision after review.
If your articles already exist in WordPress, use their edit links as the saved-post references and compare each one with its approved source or editorial instructions. You can skip the transfer step, but not the review or the final status check.
Create drafts from documents, then find each saved post
For articles outside WordPress, prepare a small, identifiable set of finished sources. Record the file name or document link and the destination site for each one. Resolve source-level questions first: for example, decide which image belongs in the article and whether the text is the version the editor intends to publish.
Then use a document-to-WordPress route that can save the articles as drafts:
- Confirm the destination. Check that the connected or selected site is the site named in your ledger. This is especially important if you manage more than one WordPress site.
- Select the intended sources. Match each document or file to its ledger row. Keep unfinished articles out of the selection, even if they are in the same folder.
- Request draft status. Use the draft-first option available in your chosen workflow. A requested status is an instruction, not proof of what was saved.
- Find the results in WordPress. Open the destination site’s Posts list and locate each resulting post. Record its ID or edit link and its actual saved status against the corresponding source.
- Investigate gaps before continuing. If one source has no identifiable saved post, leave that row unresolved. Check for an existing post before attempting another transfer.
A local upload represents the file supplied at that moment. Editing the file later does not by itself change the saved WordPress post. Linked Google Docs can be useful when writers continue working in Docs and need a source relationship for later updates, but the saved WordPress result still needs its own review.
For format-specific guidance, see the Markdown to WordPress guide or the Word to WordPress walkthrough. Then return to the same per-post approval process regardless of format.
Check every saved post before approving it
Open each saved draft and compare it with its source and the intended publishing details. A draft can pass only when the required parts are correct; a successful transfer message does not establish that the entire article arrived intact.
| Check | Pass | Fix or hold when |
|---|---|---|
| Site, title, and post type | The edit screen belongs to the intended site, the title matches the approved article, and it is saved as the intended type of post. | The post is on the wrong site, has the wrong title, or was saved as a different content type. Locate the right destination before proceeding. |
| Complete body | Compare the beginning, ending, and sections in between with the source. Required lists, tables, and other material are present and readable. | Text is missing, duplicated, or altered in a way that changes meaning. Repair it and compare again. |
| Headings | Section and subsection levels reflect the source’s structure. A subsection belongs under the section it explains. | A heading is missing, ordinary text was turned into a heading, or a subsection has the wrong level. Correct the structure and preview it. |
| Links | Open or inspect each intended link and compare its destination with the source. Check that the linked words are the intended ones. | A link is missing, points somewhere unexpected, or does not work. Replace or investigate it before approval. |
| Images | Intended inline images appear in the right places. Check captions and alternative text where appropriate, and verify the featured image if the post needs one. | An image is missing, incorrect, or assigned in the wrong role. Add or correct it and preview the post. |
| Publishing fields | Category, author, slug, visibility, and any other required fields match the release instructions. | A field is wrong or unresolved. Correct it, or hold the post until the decision is made. |
| Saved status and approval | The post remains a draft and an authorized reviewer has approved this specific version for the intended release. | The status is unexpected, the source is still changing, or approval is missing. Stop and resolve the discrepancy. |
For the illustrative batch, posts 101–103 pass these checks. Post 104 fails because its intended image is absent; even a complete-looking text body is not the approved article if an essential asset is missing. Post 105 fails because the heading hierarchy misrepresents the relationship between sections. Both stay drafts.
Preview each draft as well as inspecting the editor. A preview helps reveal problems such as an image in the wrong place or a table that is hard to read. If the preview differs from the source, correct the saved draft and preview it again. Review the entire post, not just the section you changed: a repaired heading does not prove that its links and images are also correct.
Record pass, fix, or hold in the ledger. Use fix for a known correction still to make; use hold when the post must not join the release, including when a decision or asset is outstanding. Only an explicit approval after the checks should move a row into the release selection.
Bulk publish only the approved WordPress drafts
Once the saved posts are reviewed, the WordPress Posts list is the release point for drafts that should go live now. In the example, select posts 101, 102, and 103. Do not select 104 or 105.
- Sign in to the intended WordPress site and open Posts. Find the drafts listed as approved in your ledger.
- Check the box beside each approved post. Use the titles and, where needed, the post edit links or IDs to distinguish them from similar drafts.
- Before applying a change, compare the selected titles and count with the ledger. The example should have three selected posts, not five.
- Under Bulk actions, choose Edit and apply it. In the bulk-edit controls, set the status to Published, then select Update to save the change.
- Return to the list and check the saved status of each selected post. Keep the held drafts out of subsequent selections until they have been corrected and approved.
The list may show only one page of results. Do not assume a select-all box includes every matching post across other pages. If the approved posts span pages, work through the visible selections deliberately, checking the count and titles before each change. The goal is the approved set, not every draft that happens to be visible.
If the controls or permissions available on your site differ, do not guess at an equivalent action. Resolve the access or workflow issue first, and verify the selected posts before changing their status. For another description of the dashboard route, see HostAfrica’s guide to publishing multiple WordPress posts.
Confirm public results and reconcile the ledger
An action message is a reason to check the results, not a substitute for checking them. For the example, the expected outcome is three published posts and two drafts.
Start in WordPress: open or locate each of the three selected posts and confirm its saved status. Record the actual public URL for each one in the ledger. Then check posts 104 and 105 separately: both should still show draft status. If a selected post is still a draft or a held post is unexpectedly public, the observed result does not match the plan, even if the batch action reported completion.
Next, open each released URL while logged out, or in a browser session that is not signed in. Confirm that the page is publicly accessible and that it is the intended article. Read the title and scan the headings, links, and images; open links that matter to the article’s use. A post can have a published status but still need a correction to its public presentation.
Compare the results row by row:
- Expected: 101, 102, and 103 published; 104 and 105 held as drafts.
- Observed: record each actual saved status and public URL. Mark the release complete only if all five rows match the expected outcome.
- Difference: note the affected post and symptom. Leave the other rows alone while you investigate.
The example ledger above shows the completed, matching outcome. In a real batch, replace the placeholder URLs with the URLs you actually verified. If a public page does not load, check the saved status and URL first; avoid assuming that rerunning the batch will correct it.
Fix partial failures without repeating successful work
Stop and identify the affected rows before taking another action. Repeating the whole import or publication request can create more uncertainty: a post that succeeded may be processed again while the underlying problem remains.
| Symptom | Controlled next action |
|---|---|
| A source has no matching saved post | Search the intended site’s Posts list and inspect possible matches by title and content. Confirm whether a draft already exists before retrying that source. If it exists, record its ID or edit link; if not, investigate the transfer and retry only the missing item when appropriate. |
| A saved draft has wrong or malformed content | Open the identified post, compare the affected section with its source, and correct the draft. Preview it and repeat the full approval checks before adding it to a later release. |
| Two posts appear to represent one source | Compare their IDs, content, status, and intended destination. Decide which post is the intended one before removing or changing either. Update the ledger so the extra item is not selected by mistake. |
| Only some approved drafts published | Record which posts are live and verify their public pages. Inspect the saved status of the remaining posts and resolve the issue on those rows. Do not select the successful posts again just to retry the others. |
| A held post was published accidentally | Stop further batch actions. Open the affected post, review its visibility and change its status as appropriate for your situation. Check the result and notify the people responsible for the release. Returning it to draft or making it private does not undo any prior public exposure. |
| A live post needs a correction | Identify the existing post and correct that item, then check its public page again. Avoid creating a new post merely because the source changed. |
For a correction to an existing Google Docs-based article, see the same-post Google Docs update walkthrough. Confirm that you are updating the intended post and inspect the saved result; do not assume that any particular retry or update automatically prevents duplicates.
same-post Google Docs update walkthrough

After a held post is repaired, its next release can be a single-post publication or part of a later approved batch. Update the review result and release decision first. The old hold reason remains useful context, but it is not evidence that the corrected version has passed.
Start with one saved result
If your articles are still in documents, open Tenwrite and create a sample WordPress draft from one finished article before preparing a larger batch.
open Tenwrite and start with two documents
Find that draft on the intended site and check its saved title, headings, links, images, and draft status against the source. If it matches, prepare the rest of the batch and give every saved post the same review. If it does not, resolve the difference before moving more articles. The useful result is an identifiable, reviewable draft that can later be approved for release.
