You are viewing a single comment's thread from:

RE: Analyzing traffic to hive.blog and api.hive.blog

in Hive Statistics3 years ago

Great stats, thank you for sharing. Indeed all frontends saw spike in crawling from mid July. More pages crawled means we will rank for more keywords and canonical linking across apps will increase that crawling across every app. 🚀

Sort:  

Mayve you can share some stats from Ecency

Sure, note that Ecency.com is launched 6 months later after hive.blog, so we are following behind 😊

I am not 100% sure but I think Cloudflare shows stats of every subdomains as well. Including api.hive.blog, images.hive.blog (in our case, rpc.ecency.com, images.ecency.com), etc. If anyone knows for sure would be interesting to know ways to filter out individual subdomains from Cloudflare analytics...

image.png

I am not 100% sure but I think Cloudflare shows stats of every subdomains as well. Including api.hive.blog, images.hive.blog (in our case, rpc.ecency.com, images.ecency.com), etc. If anyone knows for sure would be interesting to know ways to filter out individual subdomains from Cloudflare analytics...

You can't filter per subdomain iirc, but it definitely will show you stats from all subdomains.

Right, so RPC nodes basically have bots and all other apps which use them combined. And imagehoster instance as well, still quite impressive numbers and these will continue to grow 🚀

Very nice! Thank you

When content is published each frontend/application adds their name into metadata, that metadata then parsed by all apps accessing that content. Metadata then mapped to canonical link from @hiveio/hivescript nodejs package. So all front-ends point canonical link to original application that content was published from.