A copyright complaint to Google will not take the stolen copy of your post off the internet. Google's own policy on copyright removals is blunt about it: the company removes or disables access through its own services, and the page keeps sitting on the site that copied you, live, for anyone with the link.

That one fact reorders the whole job. Delisting is the last step, not the first, and people who start there spend a week feeling productive while the copy stays up. Here is the sequence that actually gets a page pulled down, in the order that wastes the least of your time.

Document the copy before it moves

Scraper sites are unstable. Pages get rewritten, domains lapse, whole directories vanish when a host suspends an account. If the evidence lives only in your browser tab, it can evaporate before you have finished deciding what to do about it.

Two minutes of work fixes that. Save the infringing page to the Wayback Machine's Save Page Now, which gives you a timestamped third-party record you did not create yourself. Take a screenshot that shows the full URL and the date. Write down the exact URL of the copy, not the homepage, because every removal process you are about to use asks for the specific page.

Then note your own provenance: your original publish date, and, if your CMS keeps revision history, the fact that it exists. You will probably never need it. It costs nothing now and is impossible to reconstruct later.

Find every copy, not just the one you spotted

You almost never find these on purpose. Someone emails you, or a strange referrer shows up in analytics, and you discover one copy. There are usually more, because the same aggregators tend to hit the same sources repeatedly.

The cheapest sweep is an exact-phrase search. Pull a distinctive sentence from the middle of your post, eight to twelve words, something you would never expect to see written by anyone else, and search it inside quotation marks. Use the middle rather than the intro: intros get rewritten, body paragraphs get pasted. Do it for three or four sentences from different sections, since partial lifts are common.

For a wider net, run the whole post through a checker instead of one sentence at a time. Two practical notes if you do. First, your own site will match itself, so put your domain in the exclude-URLs setting before you scan, or half the report will be you. PlagiarismCheck.io has that setting in the scan options, along with an ignore-common-phrases toggle that strips out the boilerplate every blog shares. Second, the 2,000-word cap means a long post needs splitting into two scans.

Exact-phrase searching misses the worst offenders, though. Plenty of scrapers run your text through a rewriter first, and a synonym-swapped version will never surface in a quoted search. That is where a checker's paraphrase detection earns its keep, and also where you should temper your expectations: a heavy rewrite can slip past text matching entirely.

For what it is worth, this is not a grey area to Google. Its spam policies name scraping directly, and the examples include republishing someone's content with no original material and no credit, and copying content while changing only a few words through synonyms or automation.

Start with an email, not a legal notice

Before you accuse anyone, be sure of what you are looking at. Some overlap is innocent: shared boilerplate, an excerpt quoted properly with a link back, a syndication deal you agreed to two years ago and forgot. Checkers surface plenty of matches that turn out to be nothing at all, and firing off a takedown at one of those is a bad look you cannot take back.

Once you are sure, a plain email to the site owner resolves more of these than people expect, and it moves faster than any host's abuse queue. Keep it short and unemotional. Identify your post and the copy by URL, state that you did not license the text, and ask for removal by a specific date. A week is a normal window.

Contact details are usually on a contact or author page. When there is nothing, ICANN Lookup gives you the registrar and the nameservers for the domain, and the nameservers are your first clue about who is hosting it. If nobody answers within your stated window, stop emailing and escalate.

Send the DMCA notice to the host, not the thief

The leverage is not with the person who copied you. It is with the company whose legal safe harbor depends on acting when it receives a valid notice, which means the hosting provider.

Finding it takes a minute. The nameservers from your lookup often name the host outright. Many sites sit behind Cloudflare, which complicates this only briefly: Cloudflare is a pass-through service and says on its abuse approach page that "we cannot remove content from the Internet that we do not host," and that it forwards complaints to the website operator and the hosting provider. So a notice sent there still moves, it just arrives at the host with an extra hop. To go direct, search the host in the US Copyright Office's public DMCA designated agent directory, which is where providers are required to register a contact for exactly this.

A notice has to contain six things to be valid under section 512:

Your physical or electronic signature
Identification of the copyrighted work being infringed
Identification of the infringing material, with enough detail to locate it
Your contact information
A statement that you believe in good faith the use is not authorized
A statement, under penalty of perjury, that the information is accurate and you are authorized to act for the copyright owner

You do not need a registered copyright to send this. Under the Copyright Office's own FAQ, your work is protected the moment it is created and fixed in tangible form, which for a blog post is the moment you hit publish.

Take the perjury line seriously, and the good-faith one too. Google's policy page warns that filers are liable for damages, including costs and legal fees, for a material misrepresentation, and points to a case where a company paid over $100,000. Do not send a notice over a properly attributed short excerpt, or over content you licensed and forgot about.

Then ask Google to delist the copy

Now the delisting step makes sense as what it is. It does not remove the page. It removes the page's ability to outrank you for your own words, which for most bloggers was the actual injury.

Google's copyright removal request form wants the exact infringing URLs and the location of your original. The turnaround is quicker than people assume: Google's help center puts the average processing time across all removal requests submitted via the web form for Search at roughly six hours.

One thing to know before you file. Google forwards these notices to Lumen, which publishes them after stripping certain personal information, and the delisted result in the search page gets replaced with a link to the published notice. Your name and the URLs involved become a public record. If you run your blog under your own name from your own address, use a business address in the form.

If they file a counter-notice

The person you targeted can push back. A counter-notice needs their signature, identification of what was removed and where it appeared, a statement under penalty of perjury that the removal was a mistake or misidentification, contact information, and consent to federal jurisdiction.

What follows is the part worth knowing in advance. Once a valid counter-notice arrives, the provider restores access in "not less than ten, nor more than fourteen, business days" unless you tell it you have filed a lawsuit. That is the whole mechanism. The notice-and-takedown system is not a court, and it hands the decision back to you.

Suing is a real decision with real prerequisites. For a US work you have to register the copyright before you can file an infringement suit. And under 17 U.S.C. section 412, statutory damages and attorney's fees are off the table for infringement that began after publication and before your registration took effect, unless you registered within three months of first publishing. Register a two-year-old post today and you are litigating for actual damages, which on a scraped blog article are usually not worth the filing fee.

That is not a reason to skip the notice. It is a reason to know where your leverage ends before you write a threat you have no intention of carrying out.

What this looks like on a normal week

Most copies never get past step three. You email the site owner, they pull the page or add a canonical link back, and it is done in a day. The next largest group dies at the host, quietly, without anyone replying to you. The counter-notice branch is rare on scraped blog content, because the people running those sites are running dozens of them and have no interest in a fight over one article.

The habit worth building is the sweep, not the takedown. Every quarter, take two or three sentences from your best-performing posts and run the quoted search. It takes ten minutes and it catches copies while they are still new, which is when a delisting request is worth the most to you.

If you would rather check a whole post at once than sentence by sentence, PlagiarismCheck.io is free, needs no account, and gives you clickable source links for every match, so you can go straight from the report to the page that copied you.