Customer feedback | SEO | Release notes
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 60
Description
### Feedback category
Search / navigation frustration
### Doc link
https://learn.microsoft.com/en-us/cli/azure/release-notes-azure-cli
### Summary
From Learn Customer Feedback, finding the changes of a particular Azure CLI version is difficult when we've grouped our release notes by date, not by version ID. The only way for a customer to find a release ID is `CTRL + F` (Windows) or scrolling indefinitely.
### Suggestion: Improve SEO
Make one of these two changes which will result in our release ID being searchable via Internet search engines, and more easily navigated in our doc:
* **Put the release ID as the H2.** Example 1:

* **Put both the relase ID and date both on the H2.** Example 2:

### Current state
* Release IDs are not searchable via an Internet search engine because they are not an H2 header
* This particular example is also causing a recurring azure-docs-cli build error because there are duplicate H2s.

### Customer feedback
"
Table of contents lists dates, not versions. Why? `az version` returns version number, not the date of the update. Really hard to navigate
"
### Example of current Internet search results:

CCin @dcaro for awareness.
Contributor guide
Assessment
This issue has not been assessed yet.