Domain Penalties: Detection and Recovery

What Is a Google Penalty?

“Penalty” is often used for any loss of rankings or traffic, but that wording can send an investigation in the wrong direction. A Google manual action is a documented action applied after human review. Many other losses are caused by technical changes, security incidents, removals, site migrations, changing demand, competition, content reassessment, or search-system updates.

Google’s spam policies explain that violations can be detected through automated systems and, when needed, human review. Human review may result in a manual action. The Manual Actions report identifies the issue and whether it affects pages, a section, or the wider property.

A third-party DR, DA, Spam Score, traffic graph, visibility estimate, or “penalty checker” cannot read Google’s private manual-action status. These tools can surface patterns worth investigating, but they cannot certify a domain as penalized or clean.

Five Problems Commonly Called a Penalty

Google’s traffic-drop guidance explicitly notes that search updates may change performance and that there may not be anything fundamentally wrong with the content. Diagnose before prescribing a cleanup campaign.

Confirmed Manual Actions

How to Confirm One

1. Verify the correct property in Google Search Console.
2. Open Security & Manual Actions → Manual Actions.
3. Expand every listed issue and record its wording, scope, first-known date, affected patterns, and examples.
4. Save relevant messages and establish who owned or operated the site when the violation occurred.
5. Read the policy and issue-specific corrective guidance linked from the report.

If the report shows no action, do not say “Google confirmed the domain is penalty-free.” It means no manual action is currently shown for that verified property. It does not exclude security problems, algorithmic reassessment, technical errors, legal removals, or issues outside the property scope.

Examples of Manual-Action Categories

Google’s report documents categories such as unnatural links to or from a site, site reputation abuse, scaled content abuse, cloaking or sneaky redirects, structured-data problems, thin content with little added value, user-generated spam, hacked content, and pure spam. The exact remediation depends on the category; a generic “SEO cleanup” is not enough.

Security Issues Are a Separate Emergency

Security Issues can involve hacked pages, injected spam, malware, unwanted software, phishing, or deceptive downloads. Affected pages may show search-result warnings or browser interstitials. Treat user safety and containment as the first priority—not rankings.

1. Preserve logs and evidence without browsing potentially malicious pages unsafely.
2. Restrict access, rotate credentials, remove unknown administrators, and identify the vulnerability.
3. Clean all affected files, databases, pages, accounts, scheduled tasks, and third-party integrations.
4. Patch the root cause, restore from a known-good source when appropriate, and add monitoring.
5. Test representative URLs and the wider site.
6. Request a security review only after every listed issue has been addressed.

Google warns that the example URLs in the Security Issues report are samples and may not cover every affected page. Cleaning only the examples is therefore insufficient.

Diagnose an Unconfirmed Traffic Drop

1. Define What Actually Changed

• Use verified Search Console clicks and impressions and first-party analytics where available.
• Record the exact start date, duration, affected pages, queries, countries, devices, search types, and conversions.
• Compare appropriate periods and account for weekdays, seasons, campaigns, tracking changes, and one-time events.
• Separate a loss of impressions from lower CTR, lower rankings, tracking failure, or conversion failure.

2. Rule Out Technical and Administrative Causes

• Server downtime, DNS or certificate failures, robots.txt changes, noindex, authentication, or firewall blocks
• Canonical changes, redirect mistakes, soft 404s, deleted pages, broken internal links, or sitemap errors
• Recent migrations, redesigns, JavaScript rendering changes, URL changes, or content removals
• Search Console removals, legal removals, hacked pages, and security warnings
• Analytics tag, consent, attribution, filtering, or reporting changes

Inspect representative lost pages rather than relying on a site: query or a headline index count. Our guide to checking whether a domain is deindexed explains what public observations can and cannot show.

3. Review Content, Spam Policies, Demand, and Competition

• Compare the pages that lost visibility with pages that remained stable.
• Check whether the content still satisfies the query accurately and offers original value.
• Review Google’s current spam policies for practices actually used on the site.
• Investigate changes to link schemes, doorway pages, scaled low-value content, cloaking, expired-domain use, or site reputation arrangements.
• Review the current result page, competing pages, search features, and changing intent.
• Check whether demand declined even when average position remained similar.

Aligning a traffic decline with a public update date is useful context, not proof that the update caused it. Several releases, market changes, crawl events, and search changes can overlap.

Recover From a Manual Action

1. Remediate the Specific Violation

Work from the exact issue shown in Search Console. Remove or correct the violation throughout its scope, including repeated templates and patterns not listed in the sample URLs. Address the cause that allowed it to happen.

Examples include removing hacked or spam-generated pages, securing user-generated areas, eliminating deceptive redirects, correcting misleading structured data, removing low-value scaled pages, ending improper third-party publishing arrangements, or documenting genuine link-scheme cleanup.

2. Handle Link-Related Actions Carefully

For an unnatural-links action, identify links created by the site owner, previous owner, agency, or paid campaign. Google’s manual-action guidance asks owners to make a good-faith effort to remove violating links and document the work. Do not label every unfamiliar or low-metric link toxic.

Disavow is not a routine first step. Google says most sites do not need it and warns that incorrect use may harm performance. It is intended for substantial patterns of artificial or low-quality links associated with a manual action or a likely manual action. Review our disavow guide before changing an existing file.

3. Submit a Useful Reconsideration Request

A reconsideration request asks Google to review the site after the reported problem has been fixed. Keep it factual:

• Identify the manual action and affected scope.
• Explain when and how the violation occurred, including previous ownership when relevant.
• Describe the complete corrective work and provide representative evidence.
• Explain preventive changes such as access control, publishing review, monitoring, or vendor termination.
• Disclose unresolved limitations honestly.

Do not submit while known violations remain, make ranking promises, blame Google, or repeatedly resubmit before a decision. Google states that reviews can take days or weeks and that some cases, including link-related reviews, can take longer.

Respond to Algorithmic Reassessment

There is no reconsideration request for an ordinary algorithmic traffic decline. Improve the site because the investigation found real problems—not because a “penalty detector” named an update.

• Fix crawl, rendering, canonical, internal-link, and availability problems.
• Remove or consolidate pages that exist primarily to manipulate search or add little value.
• Improve accuracy, sourcing, originality, authorship, maintenance, and the match between page and query.
• End link schemes and other practices that violate current spam policies.
• Measure meaningful page-level and business outcomes over appropriate periods.

Google must recrawl and reprocess changes, and search performance remains affected by competition and demand. There is no defensible universal recovery duration and no guarantee that prior rankings will return.

Buying a Domain With Possible Prior Problems

Before purchase, complete the domain-vetting workflow and request verified evidence where the price depends on search history.

• Ask for a supervised Search Console review of Manual Actions, Security Issues, messages, performance, indexing, removals, users, and change history.
• Document what the seller will disclose and what remains unverifiable.
• Review archived content, ownership changes, hacked paths, redirects, and the backlink profile.
• Price remediation, content replacement, security work, legal review, and the possibility of no recovery.
• Make the purchase agreement clear about included assets, representations, access, and post-sale cooperation.

If a newly acquired site has a confirmed manual action or security issue, Google’s guidance says to fix the reported problems and explain the recent acquisition and current compliance in the review request. A change of owner does not remove the need to remediate the site.

Keep an Evidence and Recovery Log

• Issue wording, scope, examples, messages, and discovery date
• Ownership, access, releases, migrations, campaigns, and vendors
• Page/query impact using verified data
• Root cause and alternative explanations considered
• Every removal, correction, security change, and outreach attempt
• Reconsideration submission, supporting evidence, response, and follow-up
• Preventive controls and responsible owner

Primary Sources

• Google Search Console: Manual Actions report
• Google Search Console: Reconsideration requests
• Google Search Console: Security Issues report
• Google Search Central: Spam policies
• Google Search Central: Debugging traffic drops
• Google Search Console: Disavow links to your site