I keep seeing writers publish the same text in several places.
Sometimes it is intentional. Sometimes it is almost innocent. A person writes something on their blog, then puts it on Medium, then sends it through Substack, then maybe posts a version on LinkedIn or somewhere else, hoping that one of these rooms will finally have people inside.
I understand the impulse.
Writing online now often feels like placing small candles in a storm. Your own website may be the place you care about most, but the readers are scattered elsewhere. Medium has readers. Substack has inboxes. Social platforms have feeds. Search has strangers. So the temptation is obvious: why keep a post in one place when the internet is already fragmented?
The problem is that search engines do not experience this as poetic distribution.
They may experience it as duplication.
The same text appears on your blog, on Medium, maybe on Substack, maybe somewhere else. From the human side, this can feel like one writer trying to let the work travel. From the machine side, it can look like several very similar pages competing to be the main version of the same thing.
That is where canonical links enter the story.
They are not magic. They are not a legal stamp. They are not a perfect shield against every SEO problem. But they are one of the cleanest tools we have for saying: this version is a copy, and the original home of the text is over there.
For an independent writer with a personal blog, that matters.
Because the goal is not necessarily to hide from platforms. The goal is to use platforms without letting them become the only place where your work exists.
Quick verdict: canonical links are worth using
Yes, canonical links are worth using if you republish the same or very similar text in more than one place.
Especially if you have your own blog.
The cleanest version is simple: publish the original post on your own website, then repost it on a platform that lets you set a canonical link back to the original URL. Medium is the obvious example because it has an import tool and canonical settings built for this. In that setup, your blog remains the home of the work, while Medium becomes an extra distribution layer.
That does not mean the Medium version will never appear in search. Google can still make its own decision. A canonical link is a strong signal, not a handcuff.
But it is still much better than throwing the same post everywhere and hoping the machines understand your emotional intentions.
They will not.
Machines are not moved by your journey as an independent writer.
They want signals.
A canonical link is one of those signals.
What is a canonical link?
A canonical link is a piece of code that tells search engines which URL should be treated as the main version of a page when the same or very similar content exists in more than one place.
In HTML, it looks like this:
<link rel="canonical" href="https://www.example.com/original-post/">
That line normally appears inside the <head> of a page.
If the page has a canonical link, you will see which URL it is pointing to as the preferred version.
The basic meaning is:
This page may be a copy, duplicate, variant, or repost. The preferred version is the URL inside the href quotation marks.
That is the technical version.
The human version is simpler:
This is not the real home of the text. The real home is over there.
That is why canonical links are useful when content appears under multiple URLs. Maybe your site creates tracking URLs. Maybe you have the same page with and without a trailing slash. Maybe an ecommerce product can be reached through several filtered category pages. Maybe you published a blog post on your own domain and then reposted it on Medium.
In all of these cases, canonical links help reduce confusion.
They give search engines a preferred version.
They help consolidate signals.
They make it easier to treat one URL as the main address of the content.
For a small writer, the practical use is very simple: if your blog is the original home, then your reposts should point back to your blog.
A canonical link is a signal, not a guarantee
This is the part many people miss.
A canonical link does not force Google to obey you.
It is not the same as a redirect. A redirect sends people and bots somewhere else. A canonical link leaves the page where it is, but tells search engines which version you prefer. That difference matters.
If you redirect a page, the visitor is moved. If you canonicalize a page, the visitor stays there, but the search engine receives a preference.
This means Google can still choose a different canonical URL if it thinks another version is better, cleaner, more useful, more trusted, better linked, or technically stronger. In practice, this is one of the risks of reposting your own work on large platforms. Your personal blog may be the original home, but a platform like Medium can have much more authority, more internal distribution, more links, and a stronger technical footprint.
So yes, canonical helps.
But no, it is not a sacred protection spell.
If your site is weak, slow, messy, poorly linked, or not clearly presenting itself as the original home of the content, a large platform may still compete with it in uncomfortable ways. This does not mean you should panic. It means you should understand the tool honestly.
Canonical is a strong hint.
Not a divine command.
Why repost at all?
Because distribution is uneven.
That is the whole reason this question exists.
If your own blog already had endless organic traffic, a loyal reader base, a strong newsletter, and perfect search visibility, you probably would not care much about reposting. You would publish at home and let the world come to you like a dignified little kingdom.
Most writers do not live in that kingdom.
Their own blog is the cleanest home for the work, but not always the best discovery engine. Platforms are not homes, but they can still be roads. Medium can put a text in front of readers who would never visit your domain directly. LinkedIn can work for professional posts. Substack can reach inboxes. Social platforms can occasionally move something. Even a repost that does not rank can still bring a few people into the wider system.
This is the practical logic.
The blog keeps the archive.
The platform helps the work travel.
A canonical link lets you do that a little more cleanly.
Medium is still the easiest example
Medium is probably the cleanest platform for this specific workflow.
You can import a story from your own website, and Medium can add a canonical URL pointing back to the original source. You can also set a canonical link manually in the story settings. This makes Medium useful as a secondary distribution layer for posts that originally live on your own domain.
That does not make Medium perfect.
A repost on Medium is still a repost on Medium. The reader is inside Medium’s interface, Medium’s ecosystem, Medium’s membership logic, Medium’s recommendation system, Medium’s comment culture, Medium’s atmosphere.
Some readers may click through to your site. Many will not. Some may follow you there. Some may only clap, highlight, leave, and disappear into the platform’s weather. That is not necessarily bad.
It is just not the same as bringing someone home.
This is the social trade-off of canonical reposting. You can tell search engines that your blog is the original source, but the human reader on Medium still experiences the Medium version as the thing in front of them. If you add a small note or CTA pointing to your website, that can help. But it can also make the platform version feel slightly less native.
The text is there.
But it is also pointing somewhere else.
That may reduce some community feeling. It may not matter at all. It depends on the piece, the audience, and how naturally you handle it.
Does Medium punish canonical reposts?
From what I have seen, no.
And structurally, it would be strange if it did.
Medium has canonical tools. It has an import tool. It gives writers a way to say that a story was originally published elsewhere. That does not guarantee distribution, of course. A repost can still flop. A good post can still disappear. A story with a canonical link can still be ignored by the platform for normal platform reasons.
But the existence of the tool itself tells you something.
Cross-posting with canonical links is not some forbidden back alley technique.
It is a normal publishing workflow.
I have also seen Medium stories with canonical links perform perfectly fine inside the platform, including stories that still included some kind of small invitation back to the writer’s own website. That does not mean Medium will reward every repost. It means the canonical link itself is not the thing I would fear.
What I would watch more carefully is reader experience.
If your Medium post feels like a cheap doorway to your blog, people may feel that. If it feels like a complete piece that also tells readers where the original lives, that is different.
The trick is not to treat platforms like trash cans for duplicated content.
Use them as rooms where the text can still stand on its own.
Substack is more complicated
Substack is a different situation.
It is a strong platform for newsletters, direct reader relationships, and subscription-based writing. But if your goal is to publish the original version on your own blog and then repost the same full post on Substack with a canonical link pointing back to your own domain, Substack is not as clean as Medium.
At least as of my current understanding, Substack does not give writers the same simple external canonical option that Medium does.
That changes the equation.
If you publish the same full post on your blog and on Substack, you may simply be leaving Google to decide which version it prefers. Maybe it chooses your blog. Maybe it chooses Substack. Maybe it changes over time. Maybe it does not matter much because the post was not going to rank anyway. But if your website’s SEO is important to you, this is not as clean as the Medium workflow.
This does not mean you can never use Substack.
It means I would be more careful.
Instead of reposting the full post there, you might send a shorter version, an excerpt, a personal note, or a newsletter-style introduction that links back to the full post on your blog. That way, Substack remains useful for reaching people, but your own site remains the real location of the full post.
If you do not care which version ranks, you can be more relaxed.
But if your own domain is part of the strategy, I would not treat Substack as a clean canonical reposting tool.
What if I post on Medium and Substack?
This is where things can get messy.
If you publish the same text on Medium and Substack, and your own blog is not part of the equation, you may decide not to care very much. Let Google choose. The search result may show Medium. It may show Substack. If your goal is simply to reach readers somewhere, this may be fine.
But if your own blog is part of the equation, I would be stricter.
The clean version is:
Publish on your own blog first.
Then repost to Medium with a canonical link pointing back to your blog.
Use Substack differently, either as an excerpt, a newsletter note, or a link-based distribution channel.
This keeps the hierarchy clear.
Your blog is the house.
Medium is a road.
Substack is a messenger, not another copy of the house.
You can ignore this if you want. Many people do. They post the same thing everywhere and move on with their lives. Sometimes nothing terrible happens. Sometimes Google figures it out.
Sometimes the stakes are too low for this to matter.
But if you are trying to build a website slowly, seriously, and with some organic search value, I think it is worth being cleaner.
Not because Google or other search engines will punish you.
Because clarity compounds.
When canonical links are useful beyond reposting
Canonical links are not only about Medium or personal blogs.
They are also used for many normal SEO situations.
A page may be accessible through several URLs because of tracking parameters, category filters, print versions, HTTP and HTTPS versions, www and non-www versions, or small CMS quirks. In these cases, canonical links help search engines understand which URL should be treated as the preferred version.
This is why many sites use self-referential canonicals too.
That means a page points to itself as the canonical version. It may look redundant, but it helps remove ambiguity. The page is saying: this URL is the clean version of me.
For most writers, this will be handled automatically by the CMS. Ghost, WordPress, and other serious publishing systems usually manage canonical URLs unless you change something manually. You may never need to touch the code yourself. But it is still worth knowing what the thing means.
Because once you start reposting your work, moving content between platforms, changing slugs, or building a wider publishing system, canonical stops being an abstract SEO term and becomes part of the architecture of your work.
My practical workflow
For now, I keep my work only on my blog, because I still believe that blogging on your blog is still worth it. It is a little harder than simply posting on ready-to-go platforms, but that is the trade-off for freedom and full agency.
But I used canonical links to repost a lot of my work to Medium at some point. Eventually, I decided to stop, because my relationship with the platform is maybe too personal to just dump my content there. But that is another topic.
Anyway, this was the workflow you can copy. It worked well for me.
First, publish the original post on your own blog.
Second, make sure the blog post has its own self-referential canonical URL.
Third, give it a little time to exist as the original after it gets indexed by search engines. I do not think this always has to be dramatic, but I like the idea of letting your own domain be the first place where the post appears. I usually waited 2–3 days before reposting. You can also use the URL Inspection / Request Indexing tool in Google Search Console to speed up the indexing process.
Example for the post you're reading right now:
site:https://www.irrelevantmatters.com/reviews/what-is-a-canonical-link-and-should-you-use-it-when-reposting-blog-posts/
If the result appears, that usually means your page is indexed. You can also inspect the URL in Google Search Console, which will tell you whether Google has found and indexed a specific page.
Fourth, repost or import it to Medium and set the canonical URL back to the original blog post.
Fifth, add a small note at the end of the Medium version and link it back to the original post. Something like: “originally published on my website,” where “on my website” can be the anchor back to the original post. It gives search engines another signal and another reason to prioritize your page over the repost.
Sixth, if you use Ghost like me, I would not use Substack for the same full post. Ghost already lets you send a newsletter from your own site, so there is no need to create another indexed duplicate. But if your blog does not have an integrated newsletter feature, you may want to publish a rewritten or shortened version specifically for Substack or another newsletter platform that also indexes newsletter posts. If the newsletter platform does not index posts publicly, canonical does not really matter, and you can ignore it.
That is not the only possible workflow. It is just what worked for me until I decided to change my strategy and become fully blog-centered.
Should you use canonical links?
Yes, if you are reposting the same text on multiple platforms and you care about which version search engines treat as the main one.
No, if you are publishing completely different versions, short excerpts, rewritten essays, or platform-native posts that only link back to the original. In those cases, you may not need canonical at all.
And maybe not obsessively, if the content is not meant to rank.
That is important too.
Not every online decision has to become a religious SEO ceremony. If you post a casual note in several places and nobody is searching for it, this may not matter. If the piece is personal, temporary, or written mainly for existing followers, then the canonical question may be less urgent.
I know successful writers who built real careers without personal blogs, without knowing what canonical links are, and without treating every publishing decision as an SEO problem. They simply published where it made sense.
But if you want a long-term website strategy, and especially if you are trying to target search traffic, reviews, evergreen questions, or long-tail topics, I would use canonical links for reposts whenever the platform allows it.
Final verdict: canonical links are useful, but not magic
A canonical link is not a miracle.
It will not make a weak blog strong. It will not turn reposting into a traffic machine. It will not guarantee that Google chooses your preferred version. It will not solve the deeper problem of distribution, authority, trust, or attention.
But it does something important.
It lets you tell the machines where the work lives.
And for an independent writer, that is not nothing.
Because the real question is not whether you should use platforms. You probably should, at least sometimes. The real question is whether you are using them as roads or surrendering your whole house to them.
Canonical links help with that distinction.
They let the work travel without completely losing its address.
So yes, use them when you can.
Publish at home first. Let the platform versions point back. Do not expect miracles. Do not panic if Google or other search engines still make their own choices. And do not confuse distribution with ownership.
The post can travel.
But the home should still be yours.
Thanks for reading. If this review helped, you can subscribe, explore more reviews, or support the project.
