So they have systems to identify this, yet they are asking - cap-in-hand - for users to report issues for further investigation? Their ranking data has been useless for some time now due to this issue. Any claims of mitigation are at odds with reality inside their product.

Fair play to Nozzle publishing this. Not really in their own interest, and the other tools seem pretty tight lipped about it. But hopefully Nozzle will get the attention they deserve for their research.

This is awful. Far too young. He was a super nice person. RIP Nick.

Some very serious data analysis showing just how much poisoning is going on: nozzle.io/research/poisoned-… TL>DR; 27.5M SERPs analysed 660K+ keywords with poisoned SERPs 49 countries - Austria had 18.8% of scraped SERPs show poisoned results. 8.0% of SERPs poisoned

I think we're safe for a little while longer... Pretty poor imo.

Most likely a third party product summarizing the reviews, and I'm pretty confident the bad reviews being left in is a conscious decision. Very easy to train or prompt out the bad in this response.

Nice that they kept it honest - not only the good, but also the bad highlighted. Probably also a fantastic way to capture product feedback. Is it indexable, and does it rank? Also wonder if it works well for AI?

Not good. At all.

I think you and I are doing something very different. I need to dog out my old tests and screenshots. The one major difference I see immediately is that I always tested rendered real content instead of dynamically painting elements. But we seem to have very different outcomes.

On the flattened DOM - this I was aware of previously, and has been the case for a decent time IIRC.

Thinking a bit more about this overnight. Google recently changed their docs to say that they changed their max HTML size to 2MB (before 15MB). I wonder now if they resize the window to any height so long as its content is within the 2MB limit?

Ok. Good to know. I think this is new behaviour since I last tried it. I'll have to get testing again to see how this works now.

Why is innerHeight changing after 5s? I think you may be doing something which isn't typical of what WRS does. I tested this by loading a very long page and then outputting read innerHeight at top of page. Then just read this from the screenshot. No dynamic loading involved.

Page 1 might be for [product for sale in location] and include pages clearly targeting different cities/locations. Page 2 includes only legal/govt sites related to a location called "sale", with nothing related to product whatsoever. AI fanout using this garbage is gonna hurt.

I'm now seeing some very serious fuckery by Google on SERP Page 2 served to trackers. For commercial queries: - Page 1 includes things like alternative locations to the users. - Page 2 sometimes replaces the main entity altogether. The giveaway is in PAA, Maps, AIOs etc.

Crawl stats now 5 days trailing with no updates :(

If Dan appeared to have pedals, handlebars and wheels would that most likely mean Dan is a bicycle?

Try instead loading a page with enough content to fill 10k px. Then read innerHeight. I suspect you'll get a different outcome.

Should be an easy theory to test. Just ping @seroundtable and ask Barry if he's previously reported any similar delays around past core updates.

Nice that you work through the list, but a challenge you have here is going to be "Other error" which can vary from 1 between Live Test tool requests. Your plugin page makes reference to the crawled page having no height limit. Might be an idea to use the WRS limit?