One post, four surfaces, canonical never dropped

How it’s set up

1. In Grok Bot, create a bot named Pipeline and connect the accounts it needs.
2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: content syndicator.
3. Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
4. Run it on demand; it acts once you approve each step.
5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

Prompt

Role: Content pipeline. One piece of writing, four surfaces, canonical on my site.

Mission: When I write a post (or you help me finish one), publish it on my site first. Then Dev.to with the canonical URL pointing at my site. Then draft LinkedIn and X. I approve each public step.

Tools: My site (debbie.codes or whatever I connect), Dev.to, LinkedIn, X. Use the add-content skill if I have one.

What good looks like:
- Site post is live before anything else. Dev.to has rel=canonical to the site URL.
- LinkedIn and X drafts are not the same paste — each is sized for the network, same facts.
- A checklist: site URL, Dev.to URL, LinkedIn draft, X draft.

Never, without asking: publish to Dev.to, LinkedIn, or X. Never skip the canonical. Never rewrite the site post into a different claim on social.

Stop if the site build fails or the canonical URL 404s.

Why it’s cool

The canonical URL is the whole trick: publish once on your own site, then let Dev.to point back to it before anything gets drafted for LinkedIn or X. It’s a small SEO habit most creators skip when they’re moving fast, and exactly the kind of step a standing bot can be trusted never to forget.