A "Read more" links are not bad for SEO (and a11y) if done right

Have you read SEO advice where you have been told that having “Read more” links (buttons) are poor for SEO? I been and I don’t agree with that.

With Hugo and i18n you can squize as much SEO benefits from Read more links as possible with just:

<a aria-label="{{ T "ReadMore" }} {{ T "about" }} {{ .Title }}" href="{{ .Permalink }}#{{ replace (T "ReadMore") " " "_" }}">{{ T "ReadMore" }}<span class="sr-only"> {{ T "about" }} {{ .Title }}</span></a>

Read more here: A “Read more” links are not bad for SEO (and a11y) if done right


See also: Removing outdated content from the website… not only for SEO

4 Likes

Good article and point!

I have one question though:

Google and search engine robots also see the link as full text (through innerText), and not only as word Read more .

If I remember correctly, search engines, in particular Google search, doesn’t like things hidden and if you’re caught, they’ll penalize you manually. In this case, it’s advisable to have the same text for aria and non-aria, or no?

Re:

Would it not be better to just update the original article as compared to creating a new article and then redirect it to that?

As far as I know, Google, Bing, and Yandex recognizes the modified meta tags and if they do detect significant changes, they’ll push it up again. (However, changing modified without any significant changes, if caught, Google will manually penalized you.)

What’s your take on that?

Also, there are other approaches I’ve seen (and I’ve used), which of the following is better overall?

  1. Update existing (old) article
  2. Create a new article and add note “this is an update of {old article}”; and in the old article add note “{new and updated version is available at: }” (probably with ‘Expiry/expires’ meta in the old too)
  3. Create a new article and redirect 301 old article to it

Any advantages and disadvantages as far as SEO is concerned?

Goods question. If this method is abused for elements that shall not be hidden then probably this will happens.

The main use apart from creating more “descriptive links” was accessibility. Some screen readers read aria-labels others do not, hence the sr-only approach.

The “descriptive links” are recommended by Google for elements like “Read More” buttons, especially when you checking your site in web.dev.

By using an accessibility approach you, maybe “by mistake”, solve SEO issues with this type of link.

The sr-only method is used widely in Bootstrap 3 to add meanings to elements that shall not have text for ordinary users. This will allow screen readers to understand these elements in the same matters as search engine robots.

If you start using it to hide paragraphs stuffed with SEO keywords then that can definitely end up bad for you.

1 Like

Would it not be better to just update the original article as compared to creating a new article and then redirect it to that?

The answer will be Yes and No.
If you publish the original article 10 years ago, even if you update it and put lastmod date to current, it will still be published 10 years ago. Sometimes it’s not worth to did that if you can use a power of 301 redirect for a new article with similar content.

301 redirect will move power (link ranking) to the new article and this could have better benefits than refreshing old content.

In some articles, when updates require just minor changes this will be better than creating a new article for sure. It’s a subjective approach and a decision needs to be taken at the time to see, whether are updated article really will be better than the newly created.

Yes, search engines recognise modified dates, but again, you need to decide what will be better for you. I got a couple of old articles that I feel better just updating rather than creating new ones, but there are some that when creating from scratch (even based on old ones) are much richer in content and are more up to date.

We need to put ourselves in user/reader’s shoes. Sometimes, like on my page, you show both dates (published and updated), the fact that the article was published over 10 years ago may not sound good for the first visit even though that updated date states a different way, but that’s strictly based which what type of user we are dealing with.

  1. Create a new article and add note “this is an update of {old article}”; and in the old article add note “{new and updated version is available at: }” (probably with ‘Expiry/expires’ meta in the old too)

This example is exactly why I finally put my main article about removing old content. It’s not always working. Users are prompted on old articles that this has been updated and to follow new articles, but it’s like 50/50 that they will do that. Sometimes you will benefit more from removing and redirecting. I noticed that my old articles, despite describing to users that there is a new one - updated, are performing (gaining users) better than new ones. After removing and redirecting, finally, I have been putting users into the article that I want them to read, rather than the old one, and as a power of the old link goes with 301 redirects, this works better at promoting the new article and gaining new users.

The 1st and 3rd shall be, in my opinion, considered in first place over the 2nd option.

1 Like

Oooh, excellent points! Thank you very much.

I’ll do that too then, especially the new article + 301 redirect methods.

True, there are some searches where I always see the old article than the new one, I had to click and click to see the latest version of the article.

Thank you for sharing! Very useful and much appreciated!

1 Like