Q: Why is canonical-link discipline a separate section?

Because most cross-posting setups silently break it — and that is the most expensive SEO mistake you can make. Without rel=canonical, Google sees five near-duplicate pages and indexes the platform with the highest domain authority (usually Medium or Dev.to), not your blog. With rel=canonical pointing home, the syndicated copy passes link equity to your original. The checklist enforces the canonical URL declaration on each platform's own settings panel.

Question 1

What's in the checklist?

Accepted Answer

Six sections: (1) the structured metadata block (title, description, slug, tags, cover, canonical, date, target keyword) you fill in once in Notion; (2) the canonical-link recipe with per-platform setting locations; (3) per-channel checklists with format-specific gotchas (LinkedIn Unicode, Medium HTML clipboard, Dev.to markdown + hash slug, X thread shape, etc.); (4) UTM strategy; (5) cross-post sequencing; (6) post-publish verification (sitemap regen, GSC, Bing IndexNow). Hand it to your editor or pipe it through Make.com / n8n as a Notion-database template.

Question 2

Why is canonical-link discipline a separate section?

Accepted Answer

Because most cross-posting setups silently break it &mdash; and that is the most expensive SEO mistake you can make. Without rel=canonical, Google sees five near-duplicate pages and indexes the platform with the highest domain authority (usually Medium or Dev.to), not your blog. With rel=canonical pointing home, the syndicated copy passes link equity to your original. The checklist enforces the canonical URL declaration on each platform's own settings panel.

Question 3

What platform-specific gotchas does the checklist call out?

Accepted Answer

LinkedIn: paste Unicode (no rich-text formatting beyond what LinkedIn parses; bold/italic via Unicode characters). Medium: paste as HTML to keep headings (markdown paste breaks). Dev.to: markdown is fine, but slug ends in a random 5-char hash &mdash; strip before using as a UTM key. X: thread shape with hook tweet + 4-7 follow-ups + final link to canonical. Hashnode: canonical setting is in the article's metadata sidebar, not the editor. Newsletter: rendered HTML, not source markdown.

Question 4

How does the UTM strategy fit?

Accepted Answer

UTM tags go on the **link back to your canonical from the syndicated copy**, not on the canonical URL itself. utm_source = platform slug, utm_medium = syndicated, utm_campaign = article slug (strip Dev.to's hash). This lets analytics attribute traffic per platform without polluting Google's view of the canonical URL with parameter noise.

Question 5

What does post-publish verification cover?

Accepted Answer

Three steps. First, regenerate the canonical home's sitemap. Second, run `gsc-nudge <url>` or its equivalent &mdash; sitemap PUT + Indexing API URL_UPDATED + URL Inspection &mdash; so Google sees the new URL within hours, not weeks. Third, ping Bing IndexNow. Optional: schedule the 48-hour engagement check that feeds back into the next article's brief.

Notion Publishing Checkliste Notion-to-Multi-Platform Publishing Checklist

ErforderlichRequiredArtikel & CanonicalArticle & canonical

Syndikations-KanäleSyndication channels

Metadaten-BlockMetadata block

UTM-StrategieUTM strategy

Generierte ChecklisteGenerated checklist

Notion + Make.com Pipeline in 2 WochenNotion + Make.com pipeline in 2 weeks