A creator publishes the same piece everywhere at once.
The copies are real.
The route back is not.
More places may create more encounters. They don’t automatically create one record people can find again.
The owned page has a job the partner page doesn’t.
It gives the piece its address and its first publication date.
It gives a crawler one place to meet the work before a feed starts making copies of it.
So publish there first.
Then tell the search engines about the original, before anything else can claim to be it.
And hold the feeds shut for a day or two.
That interval isn’t a punishment for a partner.
It is the time in which the owned page becomes the first record.
Breaking work gets a shorter hold, because waiting empties it of its moment.
Long-form work can hold longer, because the owned page has work to do before a network receives anything.
Genuine emergencies override the timer entirely, which is what an override is for.
The timer serves the decision.
It is not the decision.
So don’t unlock a partner feed because the clock moved.
Unlock it when the original has actually been crawled and indexed.
Then let the feed carry only what has cleared that step.
Start the agreement before the feed, though, because a feed cannot recover a boundary nobody set.
State whether the permission is exclusive.
State the channels, the territory, and how long it lasts.
State that the headline, the body, and the author credit do not change without written consent.
A standard feed format is useful because it makes the selection repeatable.
Carry the creator, the date, and the rights record with each item, so the partner receives the context along with the words.
Then test the feed somewhere harmless before it has an audience.
Check that the metadata, the media, and the attribution link still parse on the other side.
Delivery limits belong in the same conversation. How many items, how often a partner may poll, how large an attachment may be.
Those limits don’t make a piece more valuable.
They make its delivery predictable enough that the source stays in control of it.
When the hold ends, add the asset to the live feed and let the notification go out.
The partner will apply its own layout, and that is fine. Presentation can change.
The address and the attribution cannot.
Log every handoff. Which asset, which partner, when, in what format.
The log doesn’t decide whether a partner complied.
It turns the later check into one look at one destination, rather than a search through a vague memory of where the piece went.
Because the partner page has a different job.
It should be readable where it appears.
It should not replace the place the piece belongs.
Ask the partner page to stay out of the search index while leaving its links live.
Keep a visible, unmodified link home.
Don’t let it be buried in a footer nobody will use, and don’t let the headline, body, or credit change quietly.
The point isn’t that the copy carries no links.
It is that the necessary link is unmistakable.
A readable copy and an indexable record are not the same thing, and the whole arrangement rests on keeping them apart.
The partner introduces the work to a different audience.
The source keeps the version that future links, corrections, and subscribers can return to.
Trust is useful.
Verification is what stops trust from becoming the entire system.
So crawl the partner page shortly after release.
Check the index directive. Check the link home.
If either is missing, raise it with a deadline, and let the deadline mean something — keys revoked, feeds disabled.
Then keep crawling, on a quiet weekly rhythm.
The first check catches a broken launch.
The repeat check catches a page that changed after everyone stopped looking.
And give the agreement an ending that reaches the copies.
Require real notice before non-renewal. When it ends, revoke the keys, send the removal notices, and give the partner a stated window to take the work down from live pages and public archives.
The feed is not the asset.
The partner page is not the record.
The original is the place that can hold the credit, the context, and the next connection together.
Distribution is useful when it carries people home.