New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blog posts should use h1 for titles #294
Comments
Here are the issues I could find for this post (which probably apply to all other posts):
|
Thanks for the suggestion. Do you have any specific ideas on what areas need the most improvement? Or sources for the items you mentioned? To your second point, body text is already inside WriteFreely handles the necessary metadata for a variety of situations -- posts with or without titles, posts including images, SEO-friendly URLs, etc. It scores highly for SEO on Google's Lighthouse tool (example report). If we're going to improve SEO, we need a concrete problem to address. |
There is one fundamental recipe for online creators to understand - content is king. Search engines are smart enough to distinguish content that is suitable for searcher also considering personal factors. Yes, HTML must be valid. But saying that one or another header tag will somehow magically affect position in search results is just bullcrap typically spread by agencies that sell SEO services. I've seen loads of stories including "your site will get worse results due to use of tables instead of divs" or "menus implemented without list elements will not be indexed". There have been times in history when Google and Yahoo would even punish for too rich meta tags. Just some experts might be too young to remember those times. Sitemaps are important, but more for new sites. As soon as you are indexed and revisited every few days search engines capture your site structure easily. So don't get carried away. Plain text file is likely to perform much better if it serves unique and useful content than one with responsive, tag-rich and "seo friendly" fancy site but with sourced article. Personally I have very good search results with my blog running on self-hosted, out-of-the-box WriteFreely. It is even surprising considering I haven't done any promotion except backlinks on my other two sites and Mastodon. |
@thebaer For that, I need to do a more in-depth review of the code. If I'll find something concrete, I'll comment here. But so far the biggest issue I see is about H1.
from here https://backlinko.com/on-page-seo#on-page-seo-basics:
Alternatively you can look at how other 'big' websites are doing it. This page's H1 https://www.theguardian.com/world/2020/apr/08/coronavirus-crisis-has-transformed-our-view-of-whats-important is the title of the article itself:
and it's placed inside the
I agree, tho this is a completely different issue.
This and maybe some other optimizations which 'make sense'. I agree with you that we shouldn't overdo it. |
Agreed with @gytisrepecka on not excessively optimizing without verifiable improvements. So far looks like the bug to solve here is:
|
Images need a value for the https://moz.com/learn/seo/alt-text We should ask the users to describe the image (max 125 characters) and have that as the value for the
We could use a clever way of encouraging the user to write something: to show a modal right after the image is finished loading and have a placeholder in the modal which will be the name of the file, without the extension (.jpg, .png etc). And the user seeing this will want to erase and write something that's more appropriate and then click OK for the modal to close. |
We may need to do some 301 redirects, from https://ahrefs.com/blog/301-redirects/ Right now this works:
|
Alt text can be added in WriteFreely using Markdown syntax. It's explained in the WriteFreely guides here. Here's the example in the guide:
A modal might be too invasive, but we could mention adding an alt attribute more explicitly in the docs. I like the idea of encouraging people though. |
I appreciate the ideas, @DontUseGithub. But since WriteFreely is used in so many different ways by different people, I don't think the software should force everyone to populate every As for the redirects, we handle the basics of I've updated the title of this issue to reflect the current issue to be solved here. Just note that this is lower priority for us, since overall SEO is already solid, and this fix will break many custom themes in the wild. So as part of this change, we'll also need to provide a migration path for users with custom CSS. Either way, if anyone can address the |
This comment was marked as spam.
This comment was marked as spam.
Closing this for now, since it's very low-priority and comes with a high amount of potential negative impact from any changes we make. |
Articles are very hard to discover (or they may not appear where needed) via search engines because of lack of SEO.
Let's take a look at some examples:
1- let's look at this randomly picked article, so let's copy the first 2 sentences and introduce them in a SE (Search Engine). DDG gives us this link https://kelly.writeas.com as the first result. This is bad because it should have returned this link. Google gives us this link as the first one and that's it, on the first page there are no other results that would link to kelly.writeas.com. This is a huge problem.
2- let's look at another randomly picked article, copy the first paragraph and paste it in various SEs. DDG: nothing. Google: nothing.
3- We could look at more examples but I think the idea is clear 😀 (when testing this yourself, make sure you pick an article that has been online for at least 24 hours because it's ok for fresh articles to not index well until the SE's bots find/index it)
To fix this, we need to optimize writefreely for SEs, there are various articles online that teach us how to do this, example: https://backlinko.com/on-page-seo#on-page-seo-basics
The text was updated successfully, but these errors were encountered: