Quick SEO wins #3424
Comments
|
For the Maps page, it seems that an h1 heading could be added but with a |
|
@codisart Good point. Let's not worry about the maps for the moment I think... |
|
🎉 This issue has been resolved in version 1.180.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
Wrong auto action. There's still some to do right, @codisart? |
|
Yep at least Howto. |
|
@codisart Questions all good? |
|
There is many headings in user and user settings. I have begun working on it. |
|
@codisart Amazing, thank you! |
|
Also, @codisart - are you on our discord? I wish to send you more praise. |
|
🎉 This issue has been resolved in version 1.181.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 1.182.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 1.183.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 1.182.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
There's a few quick wins we can do from a search and social prospective.
Heading tags
The research, how-to and question titles should definitely be h1s rather than h2s. There might also be more semantic heading considerations.
Image alt tags
At the moment we don't ask users to provide alt tags for the images that upload. As a short-term fix, we should apply alt tags to research updates, how-to steps and questions which follow some kind of dynamtic structure, e.g. ' -![]()
'
Better open graph tags
At a minimum we need 'og:type' set to website in the
postCraBuild.tsscript, but there's probably more improvements we should makeThe text was updated successfully, but these errors were encountered: