Someone Copied Your Content and Appears Above You? Check the Evidence Before Responding

Finding similar text on another site can be frustrating, especially if that page appears above yours in search. Similarity alone does not establish who published first, whether a page was copied, or why a search engine selected one result. Search systems consider many signals, and a ranking difference is not proof that copying caused it.

Start by preserving the URLs, dated page captures, publication records, and the passages you believe were reused. Compare the actual content and context. A shared phrase, product specification, quote, or common definition may have legitimate explanations. Keep factual diagnosis separate from any copyright or legal determination; use the relevant platform’s process or qualified advice when needed.

Google documents canonicalization troubleshooting, spam policies that address scraping, and processes for reporting content. These routes address different issues and have different scopes. A canonical signal helps explain preferred URL selection; a spam report is not a guaranteed ranking remedy; a removal request is not the same as repairing your own site. Google: Canonicalization troubleshooting · Google Search spam policies · Google Search removal options · Google Legal Help: Copyright

Verify the overlap and the page competing in search

Record both exact URLs, query, country or market, language, device, date, and search surface. Results can vary by time, location, and context. Confirm that the other URL actually appears for the relevant query and compare the page that ranks—not just a homepage or a snippet.

Review passages side by side. Note distinctive wording, structure, diagrams, examples, images, and original data. Save dated evidence of your own source files, publication timestamp, revision history, commissioned work, and any licensing terms. A timestamp can help reconstruct sequence, but no single screenshot establishes ownership or infringement by itself.

Check for non-copying explanations: a licensed syndication, an authorized translation, a shared source, an earlier canonical URL, user-generated content, or common technical language. Also verify whether your own article is accessible, indexable, internally linked, and represented by the intended canonical URL. Do not change URLs or remove pages just because another result is visible.

Inspect canonical selection and technical signals

Check the preferred URL in your page source, redirects, sitemap, internal links, and canonical annotations. Google’s documentation explains how it may select a canonical when signals conflict; the declared canonical is a hint, not an unconditional command. Keep signals consistent and inspect the specific URL in Search Console if you have access.

Compare the two pages’ purpose, completeness, and usefulness for the query. Does yours answer the reader’s question directly, provide original examples or evidence, and explain the conditions? Does the competing page add something distinct? A ranking difference may have many causes. Improve your page because it serves the reader better, not to imitate the other page or to add bulk.

Strengthen the source record and the page’s clarity

Keep a content record with the author or responsible editor, creation and update dates, cited source material, original assets, approval status, and significant revisions. Make the publisher and author context easy to find where appropriate. Link related materials within your own site and keep the canonical and language versions accurate.

If a page has been copied at scale, inspect the affected URLs and evidence before choosing a response. Google’s spam policies describe scraping as a potential abuse pattern, but ordinary duplication or similarity does not automatically prove a policy violation. Report only what you can document. For copyright questions, use the relevant reporting route or professional advice; do not make public accusations you cannot support.

Choose the response for the actual problem

Your own signals conflict: correct internal links, sitemap entries, redirects, or canonical annotations, then recheck representative URLs.
The other page uses your protected work without permission: document the material and consult the relevant copyright process or qualified counsel. A search removal request and a source-host request have different effects.
A site appears to scrape at scale: preserve examples and consider the platform’s spam-reporting process, without assuming a report will change rankings.
Your page is weaker for the query: improve its distinct usefulness, evidence, structure, and reader path; do not copy the competing page in return.
The evidence is ambiguous: record the uncertainty and monitor, rather than escalating from a single result.

Keep a before-and-after case record

Log the query and market, affected URLs, observed overlap, page dates, Search Console observations if available, technical findings, action taken, and review date. Record the result as an observation: for example, “the page appeared for this query in this market on these dates.” Avoid claiming that a report or edit caused a ranking change unless the evidence supports that conclusion and plausible alternatives have been considered.

Field experiment thread: Monitor a source-page fix

This is a proposed monitoring plan, not a guarantee that a technical change will improve rankings.

1/ Capture the baseline: the query, market, competing URLs, your intended canonical, and the relevant Search Console status if available.

2/ Identify one supported issue on your page, such as inconsistent canonical signals or missing internal links. Do not change established URLs as part of this test.

3/ Make the scoped correction and record the date, affected pages, owner, and validation method.

4/ Verify rendered output, redirects, sitemap, internal links, and canonical consistency on the sample pages.

5/ Observe the same query and pages over a defined window, while noting other site or search changes. Separate crawling, indexing, and ranking observations.

6/ Report what changed and what remains uncertain. If no reliable conclusion is possible, extend monitoring or close the case as inconclusive.

Tool-neutral prompt pack: Organize the evidence without making accusations

Use public pages and your own source records. Do not upload confidential correspondence or customer data to an unapproved tool.

“Compare these public URLs and the supplied publication records. Identify exact overlapping passages, common phrases, unique assets, stated dates, and differences in purpose or examples. Separate observations from inferences. Do not decide legal ownership, infer intent, or claim that copying caused a ranking change. Create an evidence table with URL, passage, capture date, source record, confidence, and unresolved question. Suggest checks for canonical consistency, internal links, sitemap signals, and the relevant platform reporting route. Mark any conclusion that requires legal review.”

Verify every extracted passage against the page and source files. A similarity report is a triage aid, not a legal ruling or ranking diagnosis.

Short-video script: Do not start with an accusation

Opening: “Another page looks like yours and appears above you? Preserve evidence before reacting.”

Scene 1: Show two exact URLs and a dated capture. “Compare the same query, market, and page.”

Scene 2: Show canonical and internal-link checks. “Make sure your own preferred URL signals agree.”

Scene 3: Show an evidence table. “Similarity, policy reporting, copyright, and ranking causes are separate questions.”

Close: “Report only what you can document, fix supported issues, and monitor without promising a ranking result.”

Educational carousel: From suspicion to a checkable response

Capture context: URL, query, market, date, and search surface.
Compare the page: exact wording, assets, examples, and purpose.
Preserve your records: source files, publication history, licenses, and revisions.
Check your own site: canonical, redirects, sitemap, links, and indexability.
Separate routes: technical fix, spam report, copyright process, or reader-focused improvement.
Avoid unsupported claims: overlap alone does not prove intent or ranking causation.
Make a scoped change: document owner, date, and affected URLs.
Monitor carefully: crawling, indexing, and ranking are different observations.

Stop-doing swipe file: Replace accusations with evidence

Stop: “They copied one paragraph, so Google must rank my page first.”

Use: “We found overlap in [passages] on [URLs], captured on [dates]. The cause of the ranking difference is not established.”

Stop: “A spam report will remove the page.”

Use: “We submitted documented information through [process]. The platform decides whether it meets its policy and scope.”

Stop: “The declared canonical forces Google to use this URL.”

Use: “We aligned canonical, internal-link, redirect, and sitemap signals; we will inspect the selected canonical for the affected URL.”

Stop: “We should delete or rename our page immediately.”

Use: “We will preserve the established URL while checking supported technical issues and evidence.”

Hook–Value–Template: Report only what the record supports

Hook: “A competitor appearing above you is a symptom to investigate, not proof of why it happened.”

Value: “Separate observed overlap, technical signals, policy concerns, and ranking causes so each gets the right response.”

Template: “For [query] in [market] on [date], we observed [URL A] and [URL B]. The documented overlap is [passages/assets], captured on [dates]. Our source records show [evidence]. Our page’s technical checks found [canonical/link/indexing findings]. We [action] on [date] because [supported reason]. We have not established [uncertainties]. We will review [signals] on [date] without assuming the action guarantees a ranking change.”

Reference material and limits

These resources describe Google’s technical guidance and reporting routes. They do not establish legal ownership or guarantee how a search result will change. Seek qualified advice for legal determinations.