Mixie is an open source, community-driven recipe platform where home cooks and food enthusiasts can cook, create and collaborate on unique and delicious recipes.
There are quite a few improvements that could be done here.
[ ] Recreate all preview images for static routes at lower sizes and proper sizes
[ ] Dynamic og image for dynamic routes such as recipes and users
Better search finding
Since recipes are open to the web and being search we need to improve these being found on google. What can we do?
[ ] improve sitemaps
[ ] increase internal linking
[X] moving recipe-jsonLD to head
[ ] making sure recipe pages have proper layout of elements
Fixing up recipe-jsonLD
At the moment these are only getting put into the body, that isn't a huge issue but would be alot better in the head of the document.
The other part is generating these schemas manually rather than using a package there is a npm package for schema.org types so this could be used to properly generate the schema, this would also allow adding extra fields to schema than what is currently supported with next-seo
Proper layout of elements on the page
Search engines find it helpful when pages are laid out correctly e.g h1 as the top of the page, ul / li for lists, etc. Trying to reduce extra element on the page and only adding necessary elements as need is very important
At the moment Mixie is quite lacking in it's SEO performance and could be 10x better.
What are some things we could:
Helpful items:
Manifest.json
For proper PWA the manifest.json has to be filled out, trying to fill this out as much as possible so that devices know how to see it
Clean up code
Reducing the size of page
There are alot of page in mixie that have a really high first load of javascript reducing performance drastically, this would be improved by:
Better Social Previews
There are quite a few improvements that could be done here.
Better search finding
Since recipes are open to the web and being search we need to improve these being found on google. What can we do?
[ ] improve sitemaps
[ ] increase internal linking
[X] moving recipe-jsonLD to head
[ ] making sure recipe pages have proper layout of elements
Fixing up recipe-jsonLD
At the moment these are only getting put into the body, that isn't a huge issue but would be alot better in the head of the document.
The other part is generating these schemas manually rather than using a package there is a npm package for schema.org types so this could be used to properly generate the schema, this would also allow adding extra fields to schema than what is currently supported with
next-seoProper layout of elements on the page
Search engines find it helpful when pages are laid out correctly e.g h1 as the top of the page, ul / li for lists, etc. Trying to reduce extra element on the page and only adding necessary elements as need is very important