Take back control.

Protection solutionsDMCA takedown serviceGoogle copyright removal serviceCopyright monitoring servicePublisher anti-piracy serviceCopyright protection for creatorsImage licensing & attribution serviceSoftware piracy takedown service
Knowledge hubCopyright protection guidesCopyright essentialsTakedown field guidesContent protection
Company & standardsAbout LINK-BUSTERFees & service scopeResponsible enforcementContact

Independent copyright protection.
Hong Kong · United States

How to prepare a Google copyright removal request

Prepare a Google copyright removal request with exact source and result URLs, authority records, disclosure checks, response handling, and verified outcomes.

An original framed artwork standing clearly above several subdued duplicate search-result panels Conceptual imagery generated with OpenAI. Not documentary evidence.

Build a work-to-URL request worksheet

Prepare the case outside the form first. Each row should let a reviewer connect one protected work, one reported location, the authority to act, and the result Google communicates.

Fields for each request row

Work and authority

Name the work, official source, rights holder, signer, and document authorizing an agent.

Reported location and comparison

Save the exact page or file URL, observation date, reproduced portion, and relevant licence or exception check.

Submission and outcome

Attach the Google reference, response, clarification history, observed Search status, and separate source-page status.

Complete the request in six passes

A strong Google request maps one identifiable work to exact URLs, supports the signer’s authority, and records Google’s decision separately from the status of the source page.

Choose the Google product and legal basis

Start in Google’s Legal Help Center and select the product where the material appears. A result in Google Search, a YouTube upload, and a file in another Google product are not one reporting target. Google asks for a separate request for each relevant product because different teams, identifiers, and remedies may apply.

Choose copyright only when the complaint concerns protected expression and the claimant controls the relevant right. Trademark, privacy, court-order, and product-policy complaints follow different routes and require different facts. A legal request should explain why the identified content is allegedly infringing rather than treating an unwanted or critical page as a copyright violation.

Map the original work to each exact URL

Build a work-to-URL table before opening the form. One column should identify the protected work and an official or otherwise verifiable source. Another should contain each exact page, image, or file URL that Google should assess. A domain homepage or a search-results page usually does not identify the material precisely enough. Add a short comparison explaining what appears at that location and which part of the original it reproduces.

For example, a photographer reporting two pages should create two rows, even when both pages show the same photograph. Each row can point to the same original publication but should preserve its own disputed page URL, direct image URL where available, observation date, crop or alteration notes, and licence check. This structure lets one URL be clarified, declined, withdrawn, or verified without changing the record for the other URL.

Confirm the claimant and authority to act

Record the legal person or entity that owns or controls the relevant copyright. If a reporting organization, employee, or other agent submits the request, keep written authority that connects that submitter to the owner and the works in the request. An invoice for a copy, a general job title, or access to a website account does not by itself establish copyright ownership or enforcement authority.

Read the declarations in the current form before anyone signs. Google’s copyright process requires a good-faith belief that the reported use is not authorized by the owner, its agent, or the law, along with confirmation that the submitter is authorized to represent the owner. Check licences, assignments, fair use or other exceptions, and mistaken identity before making those statements.

Review disclosure and data before submission

Use the minimum information needed to identify the claimant, work, location, and basis of the request. Do not attach unrelated customer records, account credentials, unredacted identity documents, or private material merely because the form permits supporting information. Store the submitted version with the case so a later reviewer can see exactly what Google received.

Google explains that qualifying copyright requests may be reflected in its transparency processes and may be shared with Lumen when legally possible. The current form and privacy notices control what is collected and disclosed, so review them at the time of submission. If an example contains confidential material, describe the work accurately and seek an appropriate protected route rather than publishing the material as evidence.

Handle confirmations and requests for clarification

After submission, save the confirmation email and reference number against the exact batch of URLs. Monitor the contact address used in the request. Google may ask for missing URLs, a clearer work description, authority information, or a more specific explanation of the alleged infringement. Answer against the saved request instead of creating an unconnected duplicate case.

A declined URL is not proof that the entire rights claim failed. Google lists reasons that can include insufficient information, inability to locate the referenced material, apparent misuse of the copyright process, or a fair-use concern. Record the reason per URL, correct factual omissions where possible, and pause for legal review when the response raises a substantive dispute.

Verify delisting separately from source removal

Google Search can restrict access to a result in its own product; it does not remove the page from the website that hosts it. After a decision, check the exact result and the source URL separately. Record accepted, declined, pending, counter-notified, reinstated, and withdrawn states without converting an unavailable page into a confirmed Google delisting.

Keep later events in the same history. A site owner may challenge a removal, and an original complainant may retract a mistaken request. If source removal is also justified, identify the website operator or hosting route as a separate action with its own notice, reference, response, and verification. This distinction is central to our guide on hosting removal versus search delisting.

Sources & further reading

This guide draws on the primary references below. Requirements vary by recipient and jurisdiction; check the current official process before acting.

General information, not an individualized legal opinion. For a disputed claim or litigation deadline, consult qualified counsel. Read our editorial and correction policy.

More from takedown field guides

The DMCA takedown guide: from discovery to follow-up

Follow the DMCA takedown process from evidence and authority checks through notice preparation, recipient submission, disputes, and verified outcomes.

Read guide

Copyright evidence checklist for a defensible takedown

Use this copyright evidence checklist to preserve originals, copied locations, timestamps, authority, context, and a review another person can verify.

Read guide

DMCA counter-notice: what happens next?

Learn what a DMCA counter-notice means, which records to preserve, when to pause repeat enforcement, and when a dispute needs legal advice.

Read guide

Ready to protect
what you created?

Choose ongoing monitoring, help with a specific infringement, or an attribution and licensing assessment.

Choose a service