Canonical tags shift duplicate content risk—here's when
The office hum outside your window drops off mid-afternoon. Your laptop screen throws pale blue light across an empty coffee cup. Somewhere in your draft folder, three versions of the same post wait for their second life on Medium, LinkedIn, or both.
Canonical tags tell Google which version to rank—but timing matters more than you think
Republishing content can double your reach or split your ranking power—canonical signals decide which.
You wrote a strong post. It ranks. Now you want to syndicate it to Medium or LinkedIn to reach their built-in audiences. The conventional wisdom says “add a canonical tag and you’re safe”—but Google’s handling of duplicate content depends on three variables most operators skip: whether the canonical tag is present before Google crawls the syndicated version, how much time passes between your original publish and the republish, and whether the platform actually respects your canonical directive.
Medium honors canonical tags and lets you set them during import. LinkedIn does not offer canonical support at all—so every LinkedIn article you publish is treated as original content by Google, regardless of where you published first. If LinkedIn’s version gets indexed before yours, or if it attracts more inbound links, Google may rank it above your own site. The fix isn’t to avoid LinkedIn—it’s to let your original post get indexed and start accumulating signals for at least 48 hours before you syndicate. For Medium, set the canonical on import and check the HTML source to confirm it points to your domain, not Medium’s. For LinkedIn, treat it as a summary or excerpt with a link back to the full post, not a verbatim republish.
Timing, canonical implementation, and platform behavior combine to determine whether syndication expands reach or fragments it. The mechanics aren’t intuitive, but they’re consistent once you map them.
TACTIC
When multiple pages target the same keyword, Google picks one—and it might not be yours
You published a guide to email deliverability in 2023. This year you wrote a new version with updated examples. Now both rank for the same query, and neither holds position one. This is keyword cannibalization: your own pages compete, and Google distributes authority between them instead of concentrating it. The fix is to consolidate—redirect the weaker page to the stronger one, or rewrite one to target a adjacent keyword. Most operators spot cannibalization only after traffic drops. The better move is to audit before you publish the second piece.
WORTH READING
Social embeds pull from different API buckets than your timeline—and they break differently
You embedded an Instagram post in your newsletter archive. It rendered fine for weeks. This morning it shows a grey box. The culprit isn’t your embed code—it’s Instagram’s rate limit for embed requests, which is separate from the limit on timeline or profile requests. Most platforms assign different quotas to different API endpoints, and embeds often sit in the lowest tier. When you hit the cap, embeds fail while your own authenticated requests keep working. The fix is to cache embed HTML or switch to static screenshots for high-traffic pages.
FROM THE ARCHIVE
Stripe checkout links expire after 24 hours—here’s what happens when customers return late
You send a payment link to a client. They open it two days later and see an error. Stripe checkout sessions expire by default after 24 hours—not when the customer pays, but from the moment you create the session. If you generate links in advance or send them via slow email threads, customers hit dead links. The session doesn’t auto-renew; you have to create a new one. You can extend the expiration window to 30 days by adjusting session parameters, but most operators don’t know the setting exists. The default is silent—it just fails.
Know someone who would like this? Forward today’s email — every operator we reach is one closer to running an online business with a little less friction.