You are viewing a single comment's thread from:

RE: ATTENTION - HIVE's SEO IS SHIT - Here Is What You Can Do About It! Prizes included :D

in #hive5 years ago

IMHO, we should focus on promoting PeakD instead of Hive.blog because it seems that front-end development of hive.blog is not a priority. I fear that it will stay underdeveloped just like steemit.com has.

Where does this leave community content, for example all finance related posts on LeoFinance?

It should be separately promoted by its community members on other platforms such as Twitter, Medium, FB and other centralized platforms.

Sort:  

I have noticed incremental small updates to the hive.blog interface since launch, though. While I prefer peakd, I am more optimistic about Hive's own site improving than I was about Steemit.

Although I too am more optimistic about that, that's just not going to cut it. Imagine how many hours of work it would take in order for it to be on par with PeakD.

Promoting community front ends on social is fair enough, but from an SEO viewpoint, isn't it just duplicate content? Also we can see the struggle for consensus on which front end to focus our SEO efforts on just in this one reply thread. Hive.blog vs peakd.com.

When PeakD were asking people to vote on their new URL, they were talking about using something without the Hive word because they want to be a front end for multiple blockchains going forward. While theirs is clearly better (I'm using it right now), I think we should be focusing on an original, main hive URL for community SEO efforts.

It's just such a shit domain... I wish more thought went into SEO and the domain when the name change was thought of.

Tbh I have no clue, I'm no SEO expert, just aware of some basic concepts.

Good point about PeakD. Maybe we should focus on Hive.blog then. But then again, I would only be willing to promote it if there were clear intentions to develop its front end to the level of PeakD and beyond.

It's just such a shit domain... I wish more thought went into SEO and the domain when the name change was thought of.

I couldn't agree with you more on this. Although this entire fork was made in such a rush, this should have been considered more.