Skip to main content
Publishing works the same way whichever destination you use. What differs is what the destination gives back, and where each part of the article lands.

​
Publishing an article

Open a finished article and click Publish in the top-right corner. The Publish Article dialog lists every connected publishing destination, one row each, with a button on the right: Below the list, Connect another destination lets you connect one on the spot.
Publish article dialog over the article editor, listing a connected WordPress destination and a Publish now button

Choosing a destination

Only publishing destinations appear here — WordPress, WooCommerce, Webflow, Shopify, Framer, Wix, Ghost, HubSpot, Notion, Strapi, GitHub, the Headless API and Webhook. Search Console and Analytics are data sources; they never receive content.
Publishing is queued, not instant: the request returns a job and the dialog waits for it. A typical publish takes a few seconds — longer when images have to be uploaded.

​
Confirmation

When the job finishes, the dialog shows Article Published and a line that depends on the destination:
Publish dialog confirming the article was published to WordPress, with a link to the live post

A destination that returns a URL

Publish dialog confirming the article was published and delivered to the webhook endpoint

A destination that doesn't

Either way the article moves to Published and appears under the Published tab.

​
What gets sent

Whatever the destination, we send the same article:
  • Title and slug
  • Body, rendered from Markdown to HTML
  • Meta title and meta description (the meta description doubles as the excerpt or summary)
  • Featured image, where the destination supports one
  • Focus keyword, as a tag where the destination has tags
  • Author — the article’s author persona, falling back to your workspace name, where the destination takes an author name
Before sending, links to your other articles are resolved and dead links are removed. The article’s JSON-LD schema (Article, plus FAQ when the article has one) goes wherever the destination can carry it: Destination-specific mapping is documented on each connector’s page.

​
Re-publishing

Once an article is published, the editor swaps Publish for Re-publish and Unpublish.
  • Re-publish pushes your edits to the same item at the destination — it updates in place and never creates a duplicate. It is disabled until something has changed (“Nothing has changed since this article was last published.”).
  • Publishing an already-published article a second time is refused: “This article is already published. Re-publish it to push your changes.”
  • If the item was deleted at the destination in the meantime, Shopify, Ghost, HubSpot, Notion, Webflow, Framer and Wix create a fresh one instead. WordPress, WooCommerce and Strapi report an error.

​
Unpublishing

Unpublish takes the article down at the destination and moves it back to Ready in SeoSorted:
Unpublishing clears SeoSorted’s link to the item. Publishing the article again afterwards creates a new item at the destination, and the old draft stays there until you remove it.

​
Deleting an article

Deleting an article in SeoSorted also removes it at the destination it was published to — except for two connectors:

​
Comparison pages

Comparison pages can only be published to Webhook or Strapi for now. Other destinations show Not supported yet in the Publish dialog, and an attempt through the API is refused with “Comparison pages can only be published through Webhook or Strapi for now.”

​
Scheduling and auto-publish

Articles can also publish on a schedule instead of on demand:
  • Add to calendar on any article sets the date it should go out.
  • When that time arrives, a background job publishes it to the article’s own destination if it has one, otherwise to the workspace’s default publishing destination, otherwise to the only connected destination.
  • Auto-publish, set during onboarding or in project settings, sends newly generated articles out without a manual step.
Scheduled publishing needs an active paid plan and a connected destination at the time it fires. If the plan lapsed, the connector was disconnected, or it flipped to Error after repeated failures, the scheduled article stays where it is instead of publishing. An article with no content yet is skipped too. Check the Integrations tab if a scheduled post doesn’t appear.