Appreciate the effort, but was hoping for React-only SEO tips. Next.js is great, but sometimes you need a React-focused approach. Still, thanks for sharing your insights! 👍
I really love this I have a niche website that contains blog, tutorials , forum and many more services completely built with ReactJs and springboot backend. I am worried how to get a great SEO. everyone is talking about NextJs and I am wondering if i just wasted few months building it. should I upgrade my site to NextJs or there is a way to trigger SEO in ReactJs? thanks
In general ReactJS is great for standalone website but if you have a integrated app with different pages and services, NextJS would be a better framework. No you have not wasted your time because NextJS is built on top of ReactJS so it would be lightning fast to switch to NextJS if you already know ReactJS. I hope this helps. Cheers!!
React uses a hydration mechanism to put the data into a webpage via Javascript aka rendering and hence crawlers can't see your content. Check this for details - fluxyai.com/resources/chats/-NZg0bUc18g1dzDrTJCG
Appreciate your video for the SEO, but your dropping the coins just prior to like, subscribe. is marketing masterclass... pyschological brilliance. brilliant!!!
@@logiclab10 I get it, for the SEO purpose it is done, to stop the behind the scene hydration (could be achieved with SSR too, if I'm not wrong?) Can we somehow incorporate a loading state in the code you showed though?
@@as_if that is correct. You could use SSR as well. The bottom line is that search engine like google, they will only see the first DOM strucuture and data and not the dynamic hydration.
@@pushkarbansal1926 It because we want google to see the actual data and not the "loading". if we dont use static or SSR react will start with "loading" and rehydrate the page later but for search engine like google the page content ="loading"
I agree you said that but concept is not about static product Anurag. If you want to fetch data from a db and while its fetching, you would like to show lets say "loading" to the user, in that case, hydration cycle changes. Static display is a different story and that not what we are discussing here.
I see, but in that case wont google see some other products while we are listing some other products eventually ? Is the idea here to have a tradeoff of sorts, meaning instead of not showing the actual products we are listing the dummy placeholder products so that atleast something get crawled & listed by Google ?
@@anuragnegi9636 that is what I have explored in the video with getstaticprops. You can do the database fetch with getserversideprops if your content is dynamic and keep changing. e.g. a blog. The dummy data that you referred is what getstaticprops do in a more elegant way. If you dont like it, then yes you can start with a dummy state and rehydrate the comp later
@@logiclab10 u clarified this in comment, i think it was not clear in the video. u should have explained how we could have also fetch dynamically from DB in getstaticprops and rehydration concept.
ctx is a context variable that nextjs/react provides you. It contains items like request and response. You can print the variable to see its content or read the documentation for details.
Appreciate the effort, but was hoping for React-only SEO tips. Next.js is great, but sometimes you need a React-focused approach. Still, thanks for sharing your insights! 👍
Noted!
I really love this
I have a niche website that contains blog, tutorials , forum and many more services completely built with ReactJs and springboot backend.
I am worried how to get a great SEO.
everyone is talking about NextJs and I am wondering if i just wasted few months building it.
should I upgrade my site to NextJs or there is a way to trigger SEO in ReactJs?
thanks
In general ReactJS is great for standalone website but if you have a integrated app with different pages and services, NextJS would be a better framework. No you have not wasted your time because NextJS is built on top of ReactJS so it would be lightning fast to switch to NextJS if you already know ReactJS. I hope this helps. Cheers!!
@@logiclab10 it helps
Thanks 🙏
Wordpress was in the title, but I do not recall it ever been mentioned in the video
You are right, wordpress should be removed. Thanks for pointing it out
But how its getting data before google crawl it if i getting data from database
React uses a hydration mechanism to put the data into a webpage via Javascript aka rendering and hence crawlers can't see your content.
Check this for details - fluxyai.com/resources/chats/-NZg0bUc18g1dzDrTJCG
Appreciate your video for the SEO, but your dropping the coins just prior to like, subscribe. is marketing masterclass... pyschological brilliance. brilliant!!!
Thank you 🙏, appreciate the compliment 😄
You removed the settimeout in the getStaticProps, which dismissed the case of loading. But you've to show loading page too to the users
That is the idea, depending upon your usecase you have to choose to loading or SEO ranking
@@logiclab10 I get it, for the SEO purpose it is done, to stop the behind the scene hydration (could be achieved with SSR too, if I'm not wrong?)
Can we somehow incorporate a loading state in the code you showed though?
@@as_if that is correct. You could use SSR as well. The bottom line is that search engine like google, they will only see the first DOM strucuture and data and not the dynamic hydration.
Great content dude
Hooks are not working in it
Hi Sanket, could you please elaborate what kind of issue you facing?
In short, you kust removed loading from there. What did you even do?
If you are asking what did I even do then you didn’t not understand the problem we are trying to solve here.
I mean why did you remove the loading thing from there
@@pushkarbansal1926 It because we want google to see the actual data and not the "loading". if we dont use static or SSR react will start with "loading" and rehydrate the page later but for search engine like google the page content ="loading"
Doesn't make sense ,why can't you create a state which contains the products array, if your goal is to render a static product list ? Less hassle
I agree you said that but concept is not about static product Anurag. If you want to fetch data from a db and while its fetching, you would like to show lets say "loading" to the user, in that case, hydration cycle changes. Static display is a different story and that not what we are discussing here.
I see, but in that case wont google see some other products while we are listing some other products eventually ? Is the idea here to have a tradeoff of sorts, meaning instead of not showing the actual products we are listing the dummy placeholder products so that atleast something get crawled & listed by Google ?
@@anuragnegi9636 that is what I have explored in the video with getstaticprops. You can do the database fetch with getserversideprops if your content is dynamic and keep changing. e.g. a blog.
The dummy data that you referred is what getstaticprops do in a more elegant way. If you dont like it, then yes you can start with a dummy state and rehydrate the comp later
@@logiclab10 gotcha! 👍
@@logiclab10 u clarified this in comment, i think it was not clear in the video. u should have explained how we could have also fetch dynamically from DB in getstaticprops and rehydration concept.
What is that ctx param?
ctx is a context variable that nextjs/react provides you. It contains items like request and response. You can print the variable to see its content or read the documentation for details.
Thanks man..
Happy to help
I though Search Engines just used keywords under meta
هل يمكنك اضافة الواتس اب الخاص بك