How to Remove Defamatory Content from Google in India

Why Google Will Not Remove Content on Request

Submitting a standard Google content removal request rarely succeeds for defamation in India. Google's own policies require a court order or a clear violation of its Terms of Service before it will delist or remove URLs from Indian search results. The general public-facing forms are processed by automated systems and almost invariably rejected when the basis is defamation alone, without accompanying legal documentation.

This is not an accident of design. Google's safe harbour under Section 79 incentivises it to remain passive unless legally compelled. Understanding this structural incentive is essential before deciding on a removal strategy. A business or individual who sends only a standard online form has, in effect, done nothing. Legal compulsion — in the form of a correctly addressed advocate's notice or a court order — is what moves Google.

The distinction between Google as a search engine and the source platform hosting the defamatory content is also frequently misunderstood. Google indexes and serves links to content; it does not host most content itself. Removing a URL from Google's index is called de-indexing. It is a separate and distinct step from removing the source page itself. A complete removal strategy must address both layers.

The Two Legal Routes That Work

The first route is a formal legal notice under the IT Act. Sections 66E, 67, and 67A address privacy violations and obscene content. For defamation specifically, Section 499 and 500 IPC remain applicable alongside the civil remedy under the Law of Torts. A notice drafted by a practising advocate invoking these provisions and specifically citing the URLs to be removed carries weight that a user report does not.

The second and more effective route is a court order — either an injunction from the competent High Court or an ex parte interim injunction in urgent cases. Indian courts have consistently issued John Doe orders (Ashok Kumar orders) directing platforms to remove specific URLs even when the poster is anonymous. Once a court order is obtained and served on Google, compliance is rarely contested.

In practice, RepuLex pursues both routes simultaneously. The legal notice creates an immediate compliance obligation under the IT Rules 2021 and begins the clock on safe harbour withdrawal. The court proceedings provide the backstop — if the notice is ignored, the court order leaves Google no discretion. Running both tracks in parallel is faster than pursuing them sequentially.

There is also a third route that is underutilised: Google's own legal request mechanism for court-ordered removals, available through its Transparency Report portal. This is distinct from the public help form and is specifically designed for advocate-submitted legal requests backed by court orders or formal legal notices. Using the correct submission channel materially improves response times.

Section 79 IT Act and Google's Safe Harbour in India

Section 79 of the Information Technology Act, 2000 grants intermediaries — including search engines, social platforms, and hosting providers — exemption from liability for third-party content, provided they comply with certain conditions. These conditions include: not initiating the transmission, not selecting the recipient, not modifying the content, and — critically — expeditiously removing or disabling access to unlawful content upon receiving actual knowledge of its existence.

The phrase "actual knowledge" is legally significant. It does not mean actual knowledge in the everyday sense. Under the IT (Intermediary Guidelines and Digital Media Ethics Code) Rules 2021, a platform is deemed to have actual knowledge upon receiving a complaint from a user or a government authority in the prescribed format. Once that knowledge is established, the safe harbour window closes unless the platform takes expeditious action.

Formally stripping safe harbour from Google requires sending a notice that constitutes "actual knowledge" under the Rules — meaning it must be addressed to the correct officer (the Grievance Officer or legal department), must identify the specific content with URLs, must specify the ground of complaint (defamation, obscenity, privacy violation), and must be sent in a form that creates a verifiable record of receipt. A WhatsApp message or generic email to support does not qualify.

Once safe harbour is formally challenged through a proper notice, Google faces a choice: comply and retain safe harbour, or refuse and become potentially liable as a publisher of the defamatory content. This legal pressure — not mere moral persuasion — is what makes properly drafted IT Act notices effective. The advocate's role is to ensure the notice is structured to maximise this pressure in law.

What a Legal Notice to Google Must Contain

A valid legal notice sent to Google India's registered legal address (or Google LLC via their designated agent) must identify the exact URLs, state the specific defamatory content with verbatim excerpts, invoke the applicable sections of the IT Act and IPC, and demand removal within a defined timeline — typically 15 to 30 days, though 7 days is appropriate in urgent cases.

The notice must be sent by a practising advocate and ideally accompanied by evidence of harm: screenshots with timestamps, evidence of the content appearing in search results, and if possible, any measurable impact on business or reputation. Courts have subsequently treated the adequacy of accompanying evidence as relevant to the assessment of urgency and the award of interim relief.

The notice must also correctly identify the role of Google in relation to the content. Where Google hosts the content (as on Google Sites, Blogger, or Google Reviews), it is both the intermediary and the publisher and can be directed to delete the content at source. Where Google merely indexes third-party content, the notice must direct it to de-index the URL from search results and simultaneously a separate notice must be sent to the source platform.

A well-drafted notice will anticipate Google's standard responses — that it cannot verify defamatory intent, that the content does not violate its community guidelines, or that a court order is required — and pre-emptively address each objection by citing the specific statutory provisions that govern its obligations. This reduces the likelihood of a formulaic rejection and creates a stronger record for subsequent court proceedings if needed.

John Doe / Ashok Kumar Orders: Removing Anonymous Content

A significant proportion of online defamation in India is posted anonymously — through throwaway email accounts, VPNs, or pseudonymous handles. The identity of the poster is unknown, which ordinarily prevents service of legal notice and commencement of proceedings. Indian courts address this through what are known as John Doe orders, referred to in Indian practice as Ashok Kumar orders after the name conventionally used as the placeholder defendant.

An Ashok Kumar order is obtained by filing a civil suit for defamation naming the unknown poster as "Ashok Kumar / Unknown Defendant" and simultaneously applying for a court order directing Google, Meta, or the relevant platform to disclose the IP address, account registration details, and login records of the poster. Courts routinely grant such orders where the petitioner demonstrates a prima facie case of defamation and a legitimate need to identify the poster to pursue legal remedies.

Delhi High Court has developed a substantial body of case law on Ashok Kumar orders in online defamation cases. The court has held that the right to privacy of an anonymous online poster does not override the right to remedy of a defamation victim — particularly where the posts are clearly false statements of fact rather than protected opinion. Once the identity is disclosed by the platform, fresh summons are issued in the correct defendant's name and the proceedings continue.

The practical significance of Ashok Kumar orders extends beyond identification. The very fact that such an order has been filed and served on Google or Meta creates visible legal pressure on the poster — who typically receives notice of the proceedings from the platform — and in many cases triggers the deletion of the content by the poster himself before the identity is formally disclosed. This is an effective de facto removal mechanism, particularly where the poster is a competitor or disgruntled former employee who recognises the legal exposure.

The Role of Google's Designated Agent Under IT Rules 2021

The IT (Intermediary Guidelines and Digital Media Ethics Code) Rules 2021 require all significant social media intermediaries and search engines operating in India to appoint a Resident Grievance Officer based in India, whose name and contact details must be published on the platform's website. For legal notices to be effective, they must be addressed to this specific officer — not to the generic customer support address.

Google India Private Limited has published the name and address of its Grievance Officer, as required by the Rules. Notices sent to any other address — including Google LLC in California or Google's general Indian legal team — do not trigger the statutory 72-hour acknowledgement and 15-day resolution obligations under the Rules. Correctly addressing the notice to the Grievance Officer is therefore not a technicality but a substantive requirement for legal compliance.

Additionally, where the complaint relates to specific categories of content — such as content violating privacy, or content relating to national security — separate escalation mechanisms under the Rules require the platform to act within 24 hours. Advocates experienced in IT Act practice know which escalation tier applies to which category of content, and structuring the notice to invoke the correct tier can materially accelerate the response.

If the Grievance Officer fails to acknowledge the complaint within 72 hours or resolve it within 15 days, the platform's failure itself becomes actionable. The failure is a ground for (a) invoking loss of safe harbour under Section 79, (b) approaching the Grievance Appellate Committee established under the Rules for a direction to the platform, and (c) citing the non-compliance in court proceedings as evidence of the platform's bad faith. Documenting the submission and non-response is therefore as important as the notice itself.

Court Orders: The Most Reliable Method

Delhi High Court, Bombay High Court, and Karnataka High Court have all passed orders directing Google to delist and remove URLs. The process involves filing a writ petition or a civil suit for defamation, applying for an interim injunction, and serving the court order on Google through their legal representative. Courts have held that content accessible to Indian users falls within their territorial jurisdiction regardless of where the servers are located.

RepuLex has coordinated content removal through court orders in under 14 days in urgent cases where the client faced imminent business or personal harm. Speed depends on the jurisdiction, the evidence of irreparable harm presented, and whether the matter is listed before a bench that has previously dealt with online reputation cases. Urgent mention before the right court can compress timelines significantly.

The application for interim injunction must satisfy the three-part test: (1) a prima facie case of defamation — meaning the content contains false statements of fact, not mere opinion; (2) irreparable harm — meaning the reputational damage cannot be adequately compensated in money; and (3) balance of convenience — meaning the harm to the applicant from not getting the injunction exceeds the harm to the respondent from getting it. Courts have consistently held that professional and business reputational harm satisfies all three prongs.

Once granted, interim injunctions are served on Google through their Grievance Officer and legal representatives. Google has generally complied with High Court orders from Delhi, Bombay, and Karnataka within 48 to 72 hours of formal service. Compliance is tracked and if Google fails to act within the court-specified period, a contempt of court application can be filed — a step that courts take seriously and that Google is strongly incentivised to avoid.

De-indexing vs Source Removal: Why You Need Both

De-indexing is the removal of a specific URL from Google's search index. After de-indexing, the page no longer appears in search results for any query. However, the underlying page at the source website continues to exist and remains accessible to anyone who knows the direct URL, has bookmarked it, or accesses it through a cached version, a web archive, or another search engine that has not received a similar de-indexing instruction.

Source removal is the deletion or modification of the actual content at the source — the news portal, forum, review platform, or social media account where the defamatory content is hosted. Only source removal ensures that the content is truly gone from the internet. Without it, the content can be re-indexed by Google (particularly after the de-indexing order ages out), indexed by Bing, Yahoo, or DuckDuckGo, or discovered through direct links shared by the original poster.

A robust removal strategy therefore has two distinct tracks: legal action against the source platform under the IT Act or a court order requiring deletion; and simultaneously, a formal de-indexing notice to Google. These are two separate legal processes directed at two separate parties, and each requires its own correctly formatted notice or court order. Running them simultaneously, rather than sequentially, is materially faster.

RepuLex never treats de-indexing from Google alone as a complete resolution. In cases involving news articles, forum posts, or review platform content, the firm coordinates with the client on the source removal strategy and monitors both de-indexing confirmation (via Google Search Console API data) and source removal confirmation before closing a matter. Clients receive a written confirmation report documenting both steps.

What Happens If Google Doesn't Comply?

Non-compliance by Google with a valid court order is contempt of court — a serious matter in Indian legal proceedings. High Courts have the power to impose fines, issue summons to Google India's officers to appear personally in court, and in extreme cases, restrict access to Google services within India pending compliance. These consequences create powerful incentives for compliance that do not exist in the context of voluntary takedown requests.

In practice, contempt proceedings against Google are rarely required — Google's legal team generally prioritises compliance with High Court orders. The greater risk of non-compliance arises with smaller or foreign-hosted platforms that do not have a significant Indian presence. For these platforms, contempt proceedings are more complex because service on a foreign entity requires following the procedure under Order V Rule 25 of the CPC and the relevant letters rogatory process under the Hague Convention.

Where direct enforcement against a foreign platform is impractical, a more effective route may be to obtain a court order blocking the specific URL in India — which is served on internet service providers (ISPs) under Section 69A of the IT Act rather than on the platform itself. The Ministry of Electronics and IT (MeitY) has a blocking mechanism under which court orders can be converted into blocking directions to all ISPs operating in India, making the content inaccessible to Indian internet users even if the source page remains live.

Where Google has been served with a legal notice (not a court order) and has failed to respond within the statutory 15-day window, the escalation path is to file a contempt petition against the Grievance Officer personally, alongside a fresh application before the court for an injunction specifically citing Google's failure to act on the prior notice. Courts have found Google's failure to respond to properly addressed notices to be relevant to the grant of urgent interim relief.

Right to Be Forgotten vs Content Removal: Understanding the Difference

Right to Be Forgotten (RTBF) and content removal on grounds of defamation are distinct legal remedies that are frequently conflated but apply in different circumstances and through different legal mechanisms. Understanding the distinction is essential to choosing the correct legal route — choosing the wrong one wastes time and resources.

Content removal on grounds of defamation applies where the content contains false statements of fact that harm reputation. The legal basis is IPC Section 499/500, the law of torts, and the IT Act. The fact of falsity is central — the removal is ordered because the content is untrue and therefore unlawful to publish. This is the appropriate route when a review, article, post, or listing makes specific factual claims about you that are demonstrably false.

The Right to Be Forgotten applies where the content may be factually accurate but is outdated, no longer relevant, no longer serves any public interest, or where continuing to display it causes disproportionate harm to an individual's privacy. The legal basis in India derives from the Puttaswamy judgment (right to privacy under Article 21) and, from 2023, from Section 13 of the Digital Personal Data Protection Act. A person acquitted of charges whose name continues to appear in search results associated with the crime is a classic RTBF scenario — the article may have been accurate at the time, but its continued prominence is now misleading and harmful.

The two remedies can be pursued simultaneously. If a news article about you is both false and outdated, you have both a defamation ground and an RTBF ground. Pursing both strengthens the legal position: even if the court finds the article falls within press freedom (as accurate reporting at the time), the RTBF argument remains. RepuLex structures pleadings to advance all applicable grounds in parallel rather than selecting one and abandoning the other.

How RepuLex Handles Google Defamation Cases

Every Google defamation case at RepuLex begins with a detailed assessment under NDA. The client presents the URLs in question, and the legal team conducts a forensic review of the content to determine: (a) whether it constitutes actionable defamation under Section 499 IPC and the Law of Torts; (b) whether any RTBF grounds apply in parallel; (c) whether any IT Act-specific categories (privacy, obscenity) allow for a 24-hour or 72-hour takedown; and (d) which court has the most favourable jurisdiction and fastest listing times.

Based on this assessment, RepuLex prepares and dispatches a formal legal notice to Google's Grievance Officer and, simultaneously, to the source platform. The notices are drafted to maximise legal pressure by expressly invoking the applicable statutory provisions, citing precedent, and making clear the escalation path if the notice is ignored. This is a legal document, not a template form.

If the notices do not yield removal within the prescribed period, the matter moves to court. RepuLex's panel of advocates in Delhi HC, Bombay HC, and Karnataka HC files the civil suit, interim injunction application, and — where the poster is unknown — the Ashok Kumar application for identity disclosure. Where urgency requires it, an urgent mention is sought before the bench on the day of filing.

Following removal — whether by compliance with the notice or pursuant to a court order — RepuLex conducts a verification audit: confirming de-indexing in Google search results across relevant search queries, confirming removal at source, checking Bing and other search engines for residual indexing, and monitoring for re-publication. A written case closure report is provided to the client. All of this work is conducted strictly under NDA, and the fact of engagement is never disclosed.