Official statement
Other statements from this video 43 ▾
- 2:22 What should you do if your site lost traffic after a Core Update without making any mistakes?
- 2:22 Are Core Web Vitals Really Going to Transform Your SEO Strategy?
- 3:50 Does a ranking drop after a Core Update really indicate an issue with your site?
- 3:50 Should You Really Wait Before Optimizing Core Web Vitals?
- 3:50 Why is Google delaying the complete transition to the Mobile-First Index?
- 7:07 Can Google really delay Mobile-First Indexing indefinitely?
- 11:00 Why doesn't Google canonicalize URLs with fragments in sitelinks and rich results?
- 11:00 Do URLs with fragments (#) in Search Console mean you need to rethink your tracking and analysis strategy?
- 14:34 Why do the numbers from Analytics, Search Console, and My Business never match?
- 14:35 Why do your Google metrics never align between Search Console, Analytics, and Business Profile?
- 16:37 How are FAQ clicks really counted in Search Console?
- 18:44 Are mobile and desktop accordions really neutral for SEO?
- 18:44 Is it true that mobile accordion hidden content is indexed as visible content?
- 29:45 Does the rel=canonical via HTTP header really still work?
- 30:09 Does the HTTP header rel=canonical really work to manage duplicate content?
- 31:00 Why does Search Console still show 'PC Googlebot' on recent sites when Mobile-First Index is supposed to be the standard?
- 31:02 Is it true that all sites indexed after July 2019 default to Mobile-First Indexing?
- 33:28 Why does Google emphasize textual context in Search Console feedback?
- 33:31 Are Search Console tools really enough to solve your indexing problems?
- 33:59 Why are your pages still not indexed after 60 days in Search Console?
- 37:24 What happens when Google occasionally indexes HTTP instead of HTTPS even after an SSL migration?
- 37:53 Is it really necessary to combine both 301 redirections AND canonical tags for an HTTPS migration?
- 39:16 What really causes your sitemap to fail in Search Console and how can you effectively resolve the issue?
- 44:07 Should you choose a subdomain or a new domain for launching a service?
- 44:34 Subdomain or New Domain: What Does Google Really Think for SEO?
- 44:34 Do Google penalties really transfer between domains and subdomains?
- 45:27 Do Google penalties really spread between domains and subdomains?
- 48:24 Should you really overlook PageRank when deciding between a domain and a subdomain?
- 48:33 Do links between root domains and subdomains really pass PageRank?
- 49:58 Should you really be worried about duplicate content from scraping?
- 50:14 Can you relaunch an old domain without being penalized for duplicate content by spammers?
- 50:14 Should you really report every scraping URL via the Spam Report to prompt action from Google?
- 57:15 Is it really necessary to report spam URL by URL to assist Google?
- 58:57 Why does Google refuse to show your FAQs in rich results despite perfect markup?
- 59:54 Why doesn't Google display your FAQ rich results even with perfect markup?
- 65:15 Is it possible to add FAQs to your pages just to secure rich results in SEO?
- 65:45 Can you really add a FAQ just to get the rich result without risking penalties?
- 67:27 Should you still optimize rel=next/prev tags for pagination?
- 67:58 Should you really submit all paginated pages in the XML sitemap?
- 70:10 Should you really index all category pages to optimize your crawl budget?
- 70:18 Should you really stop placing category pages in noindex?
- 72:04 Does the number of JavaScript files really slow down Google indexing?
- 72:24 Does Googlebot really render all JavaScript in a single pass?
Google recommends using the 'Send feedback' button in the SERPs when a site disappears from the results for its own brand without any obvious reason. This option allows you to report potential bugs to Google's engineers, outside the traditional channels like Search Console. The advice applies only when all typical technical hypotheses have been ruled out — manual penalty, indexing issues, obvious negative SEO attacks.
What you need to understand
Why does Google offer this specific reporting channel?
The disappearance of a site for its own brand represents a critical warning signal. When a site historically ranked in position 1 for its domain name or brand and suddenly disappears, without visible manual intervention in Search Console, there are two hypotheses: a technical error on the site side or a algorithmic bug on Google’s side.
The feedback button at the bottom of the SERPs has been around for years, but its usage remains unknown. Google presents it here as a channel for reporting anomalies directly to technical teams, bypassing community help forums and even the Search Console support. The idea: some algorithmic bugs can only be detected through user reports, especially in edge cases.
In what specific cases should this feedback be used?
Google implies three conditions. First condition: no manual penalty appears in Search Console, 'Manual Actions' section. Second condition: no obvious toxic link profile — no clear spam, no recent massive negative SEO attack.
Third condition, often overlooked: the site must have disappeared specifically for its brand, not for its generic keywords. If you ranked for 'running shoes' and lost those positions, that’s not the use case. If you disappear for 'Your-Store-Name.com' or 'Brand XYZ', then yes.
What happens after submitting the feedback?
Google does not guarantee individual responses. The feedback feeds into a queue of data analyzed by the Quality Search engineering teams, who look for recurring patterns. If multiple sites report the same type of disappearance within the same timeframe, it gets flagged as a potential bug.
In practice, this procedure is akin to a gamble. You send a signal, without confirmation of processing, without an announced timeline. But — and here lies the interest — some documented cases show unexplained reappearances after feedback, without any technical change on the site.
- The SERP feedback is a channel for reporting algorithmic bugs, not a traditional technical support
- It does not replace a technical SEO audit — to be used only when all rational hypotheses have been ruled out
- Google generally does not respond individually, but aggregates reports to detect patterns
- This channel specifically concerns brand search disappearances, not traffic losses on generic keywords
- The processing time is unknown — no guarantee of quick resolution
SEO Expert opinion
Is this recommendation consistent with observed practices in the field?
Let’s be honest: the majority of brand search disappearances can be explained by identifiable technical causes. Poorly configured robots.txt after a migration, forgotten noindex tags, gradual de-indexing due to crawl budget issues, canonicals pointing to dead domains. Pure algorithmic bugs remain rare.
But — and that’s where it gets tricky — some cases escape all logic. Indexed site, clean Search Console, decent speed, clean links, and yet: total disappearance for the brand. I’ve observed three cases in fifteen years where SERP feedback coincided with a reappearance within 72 hours. Coincidence or causality? [To be verified] — impossible to prove without access to Google logs.
What nuances should be added to this statement?
Google does not specify what it means by 'no obvious spam links'. Obvious to whom? A link profile with 20% toxic domains according to Ahrefs, is that obvious? And 5%? The dividing line remains blurry. Similarly, 'no manual penalty' does not mean an absence of algorithmic filter — Penguin, Panda, or unnamed quality filters can act without notification.
Another point: the SERP feedback mixes all types of reports — spam, inappropriate results, technical bugs. Your report falls into a non-differentiated queue, with no visible prioritization. No guarantee that your case will be treated as a priority, even if it concerns a legitimate missing brand.
In what cases is this procedure strictly useless?
If your Search Console shows massive indexing errors, declines in indexed pages, or critical Core Web Vitals warnings, SERP feedback will bring nothing. It’s a last resort channel, not a shortcut to avoid a technical audit.
Similarly, if you have suffered a documented negative SEO attack — a surge of spam backlinks in three days — disavowing via Search Console remains the official route. SERP feedback will never replace the disavow tool. Practically speaking: start by eliminating all rational hypotheses before using this channel. Otherwise, you waste time and overwhelm engineers with irrelevant reports.
Practical impact and recommendations
What should be done concretely before sending SERP feedback?
First step: check actual indexing via a 'site:yourdomain.com' search on Google. If no pages appear, the problem lies upstream — robots.txt, noindex, unnotified algorithmic penalty. If pages appear but not for the brand query, the signal changes: it may be a relevance filter or a matching bug.
Second step: consult Search Console in detail. 'Coverage' section for indexing errors, 'Manual Actions' section for penalties, 'Security Issues' section for compromises. Also check search performance: a sharp drop in impressions for the brand confirms disappearance but may also indicate internal cannibalization if other pages of the site capture the traffic.
How to write effective SERP feedback to maximize processing chances?
The feedback field is limited in characters, so be factual and precise. Indicate the exact query tested (e.g., 'Brand XYZ'), the observed date of disappearance, and explicitly mention 'no manual penalty, no obvious spam, site indexed'. Add the URL of the page that was supposed to rank.
Avoid vague phrasing like 'my site has disappeared, help me'. Google receives thousands of feedback daily — a structured and documented message has a higher chance of being escalated to engineers. If possible, attach a screenshot of the problematic SERP, although the system does not always allow attachments.
What parallel actions should be taken while waiting?
SERP feedback offers no guaranteed timeframe. In the meantime, continue the technical audit: check server logs to confirm Googlebot is crawling, analyze Core Web Vitals in Search Console, test loading speed via PageSpeed Insights. Sometimes, a hidden issue (blocking JavaScript, misconfigured lazy loading) escapes superficial checks.
In parallel, enhance your presence on alternative channels: Google My Business for local queries, Google News if relevant, social networks to maintain brand visibility. If the disappearance lingers, consider a Google Ads campaign on your own brand — a costly temporary solution, but one that maintains acquisition.
- Check complete indexing via 'site:domain.com' and Search Console before any reporting
- Rule out all technical causes: robots.txt, noindex, canonical, redirects, compromises
- Write factual feedback with the exact query, date, and explicit mention 'no manual penalty'
- Analyze server logs to confirm that Googlebot is properly crawling key pages
- Test Core Web Vitals and loading speed — a quality filter can act without notification
- Maintain daily monitoring of brand positions to quickly detect a reappearance
❓ Frequently Asked Questions
Le feedback SERP remplace-t-il une demande de réexamen dans Search Console ?
Combien de temps faut-il attendre après l'envoi d'un feedback SERP ?
Peut-on envoyer plusieurs feedbacks SERP pour le même problème ?
Que faire si le site disparaît pour la marque mais reste visible pour d'autres requêtes ?
Le feedback SERP fonctionne-t-il aussi pour les disparitions sur Google Images ou Google News ?
🎥 From the same video 43
Other SEO insights extracted from this same Google Search Central video · duration 1h14 · published on 04/06/2020
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.