Most "penalties" aren't penalties
The call always sounds the same. Traffic fell off a cliff, revenue followed, and by the time we're on the phone the word "penalty" has been repeated enough times that everyone assumes it's established fact.
It usually isn't. Actual manual actions — a human reviewer at Google deciding your site breaks the spam policies — are comparatively rare, and they announce themselves in a specific place in Search Console. The far more common causes are an algorithmic reassessment during a core update, or something your own team shipped without noticing.
This distinction is not academic. A manual action needs a documented clean-up and a reconsideration request. A core update loss needs months of content and authority work with no submit button anywhere. An accidental noindex needs a one-line fix and a re-crawl. Sell the wrong one and you've spent six months and several lakh solving a problem you didn't have.
The triage: three causes, and how to tell them apart in an hour
The shape of the drop tells you most of what you need. A cliff on a single day is almost never an algorithm — algorithms roll out over days or weeks. A cliff is usually something that was deployed.
| What you're seeing | Most likely cause | How to confirm |
|---|---|---|
| Vertical drop on one date, whole site, impressions gone too | Self-inflicted: noindex shipped, robots.txt disallow, canonical pointing off-site, firewall or WAF blocking Googlebot, expired DNS or certificate | URL Inspection with a live test, plus robots.txt, response headers and your CDN's bot rules. Logs will show Googlebot getting 403s or nothing at all. |
| Gradual slide over one to three weeks, uneven across sections, impressions down but pages still indexed | Algorithmic — a core update or a spam-system reassessment | Line the dates up against Google's published core update log, and check whether the loss sits in one content type. Rankings drop; indexing stays healthy. |
| Specific pages or the whole domain gone from branded search, message in Search Console | Manual action | The manual actions panel names the issue and the scope. That's the only place it exists. |
| Sessions down but Search Console impressions and clicks flat | Not a search problem at all — broken analytics, a consent banner change, or a tag manager release | Compare GA4 against Search Console clicks for the same period. If Search Console is fine, the traffic never left. |
The ₹99,000 diagnosis, and when we turn the job down
One fixed fee, ex-GST, no retainer attached. Ten working days. You get a written diagnosis with the evidence attached, a fix plan with owners and effort estimates, and an honest probability of recovery.
The fee is the same whether the answer takes us three hours or ten days, and sometimes it takes three hours. We considered pricing it lower for the easy cases and decided against it, because a diagnosis priced by difficulty pays us to find something complicated.
- What's in it. Manual action review, crawl and index audit, log analysis where logs exist, backlink profile review, content assessment of the affected sections, update-date correlation, and a written verdict.
- What you can do with it. Anything. Hand it to your in-house team, your developer, or another agency. We don't withhold the fix plan to force a retainer.
- Credited back. If you start an SEO retainer with us within 60 days, the full ₹99,000 comes off the first invoice.
- When we refuse. If the diagnosis shows the traffic was built on expired-domain abuse, a private blog network, scaled low-quality content, or parasite pages on someone else's domain, we say so and stop. Those aren't recovery projects — the thing Google removed is the thing the business was doing. We'll tell you what a legitimate rebuild would cost, and it's usually more than starting fresh.
What's included, and what isn't
Recovery work splits into diagnosis and treatment. They're priced separately for a reason — plenty of clients only need the first.
| Area | In scope | Not in scope |
|---|---|---|
| Diagnosis (₹99,000 fixed) | Manual action review, crawl and index audit, log analysis, backlink profile review, content assessment, update correlation, written verdict and fix plan | Implementation. The diagnosis tells you what to do; doing it is a separate decision. |
| Manual action work | Documented clean-up, link removal outreach and disavow file, evidence pack, drafting and submitting the reconsideration request, handling follow-up rounds | Any promise about Google's decision or its timing. We don't control the reviewer or the queue. |
| Algorithmic recovery | Content quality remediation, thin and duplicate page consolidation, E-E-A-T evidence, internal linking rebuild, technical clean-up — inside a normal retainer | A dated recovery promise. Reassessment happens on Google's schedule, not on our invoice cycle. |
| Self-inflicted faults | The fix itself, re-crawl and re-index verification, plus a written post-mortem on how it shipped so it doesn't ship twice | Nothing withheld here. These are usually quick, and we'll often close them inside the diagnosis fee. |
| Ongoing growth | Available as a normal SEO retainer once the site is stable | Bundled into recovery pricing to make the invoice look better. Recovery and growth are different jobs. |
Reconsideration requests, and what the timeline really looks like
A reconsideration request only exists if there's a manual action. There is none for a core update loss, whatever a proposal tells you, because there's nothing for a human to reconsider.
Where one does apply, the request is the easy part. The clean-up before it is the work, and a request submitted before the clean-up is genuinely finished gets rejected and puts you back in the queue.
- Establish the exact scope. Sitewide or partial, and which issue Google named. Partial actions affect specific URLs and the rest of the site is unaffected.
- Fix it completely. For link-based actions that means removal attempts documented with dates and responses, then a disavow file for what won't come down. For thin or scaled content it means the content is actually gone or genuinely rewritten, not noindexed and left in place.
- Build the evidence pack. Spreadsheets of contacted domains, screenshots, before-and-after examples, dates. Reviewers are reading dozens of these. Make yours checkable in five minutes.
- Write the request honestly. What went wrong, who did it, what you removed, what you changed structurally so it can't recur. Requests that argue with the reviewer or blame a previous agency do not perform well.
- Wait. Google gives no service-level commitment. In practice responses land anywhere from a few days to several weeks, and complex link cases often take longer. Anyone quoting you a guaranteed turnaround is quoting a queue they don't run.
Core update recovery, without the false certainty
If your loss lines up with a broad core update, here's the honest position, and it's the one Google itself publishes. There is no violation to fix. Core updates reassess how well pages serve their queries, and the only response is to make the site genuinely more deserving — better content, clearer expertise, less duplication, real evidence that a real business stands behind the pages.
The part agencies skip: improvements may not show until Google next reassesses, and broad core updates land a handful of times a year. Work finished in month one might not be reflected until an update three or four months later, and sites that recover often do so across two update cycles rather than one.
That's hard to sell and easy to lie about. When traffic doesn't return in month two, an agency can always say the work needs more time — technically correct, achieving nothing. Our version: agree the quality work up front, ship it on a schedule you can audit, and report at each update whether the assessment moved. If two updates pass with nothing, the diagnosis was wrong and we say so.
Why our 90-day guarantee doesn't apply here
Every normal engagement we run carries the same commitment: we freeze your trailing-90-day count of qualified leads from organic search on day one, and if we haven't beaten it in 90 days we keep working free until we do. We never promise a specific ranking position, ever.
Recovery is the one place we take that guarantee off the table, and it would be easy to quietly leave it on to win the deal. Two reasons it doesn't belong here.
We don't control the decision. A reconsideration request is judged by a person at Google on a timetable nobody outside Google can see, and a core update reassessment happens when the next update runs. We control the quality of the work and the speed of the fix. A guarantee that depends on someone else's calendar is theatre.
The baseline is already broken. The guarantee works because we freeze a stable trailing-90-day number. On a penalised site that number is a wreck, and beating a collapsed baseline is trivially easy — which makes the promise meaningless in the other direction.
What you get instead: a fixed-fee diagnosis, a written probability of recovery with our reasoning attached, a fix plan you own outright, and the sentence "we don't think this is recoverable" when that's the truth. Once the site is stable, a normal retainer with the normal guarantee is available — measured from a baseline that means something.