StatusCake

Google News to Pay in Germany?

statuscake

The on-going battle between Google and the German authorities – to date mainly concerning privacy issues – has just ratcheted up a further notch as the Bundestag, Germany’s lower house of its parliament, approved a new bill which would require search engines such as Google, to pay a licence fee for any news “snippets” it uses in its German organic search results.

Passed by a majority of 50 politicians, the bill is a very much a compromise on that originally pushed for by beleaguered execs in the German media and publishing world.   These “old world” execs believe that Google and other news aggregation services (such as Google’s own Google News) threaten their entire way-of-life.  That if “snippets” (though this isn’t defined in the German bill!) are allowed to be displayed in Google News without their permission – generally up to 240 characters – this damages their business.  That Google News readers will simply absorb all they need to know from this “snippet” and won’t go on to read the actual article on the newspaper’s website.  Less readers on the newspaper website hits them where it hurts – in their wallets with lower advertising revenues.

What is Google saying?

Google for its part, not surprisingly, argue that actually they’re increasing the number of people who visit the newspaper website.  By giving Internet users a “taste” of the article, they’re effectively actually promoting the article to users and encouraging them to click through to the newspaper website.

So whilst Google may be suggesting, though not publically, that the likes of Axel Springer should actually be thanking Google, rather than lobbying for this new law, the newspapers are pushing on with their demands – similar to those made in France, that Google should pay them a licence fee if they want to use links and “snippets” on the likes of Google News.

So have Google with its “Defend Your Net Campaign” and “Wikimedia Deutschland”, and Internet advocacy groups like Digitale Gesellschaft failed?

Well in short, no.  The bill is as I said very much a compromise needed to push it through the lower house – and those promoting the bill, know they still have to get it approved by the upper house. The compromises included pretty substantial carve-outs – included allowing website to use “short snippets” (again not defined!) of copyright material without paying any fee.  A fee is only owed where a much longer “snippet” is used, or the entire article is published.  Now although Google may crawl a newspaper website and store the whole article – as part of its search engine algorithms – it’s very difficult to argue that it publishes the article in full.

So actually it looks, for now at least, that instead of clamping down on Google, this bill has actually legitimised the Google News business model.

So what are the options for the newspapers?  Well they could of it’s entirely open to them to stop Google (and the other search engines) crawling their site.  But they’re hardly going to do that.  As much as they may dislike Google, for better-or-for-worse they’re reliant on search traffic.  Do they move from an advertising based model to a paid subscription model favoured by the likes of the UK’s Financial Times and the US’s Wall Street Journal?  Or something entirely different?

That’s for others to decide, but this latest episode shows that the law of “unintended consequences” is always there to catch you out.  Things are never what they seem on first glance!

Share this

More from StatusCake

What the Namecheap Outage Revealed About DNS Recovery

4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and

What Broke GitHub on August 17 and How Retries Made the Incident Worse

3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests

Automate StatusCake Monitoring with viaSocket

3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect

Website Monitoring Checklist: What to Track Beyond Uptime

7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.