If another site copies your website content, identify the work you control, match it to the specific copied pages, and use Google's legal reporting tool for the product where the material appears. Explain the copying precisely and complete the applicable declarations truthfully. A request to remove a Google Search result does not remove the third-party website itself.
For a large collection of scraped articles, the practical challenge is keeping each work, reported URL and outcome connected. Start with a reliable comparison record rather than submitting a homepage and asking Google to find every copy. The workflow below covers evidence preparation and request tracking; disputed ownership, permitted use and litigation decisions require advice appropriate to the case and jurisdiction.
First check what you own and what was actually copied
Being the site operator does not by itself establish ownership of everything on the site. Check employment or commissioning arrangements, assignments, licences and any authority to act for the rights holder. If you use licensed photographs or syndicated articles, identify which rights you have before claiming ownership of those works.
A similar topic, factual statement or negative opinion is not enough to establish copyright infringement. Compare the actual expression or material used, the extent of the copying and any applicable permission or legal exception, including fair use where relevant. A licence may have limits on time, territory or use: neither “it once had permission” nor “it forgot a link” settles the issue on its own.
The U.S. Copyright Office's section 512 resources explain the notice-and-takedown system and its safeguards. If the real issue is impersonation, privacy or a disputed factual statement, choose an applicable reporting ground rather than converting it into a copyright claim without a basis.
Build a work-to-URL comparison record
Use one record for each clearly identified work and reported location. If one page contains several works, or one work appears on several pages, preserve those relationships. Grouping in a spreadsheet helps you prepare accurate submissions; it does not establish the current form's limits or guarantee that a whole domain will be removed.
| Record | What to save | What it establishes |
|---|---|---|
| Work and authority | Title or identifier, original file or URL, rights holder and relevant authority | What you claim and why you can act; review the underlying rights documents |
| Reported location | Exact page or file URL, redirects, access time and relevant passage | Where the material was observed; a homepage alone may not locate it |
| Comparison | Matching passages or image details, surrounding context and explanation | The specific copying alleged, not just a similarity score |
| Request and outcome | Product, submitted version, reference number, replies and per-URL status | What was sent and what happened; receipt is not approval |

For example, suppose your own installation guide contains a distinctive diagram and an explanatory paragraph. A reported page reproduces the diagram but rewrites the paragraph. Identify the diagram and its location precisely, and assess the paragraph separately. Do not describe the entire page as a verbatim copy when your comparison only supports a claim about the diagram.
Keep dated source files, publication records and contextual screenshots where available. A canonical tag pointing to your page, a database timestamp, a server log or a sitemap date may be supporting information, but none alone proves authorship or makes a record impossible to alter. A file hash can help check that a saved file has not changed since you recorded that hash; it does not establish who created the work or when it was first published.
Search can help discover possible copies. However, Google's site: operator documentation says results are not necessarily exhaustive. Record the actual URLs you find; do not claim that a query has located every copy or that an absent result proves a page was removed.
Choose the Google product that actually contains the material
Start with Google's content reporting selector. Choose the relevant product and the reason that matches the facts. For a third-party page appearing in search, the request concerns the search result. For material hosted on Blogger, choose the applicable Blogger route, not Google Play. Content on several Google products requires separate reports through the appropriate product paths.
Google's legal reporting instructions ask for specific content URLs and a clear explanation of what is objectionable and why. Follow the current form's instructions on grouping works, attachments and required fields. Do not rely on an assumed universal URL limit, character limit, button label or review time.
If you also want the third-party source removed, that is a separate task. Google notes that removal from its products does not erase material from the original site. Consider an appropriate request to the site operator or hosting provider, using its actual process and contact details. Keep those requests separate from the Google case record.
Prepare the notice carefully before signing
17 U.S.C. §512(c)(3)(A) describes the elements of an effective notification under that subsection. In practical terms, check the following against the applicable form:
- A physical or electronic signature from someone authorized to act for the owner of the exclusive right allegedly infringed.
- Identification of the copyrighted work; for multiple works at a single online site covered by one notice, the statute provides for a representative list of those works.
- Identification of the material to be removed or disabled and information reasonably sufficient to locate it.
- Information reasonably sufficient to contact the complaining party, such as an address, telephone number and, if available, an email address.
- A good-faith statement that the complained-of use is not authorized by the copyright owner, its agent or the law.
- A statement that the information is accurate and, under penalty of perjury, that the complaining party is authorized to act for the owner of the exclusive right allegedly infringed.
Section 512(d)(3), addressing information location tools, refers to these notice requirements but specifies identification and location of the reference or link to be removed in place of the material-identification requirement in §512(c)(3)(A)(iii). This is another reason to identify the particular search reference and destination, not merely name the suspected site.
Explain the relationship in plain language: identify your work, point to the reported location and describe the particular material alleged to have been copied. Supply the declarations required by the actual form after checking that you can make them. Under §512(f), knowingly making material misrepresentations can lead to liability for resulting injury when the provider relies on them; disagreement or an unsuccessful notice alone is not the same finding.
Check what may become public
Google's About Lumen explanation says it shares certain legal notices with the independent Lumen project. For copyright and trademark requests, the information generally shared includes the requester's name, rights holder's name, reported URLs, country, request date, explanation, attachments and quoted allegedly infringing content.
Google distinguishes contact information fields it does not share from other submitted material. Do not assume a home address placed in an explanation or a confidential document attached to the notice will remain private. Review free text, screenshots and files for unrelated personal or confidential information, while still supplying what the actual process requires.
Do not place account passwords, session cookies or private access tokens in a complaint explanation. If material cannot be viewed publicly, follow the channel's instructions for supplying it or ask what evidence is accepted. Publishing a private folder for convenience or allowing an unverified IP address is not a required step in the documented workflow.
Track replies and verify each outcome
Google says you will receive an email confirmation and reference number after filing a request. Save both with the version you submitted, and check for requests for additional information. If the form reports an error and you have no confirmation, record the submission as unconfirmed rather than assuming it succeeded.
Keep statuses such as submitted, needs more information, declined, removal reported and independently checked distinct. A response can cover only some URLs. Match it back to the reported locations and preserve the stated scope. If a request is declined, read the reason before correcting or adding material through the applicable process; repeatedly sending an unchanged allegation does not resolve a missing fact.
Verify the affected Google result and the original page separately, noting the query, product, date and observed result. A failed fetch is not proof of removal, and one search without a result does not establish global disappearance. Save later copies or new URLs as new observations rather than silently replacing the original record.
What if a counter-notification arrives?
A counter-notification is not just an informal objection. Section 512(g)(3) specifies a signed communication identifying the removed material and former location, a good-faith statement under penalty of perjury that removal resulted from mistake or misidentification, and the subscriber's name, address and telephone number. It also requires consent to the specified U.S. federal court jurisdiction and acceptance of service of process. Read the actual notice and obtain suitable legal advice before responding or making these declarations yourself.
The often-quoted restoration window has conditions. In the subscriber-hosted-material circumstances described in §512(g)(2), following a notice under §512(c)(1)(C), the provision sets out notification steps and replacement not less than 10 and not more than 14 business days after the service provider receives the counter-notice. The exception is that its designated agent first receives notice from the original notifier that an action seeking a court order to restrain the relevant infringing activity has been filed.
This statutory safe-harbor provision is not a universal promise that every Google Search URL will return on a particular day. Nor does it mean every complainant must sue within ten calendar days of receiving an email. The service, facts, notice and applicable process matter. If litigation may be involved, promptly have the actual dates and requirements reviewed; a threat to sue is not the same as notice that the specified action has been filed.
Keep copyright handling separate from SEO results
Removing an infringing result does not guarantee that your original page will be indexed, regain a ranking or receive more traffic. Continue to maintain accurate publication records, accessible original pages and clear internal links. For ongoing website work, the Guangsuan SEO service page (Chinese) explains the service scope; a copyright dispute and any legal representation need their own arrangements.
The useful completion record is specific: which works and URLs were reported, what each channel decided, what was independently observed and what remains unresolved. It is more actionable than a claimed success percentage with no underlying cases or a guaranteed processing time.