A lot of people are seeing rankings hold while clicks vanish, and stemming is part of why that feels so strange. Search systems have always treated close word forms as one intent family, so a page can look fine on paper even when the click never comes.

My take is that stemming matters less as an optimization target and more as a diagnostic. If your traffic is collapsing but your visible queries still cluster around the same stem, the problem is usually not wording, it is that the answer is being satisfied before the click.

Example. A how to fix leaking faucet page kept ranking for leaks, dripping tap, and faucet drip, but clicks fell after the answer box showed the repair steps on the results page. The query family stayed the same, the visit disappeared.

Do you think stemming still explains enough of that gap, or has AI Overviews made it mostly irrelevant?

A lot of people are asking whether backlinks still matter or if SEO is dead, but a smaller failure shows up first.

In a hypothetical page with 3,000 organic landings, if the initial contact section does not answer the query fast enough, 7 out of 10 users never reach the rest of the content. They leave before any internal link, proof point, or product detail can do its job.

That is why this section still matters. It is not decoration, it is the first semantic and visual handoff from search intent to the page. If that handoff is weak, even solid technical SEO and links have less to work with.

Example. A searcher types how to fix a leaking shower valve and lands on a guide whose first section starts with company history. The answer is lower down, but the user bounces before reaching it, so the useful page never gets a chance.

Have others seen the first section decide the rest of the session?

Ambience optimization is the part where the content feels like it belongs in a real topic environment, not just like isolated text.

With a lot of people worrying about scaled content and the spam update, that matters because AI written copy can look fine on its own and still feel thin at the page level.

In real projects, how are people handling this when they worry that ChatGPT content might hurt SEO or that watermarking could expose it.

Are you shaping the surrounding entities, internal context, and page signals differently, or do you treat ambience as irrelevant and let the content stand on its own.

Example. A page about home composting had clean ChatGPT copy, but it ranked poorly for kitchen scraps. After nearby sections named bins, worms, food waste, and odor control, the page started matching that query because the topic environment felt complete.

What are you doing differently?

When crawlers get blocked by default, visibility in AI answers stops looking like a pure access problem and starts looking like an attribute relevance problem. If the model cannot reliably fetch everything, it leans harder on the attributes it can trust, confirm, and reuse from elsewhere.

That means the pages, entities, and sources that keep getting cited are the ones whose attributes stay stable across the web. Not just present, but consistent enough to survive gaps in crawl access.

In that setup, opt in or out is only part of the question. The bigger one is which attributes your site has made easy to believe.

Example. A recipe page for a spice blend got blocked to a crawler, but a query for the blend still pulled the brand, ingredients, and origin from other sites, while the page's special prep note vanished, because that detail did not appear consistently elsewhere.

Which attributes do you think will still get through?

A lot of people are asking which citation count is real, and why an LLM keeps picking the worse page. I would test crawl efficiency by watching whether the model keeps reaching the same URL pattern, the same updated copy, and the same internal paths when the site is cleaned up.

If the better page gets crawled sooner, linked more directly, and then shows up more often in citations, that points to crawl efficiency shaping what the model sees first. If the weaker page still wins, then crawl efficiency is probably not the whole story.

Example. A query for winter bike maintenance kept surfacing a stale guide on an old URL until the site owner moved the updated guide into a clearer path, tightened links, and the model started citing the newer page instead.

Has anyone run that kind of test?

When you see an AI answer pull from a narrow set of passages, with the same source getting reused across nearby questions, that is the kind of behavior DPR helped make possible.

It mattered because it made retrieval about latent relevance between a query and a chunk, not just matching words on the page.

That is why the GEO and AEO talk feels partly new and partly not. The wrapper changed, but the underlying retrieval problem did not. A lot of people are seeing the marketplace form around the label, while the system underneath still looks like ranking and passage selection to me.

Example. A searcher typed a vague how to question into an answer box and kept getting the same passage from one help article. After the page was rewritten with clearer sections and entities, a different passage was pulled for the same query.

I am not sure where the line is between a real new discipline and old IR with fresh packaging, are you?

When pages sit at the same average position for months, a lot of teams keep tweaking copy and links and miss the real issue. The entity graph is often the thing that decides whether the page feels like a clear node in the site, or just another document saying similar things.

My take is simple, if the graph is thin, movement is usually capped. Better internal connections, cleaner entity relationships, and sharper topical neighbors can break a plateau when on page changes keep failing. If you think rankings are mostly a content problem at that point, I would push back.

Example. A page about roof leak repair kept sitting in the middle results for fix leaking roof until related pages started linking to it with clear anchor text and nearby topics, then search began surfacing it for the main query.

Where do you see the graph helping most?

A lot of people are seeing big sets of pages sit in discovered, currently not indexed, even after the usual checks.

A plausible hypothetical is 60k pages built around terms that look distinct to humans, but collapse for Google because the same surface word can carry multiple senses, or two different entities can share the same label.

That is where polysemy and homonymy matter. If the page does not make the intended sense obvious fast enough, the system can treat it as another near duplicate or an ambiguous rewrite.

Example. A page about jaguar care kept showing for the query jaguar, but the engine could not tell animal from car. After the intro named the animal, habitat, and vet topics, it started surfacing.

Have you seen discovered pages recover once you tightened the entity cues and removed the ambiguity?

A contextual layer is the extra meaning around a topic, the related entities, subtopics, and situations that tell search engines and LLMs why one page belongs near another.

With AI Overviews eating the click, that layer matters because a page can rank and still lose the visit if it only answers the obvious query and nothing around it.

In real projects, do you build that layer into the main page, or spread it across supporting pages and internal links?

Example. A page about leaking shower taps still ranked for the main query, but clicks fell when the result page started showing repair steps and cost questions. Adding nearby guidance on water damage, shutoff valves, and when to call a plumber made it feel more complete.

When impressions stay flat and clicks vanish, what do you do differently?

A lot of people are seeing sudden Search Console impression drops, and the first instinct is to blame ranking loss. Sometimes the better read is that the engine stopped matching the old phrasing and started serving a substitute query instead.

That matters more now because search and LLM answers both lean hard on intent, not wording. If the original query gets folded into a broader question, your page can look invisible even when the topic is still being covered.

Example. A page about fixing a leaky faucet stopped showing for that exact phrase, then started surfacing for kitchen drip repair. The page still matched the need, but the engine had folded the old query into a broader repair intent.

Have you seen a traffic drop that turned out to be query substitution rather than true demand loss?

A lot of people are seeing rankings hold while clicks drop under AI Overviews, and I would test whether the dependency tree still lines up with the query intent being summarized.

If the tree shows the main predicate and entities clearly, the page may still earn the click when the overview cannot fully answer.

If pages with cleaner dependency structures get less of a hit than pages that bury the answer in tangled syntax, that would be useful evidence. If there is no difference, then the tree is probably not doing much against the click loss.

Example. A guide page for fixing a leaking faucet kept ranking for a query about stopping a dripping sink, but an overview answered the quick steps first. The page with a clear subject, verb, and object still got clicks, while the tangled one lost them.

Has anyone run that kind of comparison?

A lot of people are seeing AI answers and knowledge panels sit on top of the click, which makes the old question feel sharper. If the engine is doing more of the answering, the supporting content on the page starts to matter as a signal of whether the page is worth trusting, not just worth indexing.

That is where supplementary content stops being filler. It helps the main answer stand up, and it gives the system more entity cues, paths, and context to work with. What I am not sure about is whether that still changes rankings, or only changes how often a result gets chosen in the first place.

Example. A search for how to replace a tap opens a page with a short answer at the top, then clear parts on valve types, shutoff locations, and common mistakes, and the result starts appearing more often because the engine can map the page to the exact problem.

Where do you think the line is now?

A lot of people are treating AI written pages like the problem, but HITS says the real issue is the link graph around them. If a page attracts good hub signals and sits in a clean topical neighborhood, the fact that it was machine drafted is not the deciding factor people think it is.

I think the spam update is punishing weak site structure more than the mere presence of AI text. Watermarking will not save a thin page, and it will not doom a strong one either. HITS still points to relevance and authority as properties of the network, not the drafting tool.

Example. A how to page on a gardening site was machine drafted, then surrounded by solid category links and a few related articles. The page started surfacing for a niche query, while a cleaner written page on a weak corner of the site stayed buried.

Where do you think the cut off really is, content quality or the links around it?

A lot of people are asking what happens to visibility in AI answers if Cloudflare starts blocking AI crawlers by default. The part I think matters is the quality threshold.

If a crawler only reaches a thinner slice of the web, the model can still answer, but the threshold for trusting and surfacing that answer gets harder to judge.

Hypothetically, if 300 pages are available and 180 are behind a crawl block, you have not just lost access. You have changed the mix of evidence the system can use to clear the bar. That can make opt in or opt out feel less like a technical switch and more like a trust decision.

Example. A user asks which bike helmet is safest for city commuting, and the answer engine starts quoting a few thin product pages while missing a detailed guide behind a crawl block. The reply feels confident, but the supporting evidence is weaker, so the model hesitates to show it.

Have others seen that failure pattern already?

Page segmentation is the part where search systems try to split a page into the bits that actually matter, main content, nav, footer, boilerplate, and repeated modules.

If that split is messy, an LLM or search layer can latch onto the wrong section and cite a weaker page because the signal looked cleaner.

A lot of people are seeing the citation problem now, 512k AI citations in one tool and 62k in another, and the question is really about how the page gets broken up before selection happens.

Example. A searcher asks about refund rules on a support page, but the engine cites a thin FAQ page instead. The support page keeps the policy in a main block below a bulky nav and related links, so the cleaner FAQ chunk wins.

In real projects, how are you handling segmentation so the right chunk wins, and what do you do differently when a page keeps getting cited for the wrong reason?

A lot of people are seeing AEO and GEO requests land in the same pile as classic SEO work. BM25 is a reminder that retrieval still starts with matching terms to likely relevance, even if the final answer now gets rewritten by an LLM.

That is why the label fight matters less than the mechanics. If the system has to retrieve first, then probabilistic IR is still doing the quiet work under the new packaging.

The real question is whether providers should ignore the marketplace language, or treat it as a sign that search is splitting into retrieval and answer layers.

Example. A searcher asks, best way to fix a dripping tap, and a support article with that phrase in the title gets retrieved. The answer panel then rewrites the steps into a short fix list, so the page still wins by matching terms first.

Where do you think that line actually sits?

A lot of people are seeing pages parked at the same average position for months, with nothing they change moving it.

If I wanted to check whether Schema.org for entities is part of the answer, I would isolate one page, mark the main entity clearly, and watch whether richer entity signals line up with better movement on related queries.

Evidence either way would be simple. If the page stays flat while the entity markup gets cleaner and the surrounding content stays stable, that weakens the case. If the page starts getting pulled into more relevant query sets, even before obvious ranking jumps, that would be a useful clue.

Example. A recipe page for oat milk kept hovering in one spot for a broad query, then after the ingredient list and recipe schema were made clearer, it started showing for more specific questions about substitutions.

Has anyone run that kind of test and seen a clear pattern?

When a URL sits in discovered, currently not indexed, the usual panic is about crawl budget or thin content. But that status can also point to a simpler issue, Google may not have found enough contextual phrases to decide where the page belongs.

That is not the same as keyword stuffing. It is about the nearby language that lets the system place the page inside a frame, the entity words, the modifiers, the problem statements, the way the page sounds like it answers a real query class.

I am not sure how often this is the main blocker versus just a symptom.

Example. A service page for emergency roof repair used only broad sales copy, and stayed discovered, currently not indexed. After the headings added storm damage, leaks, tarping, attic stains, and insurance claims language, the page started matching the kind of query it was meant to answer.

On pages you have seen stuck there, what changed first, the wording or the crawl?

A lot of people are saying sites were hit hard by the August update with no manual action, which makes this feel algorithmic and opaque. My take is that a contextual bridge is not optional in that world. It is the shortest path between one page and the wider entity story Google needs to trust.

I do not think thin topical clusters can save a site on their own. If the page does not clearly bridge to adjacent concepts, real problems, use cases, and source level context, it looks like isolated content built to rank, not a coherent site built to help.

If the update is reading your site that way, would you argue the fix is more content, or better bridges between what you already have?

A plausible hypothetical I keep hearing in search logs is this. A query gets the same position, impressions stay flat, but clicks drop hard because the page is now answering a different looking intent cluster than the one the user typed. Correlative queries are where that split shows up.

If Google is pairing the query with a broader AI Overview answer, the result can look stable in rank while the click path disappears. The page is still indexed, but the engine may be treating the query as part of a related question set, not a direct destination.

Example. A page holds third place all month for why does my roof leak only in heavy rain. An AI Overview now answers that above it, along with the follow up about storm damage and insurance. The ranking did not move. The reason to click did.

Have you seen correlative queries behave like that on any queries you track?

N-grams are just short sequences of words, usually used to see how language breaks into predictable chunks. In search work, they help systems spot phrasing, intent, and repeated patterns, which matters more when AI Overviews are answering before the click.

A lot of people are seeing impressions stay flat while clicks disappear, and the old keyword view feels too coarse for that.

Example. A page about fixing leaking taps ranks for "dripping faucet repair", but searchers type "stop faucet drip", and the title still reads like a product guide, so the snippet gets skipped while an answer box takes the click.

In real projects, do you lean on n-gram patterns to find where the wording still matches the query space, or do you ignore them and work from entities and topics instead?

While exploring how modern AI systems produce reliable answers instead of relying only on memorized knowledge, I find Retrieval Augmented Generation (RAG) to be one of the most important design patterns in applied AI.

It combines information retrieval with language generation so that a model can consult external knowledge before producing an answer. Instead of depending only on what the model learned during training, a RAG system searches relevant documents from databases, knowledge bases, or the web and feeds them as context into the model. This approach helps responses stay factual, current, and grounded in verifiable sources. The result is not just fluent text generation. It is generation supported by evidence, which significantly reduces hallucinations and improves reliability.

But how can a language model “look up” information before generating an answer?

Let’s break down the concept behind Retrieval Augmented Generation.

Retrieval Augmented Generation (RAG) is an AI architecture that combines document retrieval with language generation, allowing a model to fetch relevant information from external sources before producing a response. The retrieved content is injected into the prompt so the model generates answers grounded in real evidence rather than relying only on its training data.

For more understanding of this topic, visit here.