## TL;DR

Publish to dev.to, Substack, and Blogger from one canonical source: write the article once, set the canonical URL to your own site, adapt the formatting per platform, and schedule the posts staggered by a day or two. dev.to and Blogger have APIs; Substack needs its editor or email-to-post. Always check each platform's automation rules first.

```text
how to publish one article to dev.to, Substack, and Blogger automatically
```

## Use this when

- Syndicating a long-form article across platforms
- Running a regular publishing cadence
- Each platform's audience is worth reaching

## Not for this skill when

- A platform prohibits automated posting (respect it)
- The article is platform-specific (write natively instead)
- You have not set canonical URLs (fix that first)

## Steps

1. Write the canonical version on your own site first. This is the version search engines should rank; everything else points to it. Expected: a live canonical URL before any syndication.

2. Adapt per platform. dev.to takes markdown via API; Blogger takes HTML via API; Substack works best through its editor or email-to-publish. Expected: three platform-ready versions, not one pasted everywhere.

```
platform paths:
  dev.to:    API with markdown body
  Blogger:   API with HTML body
  Substack:  editor or email-to-post
```

3. Set canonical links on every copy. dev.to and Blogger both support canonical URLs; use them to point at your original. Expected: no duplicate-content confusion in search.

4. Stagger the publishes by a day or two. Same-hour blasts look automated and split the initial audience. Expected: three publishes across three days.

5. Log each publish with its URL. Expected: your publishing log shows all three copies and their canonicals.

## Variant phrasings

### cross-posting to dev.to Substack and Blogger

Canonical on your site, adapted formats per platform, canonical links set, staggered schedule.

### automatic multi-platform article publishing

One source, three adapters, canonicals everywhere, logged.

### syndicating blog posts across platforms

Write once, adapt per platform API, stagger, and always canonicalize.

## Why it happens

Each platform has a distinct audience and its own formatting and API quirks, but the content is the same. A canonical-first workflow gets you the reach of three platforms with the SEO safety of one source of truth.

## Edge cases / pitfalls

- Substack's automation surface is thin; do not fight it, use the supported path.
- dev.to rate-limits API publishing; check the current limits before batching.
- Blogger needs HTML, so keep a markdown-to-HTML step in the pipeline.
- If a platform rejects the post, read the reason; do not just retry.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_PSU-AN--IFfLyrh_zL2GmQ