This is a fantastic technical breakdown, ! It’s rare to see someone dive into the DOM and sitemaps with this much detail so quickly after joining.
Your points about the outdated UA tags and the identical title tags on https://hive.io are spot on that site definitely needs a 'maintenance' overhaul to represent a top tier L1. However, there is one major distinction that might shift the focus of your next audit: https://hive.io vs. https://hive.blog.
- Hive.io is essentially just a landing page a static 'business card' for the protocol. While it's embarrassing that it's technically lagging, it isn’t where the 'content' lives.
- The actual 'Censor Resistant Blogging' you were looking for happens on hive.blog, peakd.com, or ecency.com. When Google indexes 'Hive,' it’s actually indexing millions of posts across those frontends.
The SEO challenge we face isn't just a stale sitemap on the landing page; it's the canonical issue you mentioned in the comments having the same content mirrored across multiple domains ( blog, peakd, ecency ), which often confuses search engines and dilutes our authority.
I’d love to see you apply this same 'Screaming Frog' lens to hive.blog. That’s where the real battle for visibility is being fought (and currently, as you noted, being 'secretly' lost).
.... Looking forward to part 2!
RE: Why Google Doesn't Hate Hive (It Just Can't Find Us)