I think CMS's are moving away from SEO, targeting only backend simplification.
For frontend, plugins and community packages included, what is the ...
For further actions, you may consider blocking this person and/or reporting abuse
I reality, I am current trying Next.js; not knowing better it is better or worse than Gatsby? But I am quite sure it is
next/headis still maintained (by a paid company hostingzeit.co).I am doing laravel with my custom html static generator, I dump nextjs. Haha
I'm doing Laravel also, btw which SEO strategy would recommend for a laravel app?
Follow the Google SEO guidelines should be enough :)
Alright, I'll do that. Thanks
I tried Next but finally decided to stick with what I already knew and used (Lapis on OpenResty) for better Seo and put javascript like a cherry on top for better experience.
I had a hard time trying to understand shared state between server and client side. When navigate back and forth, the concept becomes abstract. I lost the current state of my app.
I would like to add more on SEO. Regarding the front-end solution, I completely agree that Gatsby and Hugo are good choices. However, if one wants to improve SEO hard work, it’s important for him/her to understand what is seo is and what all other factors can help them succeed.
ranking js is still a tiresome process over traditional builds, even the head of google product said if your in ecom stay away from js. i feel thats a pretty good indication crawlers still struggle with manifests an deep level dynamic linking
SEO in the end is largely not a technical problem. As long as you have access to the head, the rest is more about how to adapt your generator to output the meta tags according to your API.
As a long as it is prerendered (SSG), not Javascript controlled (SPA).
I am doing seo my onlinequranclasses.com/ and myqurantutor.com/
I made some my own strategies and I am getiing good results. Your websites should be fast and your content should be unique and do somthing new.