---
title: "Publish, update and withdraw articles"
description: "Choose a full-article destination and manage external copies without bypassing Blogged’s existing approvals."
updated: "2026-09-11"
verifiedAgainst:
  - apps/web/app/app/integrations/page.tsx
  - apps/web/components/publishing-integration-article.tsx
  - apps/web/lib/server/publishing-integrations-service.ts
  - apps/web/lib/server/publishing-integrations-editor.ts
  - apps/web/lib/server/publishing-integrations-lifecycle.ts
  - packages/shared/src/publishing-integrations.ts
---

## Save destinations for new articles

In **Connections & routing**, select one verified connection for the full article.
You can add up to three external summary destinations that support noindex.
**Show a summary and full-article link on my Blogged blog** is checked by default.
Choose **Save destinations** to activate this routing.

Existing drafts and published articles keep their destination. New eligible
articles bind to their destinations at their first release. Later Project routing
changes do not move those bound articles.

## Full article and summaries

The full article goes to one destination. A summary uses up to 1,600 characters
of the already-reviewed excerpt, description or title; setup does not generate
a new article. Summary pages are marked noindex and link to the full version.
Blogged keeps summaries hidden until the full article is verified. A destination
that cannot control indexing cannot be used for external summaries.

Your CMS theme owns how its public page renders. Review its title, images,
metadata, canonical URL and indexing settings. Search Console still needs the
correct property and authorization; publication does not guarantee indexing.

## Review an update

<Steps>
  <Step title="Save the working copy in Blogged">
    Edit through the article's existing workflow. Autosave does not overwrite the CMS copy, and
    existing approval controls still apply.
  </Step>
  <Step title="Inspect the CMS version">
    Open **External publication** in the editor. Inspect the remote version before publishing an
    update. A changed CMS version requires review.
  </Step>
  <Step title="Use the available review action">
    Publish the reviewed saved version, or import supported CMS text into the Blogged working copy
    and review it there. Advanced widgets and CMS images are not imported by the text comparison
    tool. Full Autopilot retains its content authority; these controls cannot bypass it.
  </Step>
</Steps>

## Pause, return to hosting, or disconnect

| Action                                  | Effect                                                                                                             |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Pause delivery                          | Preserves queued external work and stops new delivery work; a request already accepted by the CMS may still finish |
| Save destinations                       | Saves the selected routing for future eligible articles and enables delivery                                       |
| Use Blogged hosting for future articles | Returns future publication routing to Blogged hosting; existing bound copies stay assigned                         |
| Disconnect                              | Removes credentials only after active or pending managed copies no longer require the connection                   |

Use the original **Unpublish** action to request withdrawal. Blogged tracks each
managed copy until its withdrawal is confirmed; deleting a bound article is
refused while a copy still requires withdrawal. Disconnecting is not a shortcut
to deleting remote content. Already copied CMS content remains on the customer's
infrastructure when a subscription ends.

Follow [delivery troubleshooting](/integrations/troubleshooting) when a copy is
waiting, needs attention, or conflicts with a CMS edit.