Bless you Filipe! I appreciate it :)

Esse canal tem selo delicinha de qualidade 😉

ｓａｌｖｅ　ｔｅｌｏ

Olha só quem está por aqui, acho que estou num bom lugar

cheguei aqui pra melhorar o SEO de um projeto, e tem esse comment aqui. Posso garantir que o vídeo vai ser delicinha

Thank you very much Samira :)

Thanks Luke! I appreciate it :)

New vids every week, stay tuned!!

Thanks so much, Stephen!!

You're welcome, Ranga! Glad you're enjoying these videos :)

You're right :D changed the title to be: Mastering the basics of SEO in React and Next.js. Not as catchy but more realistic! Thanks for watching!!

You're welcome, Miguel!

Thank you The Noman!! Will be ready for next week I hope :)

Awesome! Glad you enjoyed it!

@@leighhalliday you're welcome. by any chance, please do more on SEO on nextjs and related themes. wish you the best of luck

Thanks, Richard! In a sense I view static & SSR the same way, at least to the browser or crawler... the response from the server is still pre-rendered, it's more of a matter of when that rendering takes place. Is it rendered on compile/build (static), or is it rendering upon each request (SSR). Good tips with ES lint and jsx-a11y!

What about schema SEO?

Hey Zygimantas! Thank you very much... one day I'll get there, just need to keep going :) I definitely need to do some storybook... I'll add it to my list!

Happy to help, thanks for saying hi!

Thank you Zero! You are great also!

Hey Nathaniel! What we do where I work is to use an external SEO specialist to let us know what to do, in terms of content strategies and keywords, content, etc... but the developers are in charge of implementing their suggestions. I think a web developer should at least know the technical basics of SEO, even if they aren't "SEO experts".

Hey Georgios! That's a great question and honestly I'm not sure. In Gatsby you generate them all at build-time... but that's not the case here, right? If they are user generated data, I would consider something like ImgIX or Cloudinary.

in the future we have the Image tag

I'm still making videos, one day this video may appear :D It's on my spreadsheet of topics ;)

No real difference... I think maybe some webpack configs look for one vs the other, but no difference inside of the file. I think most people just use .js now, wasn't that way a couple years ago.

@@leighhalliday Thanks. Your channel 👌🏾

Hey Vince! If I'm honest I don't think I have too many extra tips :D I'm not an SEO expert

@@leighhalliday This is enough already my website got 100 score on SEO after I watched your SEO on Next.js tutorial

Me too :D Let me know what I'm missing and then I might be able to tackle it.

Hey Muhammed! It's my understanding google has 2 crawlers... one that focuses on server rendered, which happens frequently and sooner, and another one which clicks around in a headless chrome browser, for client-side apps... this happens less often, but to be honest I doubt this will be the case for long considering how many SPAs are out there. Two approaches you could take: - Do nothing... google will probably figure it out even if you load the data client-side after initial page load. - Focus on service side rendering and/or static pages (in a sense, also server-side rendered). For that you might want to watch this video which covers the new hooks in Next.js you use to perform SSR and/or build static pages: kzfaq.info/get/bejne/h6dyntKXnd_Lqn0.html

@@leighhalliday thanks for fast reply.

Hello right back at you from Canada!

Haha... thanks! I wish I had as much money as Owen Wilson :D Off the top of my head I am not sure if the component does SSR... I would imagine it does though... that said, there are 2 types of crawlers that google deploys. One that just reads the HTML, and gets run more often and sooner. But they have another which actually renders pages and executes javascript. So I think either way you're better off than not doing any of this, but maybe you want to look into whether the Head component's meta tags are included in the HTML produced by SSR or not.

​@@leighhalliday Woah, thanks for the fast reply! I'll do just that!

Thanks Tuan!!

I haven't done this personally, but there's a lot of good discussion about it here using api routes along with Next.js/Vercel's URL rewriting capabilities: github.com/vercel/next.js/issues/9051

If anyone else is as dumb as I am, this functionality is now under the "Lighthouse" tab.

Ahh... didn't realize they renamed it to Lighthouse either! Thanks for sharing Christopher!

You'd add it in the head tag, using Head from Next.js or Helmet in plain React

Hey Michael! I think it just comes with Chrome by default!

the Audits panel is now the Lighthouse panel.