-
Notifications
You must be signed in to change notification settings - Fork 188
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
Fixed #1508: Ported SEO component to NextJS #1566
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Next.js doesn't need react-helmet.
https://nextjs.org/docs/api-reference/next/head
https://www.netlify.com/blog/2020/05/08/improve-your-seo-and-social-sharing-cards-with-next.js/
@PedroFonsecaDEV :Great! I make some modification later today. Thanks. Actually never dug into Seo with NextJS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of what you're doing here should be moved to _document.tsx
instead of being used here.
I had to do this recently with next.js, and researched it a bunch. You can see an example:
- SEO and stuff you do in
<Head />
https://github.com/humphd/snowy-owls-ca/blob/main/components/Layout/SEO.js - globally meta for all pages done in
_document
https://github.com/humphd/snowy-owls-ca/blob/main/pages/_document.js
Moving out to 1.6. |
See also #1607 |
Links to ideas for improving social/meta: |
427e890
to
8777716
Compare
8777716
to
eb79f14
Compare
eb79f14
to
1996d01
Compare
Awesome. SEO seems really neat. |
1996d01
to
da03f7c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a few small things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we might want to add some additional tags. It should probably be addressed in a separate pr, which would fix (at least partially) #1607. But one thing that caught be attention is the image meta tag. Since we provide one for twitter, shouldn't we also specify one for og? (og:image
).
Yes, can you file a follow up for the image/alt issues? |
This image seem to fall under 'Decorative' category, and according to WCAG, alt should be |
We actually looked into the |
@birtony : Does it mean I can go ahead with it? |
da03f7c
to
83f2c22
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gonna second that
Issue This PR Addresses
Fixed #1508
Type of Change
Description
I modified SEO component to be written in TS
Checklist