You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the ability to set a noindex flag on a book, but it applies to all versions of the book. For sunsetting and removing older versions, it is significantly less disruptive from an SEO standpoint if we can tell search engines to stop indexing a version before we stop publishing it. Otherwise, the pages stick around in the search index for an indeterminate amount of time and lead to 404s from search results.
I think there are other cases where having the ability to configure options on a per-version basis would be useful. I can imagine scenarios where we might want to be able to build older versions with different options or apply different styles.
The text was updated successfully, but these errors were encountered:
The "live branches" configuration solves this problem for sunsetting old versions: #1421
With Asciidoctor, it is possible to inject metadata at the page level with the description and keywords attributes. In addition, docinfo files can be used to embed custom metadata.
We have the ability to set a noindex flag on a book, but it applies to all versions of the book. For sunsetting and removing older versions, it is significantly less disruptive from an SEO standpoint if we can tell search engines to stop indexing a version before we stop publishing it. Otherwise, the pages stick around in the search index for an indeterminate amount of time and lead to 404s from search results.
I think there are other cases where having the ability to configure options on a per-version basis would be useful. I can imagine scenarios where we might want to be able to build older versions with different options or apply different styles.
The text was updated successfully, but these errors were encountered: