Claim and evidence
Let others embed your content on their sites; the player carries the platform and sends viewers back.
No dated example yet. Treat this tactic as a hypothesis.
Primary
The company or founder describes the tactic and its result themselves: own blog, talk, filing.
Working · 2026-11 Docs describe features, no growth data; inference of loop value is the harvester's.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
Embeds put your product inside other publishers' pages; docs show viewer paths back to the host in blocked states.
How to run it
- Provide embed code in share menu
- Allow privacy mode
- Keep a path back to the host platform
- Offer uploader controls
Before / after
Generalised wireframe of the pattern, not a copy of any company's screen.
Ways to run it
Design options to test, not promised results.
- Option AEmbed code in the share menu
Put copy-ready embed code next to the link so publishers can place the player in one step.
- Option BPrivacy mode
Offer an embed option that limits tracking, so privacy-minded sites can still use it.
- Option CUploader controls
Let creators turn embedding off for their content, as YouTube does.
- Option DPath back to the host
When content cannot play in the embed, send viewers to watch it on the platform itself.
Dated examples
- —
Does it still work?
Docs describe features, no growth data; inference of loop value is the harvester's. source
Risks
- No numbers
- Referrer requirements can break playback
Sources
- support.google.com
“Age-restricted videos can’t be watched on most 3rd party websites.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (referral-loops)