search

jekyll / jekyll-redirect-from

:twisted_rightwards_arrows: Seamlessly specify multiple redirections URLs for your pages and posts.
MIT License
782 stars 113 forks source link

'noindex' meta tag in redirect pages and SEO results #231

Closed reneshbedre closed 3 years ago

reneshbedre commented 3 years ago

I am moving my old site pages to the new domain address. To redirect (301) old pages to new pages, I am using redirect_to: in the YAML front matter of old pages.

The redirect is working great, but it adding noindex meta tag in the old pages. Due to this, my old pages are not indexed and I lost the old page from google search results. It caused a significant reduction in web traffic to my new website. When I checked google search console, it says No: 'noindex' detected in 'robots' meta tag.

My new domain pages are not also showing up in google search results. I need to keep old pages in google search results until it is replaced by new pages without losing google ranking. As per google docs, it says keep the "Keep the redirects for as long as possible, and consider keeping them indefinitely".

Please, let me know how can I remove noindex meta tag and keep the old page in google search results until it is replaced by a new page. Thank you.

ChrisHammond commented 3 years ago

I'm running into this same problem. Would be nice to be able to configure/disable this

reneshbedre commented 3 years ago

@ChrisHammond

Yes, the developer should check this issue and fix it. As a workaround, you can create a new layout in Jekyll (under _layout folder) for redirect pages and remove the noindex meta tag. It helped me a lot and successfully replaced the old pages with new pages on google search results.

ChrisHammond commented 3 years ago

@reneshbedre thank you I just remembered the layout fix as well and was coming back here to tell you the same thing :D

jekyllbot commented 3 years ago

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.