-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Causing SEO confusion by setting canonical to true #866
Comments
This comment has been minimized.
This comment has been minimized.
@1v9 Thank you for your help, you solved some of my problems. According to the scheme you gave, the cannonical tags in the post in the blog will no longer be confused, but the cannonical in the tags, categories, archives, etc. is still confused. @ivan-nginx Can you update the source code of NexT to adapt it to my situation? |
I know why this part of the page is still confusing now. Because the sitemap.xml generated by the hexo-generator-sitemap plugin, links to tags, categories, archives, etc. contain the "index.html" suffix, and NexT does not use the "index.html" suffix when referring to these pages, so The cannonical tag generated by NexT is also not suffixed with index.html. This resulted in the URL submitted to Google containing "index.html" and the canonical without "index.html". So, I think this is a compatibility issue between NexT and hexo-generator-sitemap plugin. I hope you can solve it, thank you! |
@siaimes You are right, I've tried sitemap plugin and repeated it. Maybe you can solve this issue by its template option. Let's wait for |
@1v9 Thank you for your reply. It may be the easiest way to have the "index.html" suffix for the categories, archives, etc. generated by the NexT theme. I look forward to your update of the NexT theme. |
Guys, can u clearly to explain what u got and what u need? In Actual behavior and Expected behavior style. Thank's. |
@ivan-nginx The most primitive problem is that the links to the pages generated by NexT are inconsistent with the canonical tags in the page. Google is not sure which page is the canonical page that the user has affirmed. I modified the source code according to the @1v9 's comments, and the problem seems to be solved. You can see this web sitehttps://blog.siaimes.me/. The page's about URL is https://blog.siaimes.me/about/, and the canonical tag in the head is This is the result of fixing bugs using @1v9 's comments. If you just look at these, it seems that there is no problem. However, when you look into the sitemap (https://blog.siaimes.me/sitemap.xml) generated by hexo-generator-sitemap, you can find that the link for about page is
This is not the same as the canonical page that is declared by NexT. This still causes SEO disorders.
|
@siaimes still not understand your problem and seems it's not a bug actually. All pages with some time will reindexed with new canonical pathes. Need some time for this, of course. Let's in order. You want:
All that canonical links will be appeared and indexed in Google Search. Let's see some examples: Without any
|
@ivan-nginx It has been modified according to the recommendation of 1v9, and the file name is as you said. The point I know is that although the link generated by NexT is
The link generated by NexT now is |
Yeah! Will be good if Hexo merge it. |
Solution of this issue: use See also #1175 |
Fixed in #1143 |
I agree and want to create new issue
My hexo config permalink is :year/:month/:day/:title.html. When I set canonical to ture, I generate my webpages with canonical tag with no html suffix. However, all of my web pages appear with html suffixes, which causes my actual web page and Google search to not get the same page and Google from Webmaster Tools can see that the traffic of the two pages are not merged.
In addition, my URL has been in use for a long time and cannot be modified. NexT seems to have just been implemented for canonical, so I hope that you can be compatible with this situation.
Expected behavior
Actual behavior
Steps to reproduce the behavior
Node.js and NPM Information
Package dependencies Information
Hexo Information
Hexo version
Hexo Configuration
NexT Information
NexT Version:
NexT Scheme:
NexT Configuration:
Other Information
The text was updated successfully, but these errors were encountered: