In response to claims Google lifted lyrics from Genius, Google has asked its lyrics partner to investigate, will soon include 3rd-party attribution on lyrics
But the Amounts Are ‘Miniscule’ Tweets: @searchliaison : Some questions have been raised this week about where Google gets song lyric information from. Our blog post today explains more. It also clears up a common misconception. Lyrics are not “scraped” from web sites; we license data feeds for them. https://blog.google/... https://twitter.com/... @lyricfind : Our official response to the Wall Street Journal article: https://lyricfind.com/... AJ Kohn / @ajkohn : The response from @LyricFind (https://lyricfind.com/...) to the accusation of copying lyrics from Genius is odd in a lot of ways. #seo #lyricsgate Stephen Shankland / @stshank : Google on lyrics in search results TL;dr1. Those copied lyrics weren't our fault — we just got them from a lyrics content provider from whom we license lyrics2. We'll add source attribution to lyrics in search resultshttps://t.co/u9zpTcDtKM
Context & Ripple Effects
Three days after Genius published what it called irrefutable proof that Google was lifting its lyrics into search results, Google has moved from denial to damage control: it says lyrics come from licensed data feeds — not scraping — and has asked its supplier to investigate. That supplier is LyricFind, the company behind Google's 2016 licensing deal to show lyrics directly in search.
The response matters because it concedes the substance of the complaint without conceding culpability: by promising third-party attribution on lyrics results, Google is effectively admitting users couldn't tell where the words came from. Whether that transparency satisfies Genius — which has framed this as theft rather than a sourcing error — is the open question heading into any legal fight.
First-order effects
- LyricFind now faces an audit of its own data feeds, with its largest customer publicly asking whether licensed sources are actually flowing through — a direct threat to its role as Google's lyrics intermediary.
- Google's promised third-party attribution changes the lyrics product immediately: every lyrics answer in search will name its source, exposing a pipeline that until now was invisible to users and publishers alike.
Second-order effects
- If attribution reveals that Genius's own transcriptions sit inside the licensed feeds, Genius gains leverage not over copying but over licensing terms — the dispute shifts from 'did you take our lyrics' to 'what do you owe the upstream source.'
- Other publishers whose content appears in Google's direct-answer features get a template to demand: named sourcing as the price of inclusion, backed by the threat Genius demonstrated — public forensics plus press coverage.
Third-order effects
- The eventual court record points one way: a US judge later sided with Google against Genius's lawsuit, and the Supreme Court declined to revive it — meaning copyright law offers publishers little recourse here, pushing the real battleground toward contract terms and transparency mechanics rather than litigation.
- If the pattern holds, search engines' licensed-content pipelines get forced into the open one dispute at a time, making source attribution a standard feature of direct answers and turning data-feed intermediaries like LyricFind into accountable, auditable links in the chain.
The trend: Search platforms are being pushed from opaque licensed-data pipelines toward visible source attribution, as publishers treat uncredited content in search results as a grievance worth litigating even when courts side with the platform.