Skip to content

Publishing Workflows

Blog SEO and Image Delivery

SEO and image capabilities for WordPress, Ghost, Hashnode, DEV.to and Blogger, with delivery checks and recovery guidance.

A post moving into a publishing calendar

Article content, search details and featured image delivery

Postly uses the same publishing services for dashboard posts, bulk CSV, connected Google Sheets, API requests and MCP tools. Each blog has different fields and permissions. Select the destination first, then prepare its supported settings.

BlogSearch detailsImages and social previews
WordPressSEO title, description and canonical through your installed SEO pluginFeatured attachment or uploaded image with alt text; plugin-dependent Open Graph and X overrides
GhostNative SEO title, description and canonicalFeatured image, alt text, caption, separate Open Graph and X fields
HashnodeSEO title, description and canonical for drafts and published articlesCover image and Open Graph image; separate social text overrides are unavailable
DEV.toArticle title, description and canonicalMain image and body images; no separate SEO title or Open Graph/X overrides
BloggerArticle title and labelsImages in the HTML body; the API does not expose custom SEO descriptions, canonicals or social overrides

Prepare the article

  1. Choose the connected blog in the composer and open its settings.
  2. Set the article title and the supported search fields. WordPress also has an SEO plugin selector.
  3. Select the featured or cover image where supported. A social preview image is a separate field; setting one does not replace the article's featured image.
  4. Add meaningful alt text where available. Existing WordPress media-library attachments keep their current alt text; edit those in WordPress if needed.
  5. Preview body images for each destination. Destination-specific media overrides are used when supplied.

For remote image URLs, use a publicly reachable image, not a sharing page, login page or expiring URL. Postly preserves the image file type and filename when uploading to WordPress and Ghost. The destination still enforces its permitted formats, file-size limits and upload permissions.

Review delivery

Open the publishing result. A WordPress post can be created successfully while SEO delivery needs review. The result retains the article link and shows a warning if the SEO writer rejects the request or does not confirm the supplied values.

Do not publish the article again to fix SEO. Open the existing article in WordPress, correct permissions or plugin setup, and save its metadata there. Postly does not automatically recreate the article after an optional SEO failure.

For a published article, view the public page after clearing the relevant site/CDN cache. Check the page's title, meta description, canonical, Open Graph image and X image. Plugin settings, themes and caching can affect the final output. Saving metadata is not a promise that a search engine will display the supplied description; crawlers may choose their own snippet. Drafts have no public page to inspect yet.

Related guides

Previous guide

Analytics and Reporting

Review campaign performance, compare channels, and turn activity data into the next publishing decision.

Next guide

API Workflows

See how Postly API fits into app backends, CMS pipelines, automations, and custom publishing systems.

Related guides