Live data from Hacker News

Google de-indexed Bear Blog and I don't know why

journal.james-zhan.com

51–60 of 199 posts

Re: Google de-indexed Bear Blog and I don't know why

#51
Without going into details. The company I work for has potentially millions of pages indexed. Despite new content being published everyday, since around the same October dates we are seeing a decrease in the number of indexed pages.

We have a consultant for the topic but I am not sure how much of that conversation I could share publicly so I will refrain myself of doing so.

But I think I can say that it is not only about data structure or quality. The changes in methodology applied by Google in September might be playing a stronger role than what people initially thought

Re: Google de-indexed Bear Blog and I don't know why

#52
post #4

We need a P2P internet. No more Google. No more websites. A distributed swarm of ephemeral signed posts. Shared, rebroadcasted. When you find someone like James and you like them, you follow them. Your local algorithm then prioritizes finding new content from them. You bookmark their author signature. Like RSS but better. Fully distributed. Your own local interest graph, but also the power of your peers' interest gra…

Why do you need Google at all?

From what you've described, you've just re-invented webrings.

Re: Google de-indexed Bear Blog and I don't know why

#53

Traffic to my blog plummeted this year and you can never be entirely sure how it happened. But here are two culprits i identified. 1. Ai overview: my page impressions were high, my ranking was high, but click through took a dive. People read the generated text and move along without ever clicking. 2. You are now a spammer. Around August, traffic took a second plunge. In my logs, I noticed these weird queries in my se…

I posted some details in the main thread but I think you might need to check the change in methodology of counting impressions and clicks Google did around September this year.

They say the data before and after is not comparable anymore as they are not counting certain events below a threshold anymore. You might need to have your own analytics to understand your traffic from now own.

Re: Google de-indexed Bear Blog and I don't know why

#55
At the risk of sounding crazy, I de-indexed my blog myself and rely on the mailing list (which is now approaching 5000 subscribers) + reprints in several other online media to get traffic to me. On a good day, I get 5000 hits, which is quite a lot by Czech language community standards.

Together with deleting my Facebook and Twitter accounts, this removed a lot of pressure to conform to their unclear policies. Especially around 2019-21, it was completely unclear how to escape their digital guillotine which seemed to hit various people randomly.

The deliverability problem still stands, though. You cannot be completely independent nowadays. Fortunately my domain is 9 years old.

Re: Google de-indexed Bear Blog and I don't know why

#57
post #35
post #15

Earlier quoted context omitted.

Centralization is simply more efficient. Redundancy is a cost and network effects make it even worse. You’d have to go the authoritarian route - effectively and/or outright ban Google and build alternatives, like Yandex or Baidu.

For a lot of things we don’t opt for the cheapest solutions that also lack redundancy for a lot of things. Why not for the “information highway”? Most efficient = cheaper. A lot of times cheaper sacrifices quality, and sometimes safety.

It's not even that. It's that "centralization is more efficient" is a big fat lie. If you look at the "centralized systems" they're... not actually technologically centralized, they're really just a monopolist that internally implements a distributed system.

How do you think Google or Cloudflare actually work? One big server in San Francisco that runs the whole world, or lots of servers distributed all over?

Re: Google de-indexed Bear Blog and I don't know why

#58
When I reload the page "https://journal.james-zhan.com/google-de-indexed-my-entire-b...", I get

Request URL: https://journal.james-zhan.com/google-de-indexed-my-entire-b...

Request Method: GET

Status Code: 304 Not Modified

So maybe it's the status code? Shouldn't that page return a 200 ok?

When I go to blog.james..., I first get a 301 moved permanently, and then journal.james... loads, but it returns a 304 not modified, even if i then reload the page.

Only when I fully sumbit the URL again in the URL-bar, it responds with a 200.

Maybe crawling also returns a 304, and Google won't index that?

Maybe prompt: "why would a 301 redirect lead to a 304 not modified instead of a 200 ok?", "would this 'break' Google's crawler?"

> When Google's crawler follows the 301 to the new URL and receives a 304, it gets no content body. The 304 response basically says "use what you cached"—but the crawler's cache might be empty or stale for that specific URL location, leaving Google with nothing to index.

Re: Google de-indexed Bear Blog and I don't know why

#59

Google search results have gone shit. I am facing some deindexing issues where Google is citing a content duplicate and picking a canonical URL itself, despite no similar content. Just the open is similar, but the intent is totally different, and so is the focus keyword. Not facing this issue in Bing and other search engines.

I've also noticed Google having indexing issues over the past ~year: Some popular models on Hugging Face never appear in the results, but the sub-pages (discussion, files, quants, etc.) do. Some Reddit pages show up only in their auto-translated form, and in a language Google has no reason to think I speak. (Maybe there's some deduplication to keep machine translations out of the results, but it's misfiring and disca…

The issues with auto-translated Reddit pages unfortunately also happens with Kagi. I am not sure if this is just because Kagi uses Google's search index or if Reddit publishes the translated title as metadata.

I think at least for Google there are some browser extensions that can remove these results.

Post reply on HN