Hivescript for canonical links and SEO

[good-karma]

Hivescript is simple script/json to keep app URL structure of all Hive apps.

Source

There has been numerous articles about importance of canonical linking and SEO effects, optimization for Hive apps. Hivescript is result of those conversation to give SEO credit to apps. Previously, Steemscript was used across all apps on Steem. Now that all migrated to Hive, we have forked and keeping this up to date with Hive apps.

If post is published via one particular app, all other front-ends and apps should set canonical links to that particular website, which will increase their chance to get better ranking on Google and other major search engines. It helps not only apps but users who choose to use their services, because users design, prepare, format their posts for that particular application and they want readers to find that particular post/link. Note, if your app is not on a list, all other apps will likely set canonical to themselves.

Recent changes

• Added 3Speak
• Contains travelfeed, actifit, steempress, peakd, esteem, hiveblog.

If you are developing app and you don't find your app on a list, please do pull request here: https://github.com/ledgerconnect/hivescript

Hive on!

Comments

[lemouth]

Nice initiative. Would it be possible to add:

"STEMsocial": {
    "name": "steemstem",
    "homepage": "https://stem.openhive.network",
    "url_scheme": "https://stem.openhive.network/#!/@{username}/{permlink}"
  }

Thanks in advance! Do not hesitate to come back to me if any additional information would be needed.

Cheers!

B>

[good-karma]

Could you share example post which was posted from stemsocial ?

Posts should have json field similar to this structure: json_metadata "{"app":"stemsocial/1.0.0",

EDIT
ok, I have found this {"tags":["hive-196387","science","physics","oc"],"app":"steemstem"} Is this correct, will app field change to stemsocial?

if it won't change then, it should be like this:

"steemstem": {
    "name": "STEMsocial",
    "homepage": "https://stem.openhive.network",
    "url_scheme": "https://stem.openhive.network/#!/@{username}/{permlink}"
  }

[lemouth]

The app field will stay steemstem (at least for now). So what you propose is good. Thanks a lot for your help!

Cheers!

B>

[good-karma]

ok, added. @hivechain/[email protected] is available

[lemouth]

Thanks a bunch!

[yintercept]

This is really useful information. I often link to Hive content from other sites. I now know to look up the canonical source to help with people's SEO efforts.

I admit, I am one of those geeks who looks at HTML Source. I think it would be helpful if the rel=canonical tag was on a new line in the HTML. This picture shows that it is in the center of a long line:

If the canonical link was on its own line in the HTML, I could easily find the preferred link for a given article.

Of course, I am probably one of few remaining people on the planet you routinely uses the "view source" option on my browser.

PS: could you please tell Hive.blog to stop shrinking images to illegibly small sizes.

[rishi556]

Sending a few PR's for the tribes.

[rishi556]

Would adding Dblog/Engrave be another thing? It'd require some new additions.

Here's an example of a dblog post on the block explorer : https://hiveblocks.com/engrave/@rishi556/welcome-to-my-blog.

In the metadata, there's a key engrave with value {"domain":"rishi.dblog.org","permlink":"welcome-to-my-blog". That pretty much is all thats needed for it.

Format could be :

"Dblog": {
    "name": "Dblog",
    "homepage": "https://dblog.org/",
    "url_scheme": "https://{domain}/{permlink}"
  }

Frontends can pretty easily pull the domain from the metadata. But due to its unique nature, I didn't make a PR for it yet.

[good-karma]

It will require coordination on all frontends, I would suggest you to create PR for hivescript and then create issue on all frontend repositories so they can follow up and make changes accordingly.