To publish Google Docs to WordPress with Tenwrite, open WordPress → New Export, choose your site, select your document, and choose Draft. Review the image, featured-cover and post settings, click Start Export, then check Confirm publication outcome before choosing Confirm Export. Inspect the WordPress draft and publish when it is ready.
You can also upload DOCX, Markdown or text files in Tenwrite’s web app. A Word file does not have to become a Google Doc just to be published. Choose Google Docs when you want collaborative writing and a linked source for later updates; choose a local upload when your approved source is a file.
This guide explains the current workflow, including images, supported SEO fields, publication confirmation and troubleshooting. Screenshots use Tenwrite’s approved demonstration document and a test site. The demonstration stops at draft confirmation; it does not create a test post.
Should you paste into WordPress or use Tenwrite?
Copying a short, simple article into WordPress can work. The current block editor understands common content such as paragraphs, headings, lists and images. You should still review the result in your theme, because document formatting and a website layout are different things.
Images need a more careful explanation than “pasting always leaves Google URLs.” WordPress’s current Image block documentation says images copied from Google Docs or Word may upload automatically to the Media Library. Select an image and check the available upload controls and saved media rather than assuming every paste succeeded or failed.
Tenwrite is useful when you want a repeatable publishing process: choose the source, set post details, control image transfer and formatting, then update the existing article from its linked document later. It does not remove the need for an editorial review or a destination preview.
| Source | Best fit |
|---|---|
| Google Docs | Shared writing and linked document updates |
| DOCX upload | An approved Word file with embedded images |
| Markdown or text upload | A file-based writing workflow |
For an occasional basic post, use the method that needs the least maintenance. For regular publishing from documents, Tenwrite’s Google Docs to WordPress workflow keeps the source and publishing controls in one process.
Prepare the document and connect your site
Finish the factual and editorial review in the source. Remove internal notes, placeholder links and unfinished sections. Check that you have permission to publish the included images. A converter cannot decide whether a screenshot contains private customer information or whether a quoted claim is accurate.
Use real heading styles in Google Docs. When your WordPress template supplies the main article title, use Heading 2 for sections and Heading 3 for subsections. Avoid adding another large title in the body unless the design deliberately calls for it. Use actual lists and keep complex tables narrow enough to read on a phone.
Prepare a topic-specific cover separately from supporting screenshots. Put it first in the document if you intend to use Tenwrite’s first-image featured setting. Add descriptive alternative text and keep essential instructions in the article text, so readers do not have to decipher a screenshot to complete a step.
Connect the destination through WordPress → My Sites if it is not already available. Tenwrite supports WordPress.com connections through OAuth and self-hosted WordPress connections using Application Passwords. Self-hosted sites need reachable HTTPS addresses and a working WordPress REST API. Follow the site connection guide for your hosting type.
Use an account with the permissions needed for the intended post action and media upload. If a connection fails, investigate the actual authorization or network error. Do not disable site security broadly just to make an export work.
Publish Google Docs to WordPress: a draft-first walkthrough
1. Open New Export and choose Post or Page
Sign in to the Tenwrite web app and open WordPress → New Export. Select Post for a normal blog article or Page for standalone material such as an About page.
Posts can use categories, tags and sticky settings. Pages have controls such as parent page and menu order. Choose the correct content type before setting details, rather than publishing a page and expecting it to behave like a blog post.
The Google Docs add-on provides a document-based route too. This walkthrough uses the web app because it also exposes local-file upload. Do not assume that a file-upload instruction applies inside the add-on’s document sidebar.
2. Select the destination and writing source
Choose your WordPress site under Destination Site. Read the domain as well as the site name, particularly when you manage several client sites or keep a staging site beside production. The destination applies to the current export batch.
Click Google Docs, choose your approved document in the picker, and confirm the selection. The export table shows the selected document and its progress state. Start with one representative article before moving to a larger batch.

Current web interface: choose a Google Doc or upload a local file. This selected source is approved demonstration content.
For a local source, use Upload a file. Current web-app limits are 25 MiB for DOCX and 5 MiB for Markdown or text. Markdown accepts .md and .markdown; plain text uses .txt. PDF is not a supported publishing source.
A DOCX can include embedded pictures. Markdown image references need accessible HTTP or HTTPS image URLs; relative paths on your computer do not include those files in a single Markdown upload. Plain text carries neither document formatting nor embedded pictures. Direct editing of a frontmatter table through Tenwrite requires a native Google Doc, which is a separate capability from publishing a DOCX.
3. Review title, slug, excerpt and post details
Check the Title rather than treating a working filename as the final headline. Remove review markers and make the article’s purpose clear. Review the Custom URL Slug before the first publication; on an existing article, keep its established URL unless you have a deliberate redirect plan.
Write an Excerpt that summarizes the article for archive or theme displays. An excerpt and an SEO description are separate fields, even when a particular site chooses to reuse one for the other.
For a post, select relevant Categories and Tags. Search for existing terms before creating near-duplicates, and confirm selected values so they appear as chips. Set comments and pingbacks according to your publication’s policy. Do not enable sticky simply because an article is new.
Choose Draft for the first export. If the document contains frontmatter, read the notice: filled document fields override matching form fields and may be locked. Use Edit existing frontmatter to change those values, then refresh document settings and review the resolved outcome.
4. Choose blocks and formatting cleanup
Open Show Advanced Options. Choose WordPress Blocks for a site that uses the block editor; choose Classic HTML for a workflow that needs classic markup. The WordPress block editor guide explains how blocks represent content such as paragraphs, headings and images.
Begin with Balanced cleanup unless you have a reason to retain more source styling. Original keeps more Google Docs styling; DOCX uses the same conversion in either cleanup mode. Your theme still controls much of the page’s appearance, so preserving more document formatting is not automatically better.
Change individual transformations to solve an observed problem. For example, heading demotion can help when a source contains an unwanted extra H1. Font-family or font-size removal can let the theme supply its typography. Avoid switching every option at once: it becomes harder to identify what changed the result.
5. Set image transfer and the featured cover
Under Image Processing, review Upload Images to Media Library. When enabled and successful, Tenwrite saves document images to the destination library and uses the WordPress media URLs. Check the export result and any warnings; a picture appearing in the source is not proof that it reached WordPress.
Enable Set First Image as Featured Image when the first source image is your intended cover. Do not enable it blindly when the document begins with a step screenshot, logo or decorative divider.

These are separate controls: one handles image transfer, while the other chooses the source’s first image as the post’s featured image.
A featured image is attached to the post separately from ordinary body images. Its placement depends on the theme and template; see WordPress’s featured-image guidance. Tenwrite’s first-image option can remove that cover from body content, so do not leave a caption that only makes sense directly below an image that moved.
Preview the top of the article and its listing card. If the cover appears twice, check the theme’s featured-image display and the body content before deleting media. Also inspect the crop: keep important words and subjects away from edges that a card template may trim.
6. Review supported SEO fields
For supported SEO transfer on a self-hosted WordPress site, install and activate the Tenwrite WordPress plugin. Yoast SEO or Rank Math alone is not enough for Tenwrite’s integration. The plugin saves supported values and maps them to the corresponding Yoast or Rank Math fields when those plugins are active.
The supported controls are:
- SEO title: the requested search-title metadata, distinct from the visible article heading.
- SEO description: a concise, accurate description of the article.
- Focus keyword: a phrase used by the site’s SEO workflow; entering it does not create a ranking benefit by itself.
- Canonical URL: leave blank for the normal post URL unless another canonical is intentional.
- No Index: request that search engines do not index this page.
- No Follow: request that search engines do not follow links on this page.

Supported SEO transfer requires the Tenwrite plugin. The form also offers indexing controls below the fields shown here; review those deliberately.
Keep the description specific to the finished article and avoid promises the content cannot support. Treat character suggestions as editing aids, not guarantees of how Google will display a result. For a normal public article intended for search, do not accidentally select No Index.
Manual SEO controls are available across plans; optional AI generation has separate eligibility and credit rules. WordPress.com and other SEO plugins should not be assumed to support the same mapping. In particular, do not assume AIOSEO uses Tenwrite’s saved values: verify the title, description, canonical and robots metadata rendered by your actual site. Read the Tenwrite SEO plugin guide for supported fields and frontmatter precedence.
7. Confirm that the first export will stay a draft
Check the destination, content type and document count at the top. Click Start Export to open Confirm publication outcome. Publishing has not started at this review step.
For the first export, the resolved result should say Will remain a draft. If it says publish now or schedule, use Back to settings and correct the source or form. Filled frontmatter takes priority: a future date with Automatic publication can schedule a document even when the form still displays its default Draft choice. Explicit Keep as draft remains a draft even with a date.

The demonstration stops here. In your own workflow, choose Confirm Export only after the resolved outcome matches your intended draft state.
Choose Confirm Export when the result is right. Watch the row’s progress and read any error or warning. A Pending or Processing row is not a completed export. On success, use the available Edit or Preview link to inspect the destination.
Review the draft, then publish or schedule it
Open the actual WordPress draft. A draft preview normally requires an authorized login; a login screen in a private browser window does not prove that the content is missing.
Check the complete article at desktop and phone widths:
- The correct title appears, with a sensible heading hierarchy and no accidental duplicate title.
- All intended images load, have useful alt text where appropriate, and fit the content column.
- The featured cover has the right crop and appears where your theme expects it.
- Tables, lists and links are usable; the article’s CTA reaches the intended page.
- Categories, tags, comments, excerpt and SEO settings match the editorial plan.
When ready, open the existing draft’s Full Edit in Tenwrite, choose Publish or Scheduled, and review the final confirmation. Scheduled publication needs a valid future date. Tenwrite interprets dates using the timezone saved in your Tenwrite account, shown in the outcome preview; do not infer it from your device clock. Frontmatter may need updating first if it explicitly keeps the source as a draft.
After publication, check the public URL and the actual metadata. For a scheduled article, check the destination after the planned time too; publication depends on the destination’s scheduling operation as well as accepting the requested date.
Update the same WordPress post later
For a linked Google Doc, approve the revision in the original source, find the article under WordPress → My Posts, and choose Options → Sync Post. Review the publication outcome and choose Confirm Sync. Tenwrite re-exports into the existing post instead of creating another article.
If someone edited the body directly in WordPress, reconcile those changes into the Google Doc first. Otherwise, the next document sync can replace them. Blank publication settings preserve the existing state during sync; explicit frontmatter settings still need review.
For a local-file article, open its existing Full Edit, upload the revised file, and choose Update Post. A local upload is a snapshot, not a live connection to a file on your computer. Starting another New Export is not the same-post revision workflow.
Sync Site Content reads the site’s latest state into Tenwrite’s index. It does not push your document edits out to WordPress. The Sync Post guide explains the direction and confirmation behavior in more detail.
Troubleshooting the first export
The site is missing or authorization fails
Check the connected site and the intended WordPress account under My Sites. Confirm the destination address, required permissions and REST API access. Read the specific error before reconnecting. If a security rule blocks a request, address that rule with the site administrator rather than switching off protection across the site.
An image is missing, external or in the wrong place
Compare the source, export result, Media Library and rendered page. Look for a failed upload, an inaccessible Markdown image URL, a theme display problem, or a first image that became the featured cover. Google Doc image warnings can leave original image references; those are not equivalent to successfully saved media. For the full repair sequence, follow Google Docs images not showing in WordPress.
A field is locked or the post status surprises you
Check the document’s frontmatter. Filled fields control their matching values; clearing an unrelated form input does not remove the source setting. Edit the frontmatter, save, refresh document settings and review the outcome again. Use the WordPress frontmatter guide for status, date and timezone rules.
The post looks different from the Google Doc
Compare one problem at a time: heading levels, theme fonts, image width or table layout. Check the selected output format and cleanup settings before changing the source. A WordPress page does not have to imitate a printed document to be readable. Prefer a consistent theme layout over preserving every original font or fixed width.
SEO fields are saved but the search preview looks different
Confirm the Tenwrite plugin is active and that your SEO plugin uses the supported mappings. Inspect the rendered metadata rather than relying only on a saved form. Google may choose different title links or snippets, so a search-result difference alone does not establish that the transfer failed.
When to move beyond manual publishing
First establish a reliable manual draft, preview and same-post update. Then consider Drive or Sheets automation for a recurring workflow. Drive automation watches configured Google Docs folders; Sheets automation can organize supported content and document links with publishing settings.
These publishing automations run hourly on eligible Pro and Agency plans, not instantly after every edit. Frontmatter, source access and publication choices still apply. Compare the current plans with your actual volume before building a larger process.
Start with one article you can review
Choose a finished document with a cover, a few supporting images and a clear reader goal. Send it as a draft, inspect the result in your theme, and publish deliberately. Once that works, keep the source current and update the existing post when the article changes.
Open Tenwrite and publish your first WordPress draft. You can use a Google Doc or upload the approved file you already have.
