I probably just suck at explaining.
CMSs and platforms like this will just use whatever the user put in the "title" field of the form as the <title>
(which is in the head tag and that we can't edit) and as the visible title of the article (rendered as <h1>
).
If the <title>
tag was removed you wouldn't notice a difference in the article but might notice that the browser tab is empty (or maybe contains | [site name]
as most of them append the site name to the article). Browsers and search engines use it so you probably want it.
If the <h1>
tag was removed, the title would be rendered as body text and be non-obvious to humans so you probably want that too XD Additionally, search engines (or at least Google because all seo is apparently all about Google) use h1 to identify what the page is probably about, the h1 is one of the main things that get matched in searches.
And yes as you noted you do absolutely need both to help with rankings :)
The heading tags (h1, h2 etc) are semantically supposed to function kind of like how they do in textbooks, where you have one main topic heading (h1) and several subtopic headings (h2) possibly with subsubtopic headings (h3+). There was a time where Google was using the h1 to help with matching keywords and rankings and stuff and so would penalise for multiple h1s as some were trying to do that to game their rankings, which is why I suggested starting from h2 when writing your post as the post title will be set as h1. And even if it doesn't matter for Google anymore (because they change their algorithms like underwear) it still looks nicer from a semantic point of view (like too many people would look at the code anyway XD).
That's the important bit and the rest was me ramblingly wondering how they deal with feed sites then but seems smart sites like peakd just give the feed pages lower headings (all the post titles on my "following feed" on peakd use h5).
Did that help or did I make it worse? :D
😂
So i've just created this wonderful post: https://hive.blog/itsatag/@zapncrap/testing-again-title
and on checking the page source, I see no '< h1 >' tag, which I didn't include in the text but gather from what you are saying will come from the Title if not included directly?
Damn, things are tough in the morning - I should probably go back to bed for a few more hours!
Great post, much inform XD
Yep :)
And in the source code:
ahh!
I was looking for h1 with a > directly following. Thanks for that. Soo, where are we - another coffee and I re-read what you put above? :D
So we can either have title and h1 the same by just entering the title, or go for a slight alteration and include a h1.
Go clickbait with the title and more keywordy with the h1?
If you can change the
<title>
then you could do that :) I don't know if you can do it on here though?I think I'll quit while I'm behind :)
Although I tried with SEO stuff on this post, I guess it's not really the type for trying to rank high on engines and bring people in.
What I really want to see, as mentioned in another comment, is a hive.blog post ahead of this one for an 'earn cryptocurrency' search on Google.
I think we've tried to move away from the 'get paid to do stuff' theme in recent years but lets face it, there are many things you can do on Hive to earn crypto (outside of begging and selling your vote too :D )
If you just write what people are looking for they'll find it. Which means either do all that horrible market research crap that I hate or just write what you're gonna write XD I put exactly no effort into seo these days (too lazy, got too many other things to do) and people are still managing to find the Blender and (now ancient because I haven't done any recent ones) Drupal notes on my blog.
Most of Hive's current ranking problem would be age as all pre-fork posts are also on steem so if the age thing still matters that would probably get priority if you were searching for something that could be found on either.
So really all we have left to do is write amazing beautifully formatted posts ;D
Indeed. Which is why we need to probably reproduce the guides/etc on the new chain, and be good with formatting. And write awesome content of course :)