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

Buy vs Build in the Age of AI (Part 2)

6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff

Buy vs Build in the Age of AI (Part 1)

5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything

Alerting Is a Socio-Technical System

3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting

Designing Alerts for Action

3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams

A Notification List Is Not a Team

3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years

Alert Noise Isn’t an Accident — It’s a Design Decision

3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.

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.