Thanks for the feedback, that's a really good point.
To be honest, I added that text hoping to improve search engine visibility, but I wasn't sure if it was the right approach. It seems like it hurts the user experience.
Is the general consensus that this kind of content should live on a separate "blog" or "about" page for a single-page application like this? I'm new to this and would love to learn the best practice.
Users who see the blog post section will know it is an SEO tactic, which puts people off. Also, nobody's going to read it; I would recommend adding some JS to detect if the user is a google bot, if so, remove the blog post. Lastly, the faceless, generic design can seem very sketchy.
I don't really think it matters. This helps with SEO so more people can find the site. The UI is right at the top, so it doesn't really impact the user experience, especially since few people would bother to read all that content. As long as the tool is functional, that should be enough, right?
zaiyiqi|5 months ago
To be honest, I added that text hoping to improve search engine visibility, but I wasn't sure if it was the right approach. It seems like it hurts the user experience.
Is the general consensus that this kind of content should live on a separate "blog" or "about" page for a single-page application like this? I'm new to this and would love to learn the best practice.
Thanks again!
anon1395|5 months ago
Example of a good image toolbox online: https://ezgif.com/ - straight to the point.
Example of a bad page: https://imageresizer.com/crop-image - the long SEO-style content feels distracting and undermines trust.
Users who see the blog post section will know it is an SEO tactic, which puts people off. Also, nobody's going to read it; I would recommend adding some JS to detect if the user is a google bot, if so, remove the blog post. Lastly, the faceless, generic design can seem very sketchy.
teroquyiqwu|5 months ago
anon1395|5 months ago