Why next-seo plugin is no longer used? #91
-
|
I noticed that in the v1 branch, specifically in this commit 04ad761 you decided to replace the next-seo plugin with a custom header. May I ask why? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
I found next-seo to be more complicated than necessary, and that it is easier to add what I want manually rather than through its API. There were also problems with duplicated headers. I plan to add it back for the blog page. If you are using it for other pages you can generate the code from here https://www.google.com/webmasters/markup-helper/u/0/ and copy it over to the headers. Hope that helps |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your answer. Are you currently working on it? Or should I give it a shot and send a PR to the v1 branch? |
Beta Was this translation helpful? Give feedback.
-
|
Feel free to push a PR to the v1 branch, thanks! |
Beta Was this translation helpful? Give feedback.
I found next-seo to be more complicated than necessary, and that it is easier to add what I want manually rather than through its API. There were also problems with duplicated headers.
I plan to add it back for the blog page. If you are using it for other pages you can generate the code from here https://www.google.com/webmasters/markup-helper/u/0/ and copy it over to the headers.
Hope that helps