This article may contain affiliate links. This article is documentation-based research, not a live API test. It uses only the supplied official Surfer documentation and our own editorial reasoning. We do not claim to have run a Surfer trial, measured rankings, or tested any export behavior directly. The goal is to help you choose between updating an existing indexed WordPress post and creating a new draft when a Content Editor draft is ready.
Introduction
You have a Content Editor draft that rewrites a live WordPress post. The live post is indexed and has backlinks. Surfer’s export dialog offers two paths: create a new WordPress draft or update an existing post or page. The help page explains the mechanics: a new export defaults to draft, and updating a published post makes changes visible immediately, while updating a draft keeps it a draft (https://docs.surferseo.com/en/articles/9071075-how-to-export-content-between-surfer-and-wordpress). It does not tell you which path to choose when the live URL is already an asset. Our editorial heuristic fills that gap: treat the existing post’s URL as the asset, not the draft. If the live post is indexed and has any inbound links, update it in place. If the rewrite targets a different primary keyword, export as a new draft and keep the old post. This is our suggested process, not a vendor API contract. For related background on how optimization signals fit into editorial workflows, see our /surfer-seo-review/.
Documented Workflow
The official help page describes the export steps: in the Content Editor, open the Publish and Export tab, select WordPress, then choose whether to create a new WordPress draft or update an existing post or page. You then review post settings such as title, category, status, and type, which are fetched from your WordPress settings. A new post or page defaults to draft. Updating an existing post or page keeps its current status: a published post stays published and changes are visible immediately; a draft stays a draft (https://docs.surferseo.com/en/articles/9071075-how-to-export-content-between-surfer-and-wordpress). The Content Editor overview adds that the Publish or Export step is where you add meta tags, copy or download content, or export directly to WordPress, and that Content Editor is a writing and optimization tool rather than an auto-publisher (https://docs.surferseo.com/en/articles/5700347-content-editor-overview).
Our suggested process is a one-line Export Direction Note written before you click export. It has three parts: (1) the target post ID and its current status, (2) the reason for update-vs-new, and (3) the one thing that would flip the choice. Example: “Update post 4821; reason: indexed and linked; flip if the brief changes the target keyword so much that the old URL no longer matches intent.” This note is our editorial artifact, not a Surfer feature. It forces you to name the asset and the exception before the export dialog makes the decision feel like a simple toggle.
Editorial Decision Checklist
Use this checklist when a Content Editor draft is ready and the live WordPress post is already indexed. Each item is a decision, not a vendor instruction.
- Confirm the live post’s current status in WordPress. If it is published, updating it will keep it published and changes will be visible immediately, per the help page (https://docs.surferseo.com/en/articles/9071075-how-to-export-content-between-surfer-and-wordpress).
- Check whether the live URL is indexed. If you cannot verify indexing, treat the URL as if it is indexed when it has any age or inbound links, because a new URL would start from zero.
- Check whether the live URL has inbound links. Even one relevant inbound link is enough to make the existing URL the asset in our heuristic.
- Compare the draft’s primary keyword with the live post’s primary keyword. If they match, update in place. If the draft targets a different primary keyword, export as a new draft and keep the old post.
- Write the Export Direction Note before opening the export dialog. Name the target post ID, the reason, and the flip condition.
- Choose update when the live post is indexed and linked and the primary keyword still matches. Choose new draft when the rewrite is a different topic or keyword.
- After export, verify the live post’s status and visible changes in WordPress. The help page notes that updating a published post makes changes visible immediately, so check the live page rather than assuming a draft was created (https://docs.surferseo.com/en/articles/9071075-how-to-export-content-between-surfer-and-wordpress).
- If the draft was created from an existing WordPress post via the Surfer tab, remember that the help page describes exporting the newest version back into the connected Content Editor without counting toward the Content Editor limit (https://docs.surferseo.com/en/articles/9071075-how-to-export-content-between-surfer-and-wordpress). This is a workflow detail, not a ranking signal.
Worked hypothetical example: a Content Editor draft rewrites a post that has been live for a year and has three inbound links. The editor updates the existing post rather than exporting a new draft, and writes: “Update post 4821; reason: indexed and linked; flip if the brief changes the target keyword so much that the old URL no longer matches intent.” The editor then checks the live page after export because the help page says published updates are visible immediately.
Exception that changes the choice: if the rewrite targets a different primary keyword than the existing post ranks for, export as a new draft and keep the old post. Updating in place would strand the old keyword with no page. This exception is our editorial rule, not a Surfer recommendation.
Limits
This guide is documentation-based research, not a live API test. It does not measure indexing, rankings, or backlink value. The help page does not state how search engines treat updated content, whether a new draft will be indexed, or how long changes take to appear in search. Optimization scores and AI visibility reports are vendor signals, not Google ranking factors or indexing guarantees (https://docs.surferseo.com/en/articles/5700347-content-editor-overview). The absence of a detection signal is not proof of human authorship, and the presence of a vendor score is not proof of ranking impact. The help page also does not document auto-publishing, data retention, access controls, or immutable brand versions; we do not imply those exist. Our checklist is an editorial heuristic, not a vendor API contract, and it may not fit every site. If your WordPress permissions or editorial review process require a draft-first workflow, adapt the checklist rather than treating it as a rule. We do not include prices or quotas because the decision at hand does not depend on them.
Final Verdict
When the live WordPress post is indexed and has inbound links, update it in place and write the Export Direction Note before you export. When the rewrite targets a different primary keyword, export as a new draft and keep the old post. This is our suggested process, not a Surfer feature. The help page gives you the mechanics; you supply the judgment about which URL is the asset. Use the checklist, verify the live page after export, and treat vendor scores as signals rather than guarantees.