Follow one case from discovery to follow-up
A complete, accurate notice is more useful than a large batch of unreviewed URLs.
Start with the work, not the complaint
A useful takedown case starts with a specific work and a clear account of who owns or controls the relevant rights. Save the original publication URL, title, creation records, and any agreement authorizing you to act. A public page appearing after your publication is a lead, not conclusive proof of copying.
The other publisher may have a license, an independent source, or a legally permitted use. Review those possibilities before drafting a claim.
Create a short rights memo before collecting screenshots. Name the work, the relevant exclusive right, the current owner, and the document supporting any agent or employee who will sign. If ownership changed, preserve the assignment and its effective date. This memo gives the reviewer a place to resolve conflicts before personal information or allegations are sent to a provider.
Use the copyright evidence checklist to build a record another reviewer can follow.
Preserve the exact location
Record the full URL where the material appears, the date and time of observation, and the part of the page or file that reproduces your work. Keep a screenshot with context and a comparison against your original.
A domain name alone usually leaves a recipient unable to locate the disputed material. Where several URLs reproduce the same work, preserve a separate row for each one and distinguish direct copies from pages that merely discuss or link to the work.
Capture more than the visible crop. Save the page title, surrounding text, uploader or account name, direct file address when available, and a timestamp with time zone. Keep the untouched capture separately from marked-up comparisons. If the page changes later, the original capture shows what was actually reviewed instead of relying on memory or a cropped image with no context.
For case support, our managed DMCA takedown service turns exact locations into a reviewed notice packet.
Choose a recipient that can act
The site operator or hosting service may be able to disable the hosted material. A search engine can evaluate removal from search results, but that does not erase the source. A social platform has its own reporting process.
These actions can be pursued separately, with records showing which recipient received which URLs. Do not assume that a CDN, registrar, or payment processor hosts the content merely because its name appears in a technical lookup.
Test control before sending. Ask what exact action the recipient can perform and what identifier it needs to find the material. A platform may need a video URL, a host may need a page or file URL, and a search engine may need the result URL plus the source. When control is uncertain, document the lookup and ask the provider instead of copying every intermediary.
Compare hosting removal with search delisting before choosing the recipient.
Build and review the notice
Section 512 describes notice elements including identification of the work and disputed material, contact details, a signature, and required statements concerning good faith, accuracy, and authority. Our notice workspace collects these components and holds cases for review.
Check ownership, licenses, exceptions, and the recipient before approving an export. The signer must read and truthfully adopt the statements; an automatically filled form cannot establish their truth.
Review the final notice as a claim, not as a completed form. Compare every reported location with the original, remove URLs that no longer show the material, confirm that the signer recognizes the declarations, and check that the requested action matches the recipient. A second-person review is especially useful when a batch contains different works, owners, licences, or publication histories.
For cross-border cases, check when a U.S. DMCA route can still apply outside the United States.
Close the loop
Save the provider reference, submission time, response, and any follow-up. Track submitted, delisted, source removed, rejected, and disputed as different outcomes. Recheck the exact location after a response.
If a counter-notice arrives, preserve it and seek qualified advice promptly rather than repeatedly sending the same complaint. There is no universal removal deadline or guaranteed acceptance.
Verification needs a date, method, and observed state. Record whether the page returned an error, redirected, remained available, or disappeared from a particular product. Do not infer source removal from a missing search result. Schedule a proportionate recheck, retain later restoration or dispute events, and close the case only when the recorded outcome matches the claim made in reporting.
If the recipient sends one, follow the separate counter-notice process and pause routine resubmission.
DMCA case checklist
A useful case connects the owner, original work, disputed location, signer, recipient, and requested action. Keep those relationships documented from intake through follow-up.
Records to keep together
- Original and copySave the authorized source beside each exact disputed URL.
- Authority and reviewRecord who owns the right, who may sign, and which licences or exceptions were checked.
- Recipient and outcomeLog where the notice went, the reference, the response, and the verified result.
Sources & further reading
This guide draws on the primary references below. Requirements vary by recipient and jurisdiction; check the current official process before acting.
- U.S. Copyright Office - Section 512
- 17 U.S.C. § 512 - Notice and counter-notice requirements
- Google Legal Help - Report content for legal reasons
General information, not an individualized legal opinion. For a disputed claim or litigation deadline, consult qualified counsel. Read our editorial and correction policy.