Ask HN: Why isn't Google indexing information about the AT Protocol?
I've been observing this for a while, where very basic queries about atproto stuff doesn't show up. But yesterday I found a query that makes it VERY obvious: "list of public atproto relays". Here's DuckDuckGo:
1. https://firehose.directory
2. https://atproto.at/relays
3. https://atproto.wiki/en/wiki/reference/core-architecture/relay
4. https://pulsar.feeds.blue
5. https://leaflet.pub/12022731-ae4f-4a13-9f7a-5738b7a83c2e
Of those results, Google only has 3, the only one on the list that... doesn't have a list of public atproto relays. None of the other sites are present anywhere. Trying not to assume malice instead of incompetence here, but it's really ironic that one of the ecosystems with the strongest ties to the open web, with users creating dozens of new websites every week, isn't getting indexed.
12 comments of 33
[ 0.19 ms ] story [ 32.8 ms ] threadhttps://atproto.at/robots.txt is good and findable with a direct search
https://atproto.wiki/robots.txt is empty but findable on Google.
https://pulsar.feeds.blue/robots.txt is 404 and thus not indexed by Google.
https://leaflet.pub/robots.txt is good. A logged in google search for this finds this for me.
Tell the people at https://pulsar.feeds.blue to fix their robots.txt if they want to get indexed.
https://en.wikipedia.org/wiki/Hayes_AT_command_set
Yes, I "used an incognito window". Yes, I checked on multiple devices. Yes, Google is personalized. Maybe if you search "list of public atproto relays" from East Timor you get lists of public atproto relays. But you sure don't from Seattle right now.