Your traffic dropped, a chunk of your article showed up on someone else's site, or a run of one-star reviews landed on your profile in the same week. The first question you ask is whether a competitor is doing this on purpose. That question matters, because the fix for competitor scraping content is not the same as the fix for a technical problem on your own site, and treating every dip as an attack wastes time you don't have.
This piece walks through the situations that actually come up: falling search traffic with no obvious cause, a copied article, a sudden pile of odd backlinks, suspicious reviews, a compromised site, and a citation issue in an AI answer. Each section tells you what the symptom looks like, how to confirm it using a tool you already have, and what to do about it. Read the section that matches your situation. You don't need to work through all six.
Your search traffic fell, but a competitor might not be the reason
This is where to start, even if you already suspect negative SEO from competitor activity is behind it. A falling traffic chart and a competitor you don't like are not the same thing as proof, and most traffic drops trace back to something on your own site, not someone else's campaign.
What it looks like: clicks or impressions drop after a site change, a demand shift, or a search ranking update. These changes can happen at the same time you notice a scraper or a batch of new backlinks, without either one causing the drop.
How to confirm it: open Google Search Console's Performance report and compare the period where traffic fell against the period before it, and against the same period a year earlier if the topic has any seasonality. Google suggests looking back 16 months so you can see that kind of pattern. Look at clicks, impressions, and average position separately instead of treating one number as the whole story, and check which specific queries and pages moved. Then check the Page indexing and Crawl stats reports for indexing errors, the URL Inspection tool for the pages that lost traffic, and the Manual Actions and Security Issues reports for an actual notice, not just a hunch. If a demand shift seems likely, Google Trends can confirm it, and Google publishes information on ranking updates when one is suspected.
What to do: fix anything you find on your own site first, whether that's a server issue, a robots.txt mistake, a missing page, or an indexing problem. If the timing lines up with a known ranking update or a demand shift, that's your answer. Only move to the next sections once you've ruled these out. A dip in the chart next to a competitor you're suspicious of is a hypothesis, not something you can act on yet.
Someone copied your article and it's showing up in search
This is the branch for competitor scraping content specifically: your text, images, or a whole page reappear on another domain, sometimes with the byline changed or the branding swapped out.
What it looks like: before you call this scraping, rule out licensed syndication, an ordinary quote with attribution, and your own duplicate URLs. A copy showing up in search results doesn't by itself mean Google penalized your original page.
How to confirm it: write down your original page and every copy you find, along with the passages or images that match, your own publication records, and dated screenshots. Check your original in Search Console's URL Inspection tool, including the indexing status and which URL Google picked as canonical. Save your source files, CMS records, and any related correspondence before you contact anyone about taking the page down.
A canonical tag on your own page is a hint to Google about which version to treat as the original, not a rule, and Google can pick a different URL. That also means a canonical tag on your page does nothing to control a page a scraper publishes on their own domain. Google's spam policy names scraping directly: taking material from other sites and republishing it to manipulate rankings, especially when it adds no original value or stitches together copied pieces. That description doesn't mean every duplicate you find gets penalized automatically.
What to do: if the copy is unauthorized and reproduces a meaningful amount of your work, contact the publisher or their hosting provider directly with your original, the offending page, and a specific description of what was copied. For the version appearing in Google Search, use Google's copyright reporting process when the situation genuinely involves a copyright claim, not just similar wording or a licensed reuse. A Search removal takes the page out of Google's results. It does not remove the material from the host, from other search engines, or from anywhere else it might be published, so don't tell your team the problem is fully solved once that one removal goes through. If the copied page is also built to manipulate rankings, Google has a separate spam-reporting route for that, distinct from the copyright process. For repeated copying or anything with real financial stakes, bring in counsel rather than handling it alone.
A cluster of suspicious backlinks shows up
This is the branch people usually mean when they ask whether a competitor doing shady SEO is behind it: a sudden pile of low-quality or irrelevant links pointing at your site, often with strange anchor text.
What it looks like: many new links appear at once from pages that have nothing to do with your topic, or the anchor text follows a pattern that looks manufactured. A high link count on its own, a "toxic" label from a third-party tool, or suspicious timing does not establish that a competitor built those links or that Google has penalized you for them.
How to confirm it: look at where the links actually point and where they come from, and check whether there's a coherent pattern rather than noise. Line up the timing against your Search Console Performance report. Most importantly, check the Manual Actions report for an actual unnatural-links notice before you describe this as a penalty, because a rising risk score from a third-party tool is not the same thing as a notice from Google. Save representative examples of the links and any evidence that someone solicited or built them deliberately. If rankings dropped around the same time, run through the ordinary explanations in the first section before assuming this is the cause.
What to do: Google's disavow tool is meant for sites that have an unnatural-links manual action, or a real reason to expect one because of paid links or another scheme that breaks its policies. Google's own guidance is to try removing the problematic links at the source first. If disavowal is warranted, use the tool carefully and for the specific property affected, since an uploaded list applies to that property and anything under it, and separate HTTP and HTTPS versions of a site are sometimes handled separately. Don't disavow every domain you don't recognize, and don't hire a link-cleanup service just because a risk score went up. If Google did issue a manual action, work through its specific review process rather than assuming an uploaded disavow file automatically clears things.
Suspicious negative reviews start appearing
Sometimes the symptom isn't traffic at all. It's a run of one-star reviews describing an interaction nobody on your team recognizes.
What it looks like: the reviews describe something your team can't match to a real customer, use strangely similar wording to each other, arrive in a tight cluster, or come with a demand for payment attached. These details are worth investigating, but they are clues, not proof that the reviewer is fake or that a competitor is behind them. A genuinely unhappy customer can also be anonymous to your marketing team.
How to confirm it: look at each review on your Google Business Profile individually. Save the text, the date, how the reviewer is displayed, and any messages connected to it. Compare specific factual claims in the review against your own records, without publishing anything about the customer publicly. The useful question isn't just "is this negative," it's which specific policy the review might violate, because Google only removes reviews that break its stated policies, not reviews that are simply unflattering.
What to do: report the specific review through Google Business Profile's inappropriate-review process and include the relevant facts. Don't promise your team a removal or a timeline, since that isn't something you control. While the report is pending, a measured public reply that acknowledges the concern and points the writer toward a private support channel is usually the right move, without disclosing account details or asserting the review is fake. Never buy counter-reviews, offer compensation for changing a review, or ask employees to post experiences they didn't have. If a message threatens a wave of negative reviews unless you pay, save the demand and report it through Google's dedicated process for negative-review extortion, giving as much detail as you can. Treat a credible threat like that as something to escalate to legal or security, not something to handle over email alone.
On the regulatory side, the Federal Trade Commission announced its final rule on fake reviews and testimonials on August 14, 2024, which addresses creating or selling reviews that misrepresent a reviewer's real experience, certain purchases of fake reviews, and some forms of review suppression. That's useful context for understanding what the FTC considers out of bounds. It isn't a guarantee that any specific review you're disputing falls under the rule, and it doesn't replace a platform report or legal advice for your situation.
Your site shows security warnings or content you didn't publish
What it looks like: unexpected pages, redirects you didn't set up, a browser security warning, or a broad traffic change that doesn't fit the copied-article or backlink pattern. Don't label this a competitor's negative SEO campaign without evidence pointing at who actually did it, because the more common explanation is a compromised site, not sabotage.
How to confirm it: check Search Console's Security Issues, Manual Actions, Page indexing, and Crawl stats reports, and look at the affected URLs alongside your own site-change history. Google notes that security problems like malware or phishing can trigger warnings before a visitor even reaches your site, which cuts off search traffic before rankings are even a factor.
What to do: treat a confirmed compromise as a security incident, not an SEO problem. Preserve what you find, bring in your site administrator or security team, remove any unauthorized changes, and follow the review process for the platform involved. A copyright complaint or a disavow file won't fix a hacked site, so don't spend time on those while the actual vulnerability is still open.
An AI answer cites a questionable page about you
This is a shorter branch, and it comes up less often than the others: an AI platform's answer repeats something false or points to a source that looks off.
What it looks like: an AI tool answers a question about your brand or product using a claim that isn't accurate, or it cites a page that looks unreliable or unfamiliar. Save the exact prompt, the answer text, the cited page, the platform, and the date you saw it. The fact that a competitor's page turns up in an AI answer doesn't by itself prove manipulation or a lasting loss of visibility for you.
How to confirm it: open the cited page and check where its information actually came from before assuming bad intent. If it turns out to be a copied page, treat it with the copyright branch above. If it looks like deceptive search spam, use the relevant platform's reporting route. If it's simply a false factual claim, ask the publisher for a correction and use whatever feedback mechanism the AI platform offers. This is a case where a tool like DeepSmith's AI visibility tracking is useful for spotting the pattern early, since it shows which pages AI engines are citing for your brand's prompts over time, but seeing a shift in citations is an observation, not evidence of wrongdoing on its own.
What to do: don't promise anyone that removing one page will change an AI answer right away. Answering platforms describe their citation measurements as observational rather than a ranking or quality signal, and they note that citation patterns shift with the underlying model, how fresh the content is, and how the web itself changes. Treat this as a signal to investigate the specific claim or page, not a standing program to monitor competitors day to day.
When none of these match
Sometimes you check every branch and nothing quite fits, or you find a mix of small things that don't add up to a clear story. That's a legitimate outcome, not a failure to find the right answer.
Build a short incident record instead: the symptom and the affected page or profile, the date you first noticed it, the original and offending locations, any screenshots or records you saved, what Search Console showed, which platform policy (if any) seems relevant, and what you've reported so far along with any responses. From there, bring in a technical SEO specialist for indexing or ranking questions you can't resolve yourself, your security team for anything that looks like a compromise, and qualified counsel for infringement, defamation, extortion, or a contested copyright claim. "We don't know who did this yet" is a fine place to land. Revisit the record when a platform notice, a host response, or new evidence comes in, rather than guessing at an answer now.
If you're tracking how your brand shows up across AI answers as part of your regular reporting, keeping that watch running makes it easier to notice a real citation shift instead of reacting to normal week to week variation.
