Open arzljames opened 8 months ago
@arzljames I'd be glad to add this ticket to the roadmap but do want to bring up that it is not recommended for SEO to include underscores. I learned about this from @shrunyan when I joined Zesty.
You can read more on this here:
I would recommend sharing this with the customer if @giseleblair approves.
@arzljames I'd be glad to add this ticket to the roadmap but do want to bring up that it is not recommended for SEO to include underscores. I learned about this from @shrunyan when I joined Zesty.
You can read more on this here:
- https://www.woorank.com/en/blog/underscores-in-urls-why-are-they-not-recommended
- https://www.semrush.com/blog/the-most-common-hreflang-mistakes-infographic/
- https://www.semrush.com/kb/542-site-audit-issues-list#underscore-url
I would recommend sharing this with the customer if @giseleblair approves.
Got it. This is insightful. Thanks.
@zcolah I agree with SEO best practices, but the API allows for it and so does Webengine. This was a request that came directly from the customer so we just want to match the UI to our API service in this scenario. If you'd like to scope in a warning message about this in the UI then that's definitely an option
Some customers have requested to change their URL path parts to include underscores as values. While this can be updated through the API, it would be nice if the users themselves had the capacity to update it in the UI.
e.g
mywebsite.com/about-page
tomywebsite.com/about_page