Next SEO is a plug in that makes managing your SEO easier in Next.js projects.
MIT License
Bot releases are visible (Hide)
Full Changelog: https://github.com/garmeeh/next-seo/compare/v6.4.0...v6.5.0
CustomJsonLd
for carousel (#949) ae7923dMisc
Published by garmeeh over 1 year ago
Breaking change:
If you are using the app
directory you will need to migrate from NextSeo
component to the built in generateMetaData method in Next.js
Notes:
For standard meta data (eg: , ) then it is highly recommended that you use the built in generateMetaData method. You can check out the docs here
For JSON-LD then the only change needed is you should add useAppDir={true} to the JSON-LD component in use. You should add use this component in your page.js and NOT your head.js.
Also better safe than sorry with SEO 😅
As this bug was fixed via #1062 it may have some strange effects if you have a work around in place.
All other changes:
https://github.com/garmeeh/next-seo/compare/v5.15.0...v6.0.0
location
and address
(#1122) 0dbcef4eventStatus
/eventAttendanceMode
if not present (#1121) 94abb9ehttps://github.com/garmeeh/next-seo/compare/v5.14.1...v5.15.0
https://github.com/garmeeh/next-seo/compare/v5.14.0...v5.14.1
This release could probably have been a patch release with the below being the only change. Being an SEO library I will always lean towards being extra careful, hence the minor vs patch. Also this could result in broken tests anyway if someone was doing some form of snapshot on the output.
Changes:
Chores:
https://github.com/garmeeh/next-seo/compare/v5.13.0...v5.14.0
Be sure to check out the docs around the app directory
https://github.com/garmeeh/next-seo/compare/v5.12.0...v5.13.0
This release deprecates contactPoints
prop on the <OrganizationJsonLd />
component in favour of contactPoint
.
You do not need to change anything as until the next major release we will continue to accept contactPoints
.
However, it is worth noting that the output script will now contain containPoint
as per the correct schema definition. I did consider whether this was a breaking change as if you have tests checking the output they will fail and require a change. If you were effected by this and consider this a breaking change please let me know.
https://github.com/garmeeh/next-seo/compare/v5.11.1...v5.12.0
Chores
https://github.com/garmeeh/next-seo/compare/v5.11.0...v5.11.1
feat: add isAccessibleForFree prop on article and newsarticle (https://github.com/garmeeh/next-seo/pull/1060)
fix: article object type BlogPosting (https://github.com/garmeeh/next-seo/pull/1050)
https://github.com/garmeeh/next-seo/compare/v5.10.0...v5.11.0
themeColor
meta tag to support Discord Embed & mobile Chrome Browsers (#984) ac547e2Chores:
Chores:
Chores