@fullstackdatasolutions/articles 1.3.0 → 1.4.0

package/dist/index.d.cts

@@ -591,6 +591,22 @@ interface ArticlesConfig {
      * a config is available (i.e. via `getArticleMarkdownResponse`).
      */
     markdownTwinHeader?: boolean;
+    /**
+     * Set to `false` to stop serving the `category/`, `authors/`, and `series/`
+     * listing twins with `X-Robots-Tag: noindex`. Default: `true`.
+     *
+     * Only the listing twins are configurable. Article twins are always
+     * `noindex`: an article twin is the same text as exactly one HTML article,
+     * so indexing it can only ever split that article's own signal between two
+     * URLs. A listing twin is a different case - it is a generated index of a
+     * category or author rather than a copy of one page - so a site may have a
+     * reason to let it rank, and this leaves that open.
+     *
+     * Either way AI crawlers can still fetch every twin; `noindex` only removes
+     * them from search results, and never blocks the fetch that is the point of
+     * publishing them.
+     */
+    listingTwinNoindex?: boolean;
     /**
      * Vendor-neutral event callback (Phase 27F). Fired by components/hooks at
      * meaningful reader-journey moments (see `ArticleEvent` in `events.ts`).

package/dist/index.d.ts

@@ -591,6 +591,22 @@ interface ArticlesConfig {
      * a config is available (i.e. via `getArticleMarkdownResponse`).
      */
     markdownTwinHeader?: boolean;
+    /**
+     * Set to `false` to stop serving the `category/`, `authors/`, and `series/`
+     * listing twins with `X-Robots-Tag: noindex`. Default: `true`.
+     *
+     * Only the listing twins are configurable. Article twins are always
+     * `noindex`: an article twin is the same text as exactly one HTML article,
+     * so indexing it can only ever split that article's own signal between two
+     * URLs. A listing twin is a different case - it is a generated index of a
+     * category or author rather than a copy of one page - so a site may have a
+     * reason to let it rank, and this leaves that open.
+     *
+     * Either way AI crawlers can still fetch every twin; `noindex` only removes
+     * them from search results, and never blocks the fetch that is the point of
+     * publishing them.
+     */
+    listingTwinNoindex?: boolean;
     /**
      * Vendor-neutral event callback (Phase 27F). Fired by components/hooks at
      * meaningful reader-journey moments (see `ArticleEvent` in `events.ts`).