Search Central LiveDeep Dive Europe 2026

Knowledge base v2.13.0 · Community edition · data through 2 October 2026

Day 3 · Friday 2 October 2026 · 10:45

Lightning session K: Facets of quality

Speaker Community speakers

Lightning talkCoverageTranscript

Only one community talk was recorded: writing for people rather than for search-engine metrics, with a case study from the speaker's own company. The other talks of this block were not captured.

Said on stage 20

StageD3-C097

In Lightning session K (Facets of quality), a community speaker argued that SEO is for humans: write for people and the problems they have, rather than to please Googlebot.

“SEO is for humans”

Speaker Community speakersEvidence transcript

Things
StageNot in docsD3-C098

A community speaker recalled that around 2009 writers bent titles and phrases to include a keyword because their CMS counted keyword density, and said that hitting the ratio really worked at the time.

Speaker Community speakersEvidence transcript

StageD3-C102

Entering the Polish market late, against strong competition and with a small team, a community speaker's team could not be a 'department store' that covers everything, so it went really deep instead of going broad.

Speaker Community speakersEvidence transcript

StageD3-C104

To choose what to cover in depth, a community speaker's team used Google Trends to find what people in their market were interested in and then gave them that content.

Speaker Community speakersEvidence transcript

  • Extends D2-C789 Day 2: Google presented three uses of Google Trends for content creation, marketing and SEO: keyword selection…
StageD3-C105

A community speaker reported that going deep instead of broad took the Polish edition of a large Spanish software-download website into the top three technology websites in Poland (period not stated).

Speaker Community speakersEvidence transcript

StageD3-C106

With a much smaller team, the Polish edition of a large Spanish software-download website reached double the organic traffic of the site's English edition, a community speaker reported (period and measure not stated).

Speaker Community speakersEvidence transcript

StageD3-C107

Because Googlebot is not a human, the speaker's team at the time thought more about Googlebot than about human readers, a community speaker said.

Speaker Community speakersEvidence transcript

Things
StageD3-C110

Because a bot that counts things was easy to work around, SEOs made the facade of their sites nice and fancy instead of focusing on what was inside, sometimes with no real shop behind the facade, a community speaker said.

Speaker Community speakersEvidence transcript

StageConsistent with docsD3-C116

Google's long-standing advice to write for people and give them what they want has become true in practice because Googlebot has become more and more human, a community speaker argued.

Speaker Community speakersEvidence transcript

Things
  • Repeats D1-C047 Day 1: Google's answer was that ML-based ranking systems are trained on content written by humans for humans, so…
StageD3-C119

In a community speaker's case study from the speaker's current company, a well-written, complex and complete article got 1,600,000 impressions, while an article written for a very specific audience got 46,000 impressions over the same period (data source and period length not stated).

Speaker Community speakersEvidence transcript

StageD3-C120

The niche article in a community speaker's case study was written for a very specific audience: a group of friends who wanted to play a game, had problems with a public server and looked for alternatives.

Speaker Community speakersEvidence transcript

StageD3-C121

Despite far fewer impressions (46,000 against 1,600,000), the niche article in a community speaker's case study got 28 times more clicks than the comprehensive article over the same period.

Speaker Community speakersEvidence transcript

StageD3-C122

In the same case study, visitors who landed on the niche article converted 10 times more than visitors of the comprehensive article, a community speaker reported.

Speaker Community speakersEvidence transcript

StageD3-C123

Conversions from content are real money that can be reported to stakeholders and shareholders, not an abstract KPI, a community speaker said.

“This is not some abstract KPI. This is real money that you can report to your stakeholders”

Speaker Community speakersEvidence transcript

StageD3-C124

The niche article in a community speaker's case study worked because the team stopped to analyse how people use the company's products and what the products bring them, then wrote about it.

Speaker Community speakersEvidence transcript

StageD3-C128

A community speaker's exercise: step out of your shop, look at your site from across the street the way users do, and check what problems its pages solve.

“walk out of your shop. Stand on the other side of the street, look at the shop the way your users are looking at it”

Speaker Community speakersEvidence transcript

StageD3-C129

If you cannot say what problems your pages solve for users, or the answer is 'it depends', you are optimising for the search engine rather than for people, and that will not work for long, a community speaker warned.

Speaker Community speakersEvidence transcript

  • Repeats D1-C013 Day 1: Ecosystem principle 4, incentivise high-quality content: content made for Search will not be successful.

What Google's documentation says 7

DocsSourceD3-C100

Google's spam policies define keyword stuffing as filling a web page with keywords or numbers to manipulate rankings in Google Search, for example repeating the same words or phrases so often that it sounds unnatural.

“filling a web page with keywords or numbers in an attempt to manipulate rankings in Google Search results”

Publisher Google Search Central

DocsSourceD3-C101

Google's guide to people-first content lists writing to a particular word count, in the belief that Google prefers one, as a warning sign of search engine-first content, and says Google has no preferred word count.

“Google has a preferred word count? (No, we don't.)”

Publisher Google Search Central

DocsSourceD3-C103

Google's guide to people-first content lists producing lots of content on many different topics, in the hope that some of it performs well in search results, as a warning sign of search engine-first content.

Publisher Google Search Central

DocsSourceD3-C117

Google's guide to people-first content says its automated ranking systems are designed to prioritise helpful, reliable information created to benefit people, not content created to manipulate search engine rankings.

Publisher Google Search Central

Analysis by the author 6

AnalysisD3-C109

The inspector metaphor blends two steps: Googlebot fetches pages during crawling, while tokenization happens later when the page is processed for the index, as Google explained on Day 2.

Author Ibrahim Anjro

  • Extends D2-C318 Day 2: Google does not store the complete sentences or the full HTML of a page in the Search index, because large…
AnalysisD3-C126

The case-study figures were said on stage without a photographed slide, a data source or absolute click numbers, and together they imply a click-through rate nearly 1,000 times higher on the niche article, so use them as an illustration, not a benchmark.

Author Ibrahim Anjro

AnalysisD3-C127

For content planning, start briefs from a concrete problem a real group of users has with or around your product, such as a failing setup they need an alternative for, rather than from a broad keyword the page should rank for.

Author Ibrahim Anjro

  1. Stage D3-C104 Day 3 · Lightning session K: Facets of quality

    To choose what to cover in depth, a community speaker's team used Google Trends to find what people in their market were interested in and then gave them that content.

    extends
    Stage D2-C789 Day 2 · Google Trends

    Google presented three uses of Google Trends for content creation, marketing and SEO: keyword selection, scheduling and ideation.

  2. Analysis D3-C109 Day 3 · Lightning session K: Facets of quality

    The inspector metaphor blends two steps: Googlebot fetches pages during crawling, while tokenization happens later when the page is processed for the index, as Google explained on Day 2.

    extends
    Stage D2-C318 Day 2 · Understanding what's on a page

    Google does not store the complete sentences or the full HTML of a page in the Search index, because large pieces of text would be unsearchable; it tokenizes the text into the smallest segments that still allow search.

  3. Stage D3-C116 Day 3 · Lightning session K: Facets of quality

    Google's long-standing advice to write for people and give them what they want has become true in practice because Googlebot has become more and more human, a community speaker argued.

    repeats
    Slide D1-C047 Day 1 · How Search works and where's AI?

    Google's answer was that ML-based ranking systems are trained on content written by humans for humans, so they understand and promote natural content better.

  4. Stage D3-C129 Day 3 · Lightning session K: Facets of quality

    If you cannot say what problems your pages solve for users, or the answer is 'it depends', you are optimising for the search engine rather than for people, and that will not work for long, a community speaker warned.

    repeats
    Slide D1-C013 Day 1 · Welcome and opening keynotes

    Ecosystem principle 4, incentivise high-quality content: content made for Search will not be successful.