Feature Request

The customer would like to have the option to display the configured Meta Title as the title of an article in the Knowledge Base site’s search results. Currently, the Article Title is displayed regardless of whether a Meta Title has been configured. Using the Meta Title in search results would help us differentiate articles covering similar topics across different product areas and provide clearer, more relevant titles to users.

Document360 already auto-generates llms.txt with links to .md versions of published articles. Please also generate llms-full.txt — the companion file in the llms.txt standard that inlines the full Markdown content of all published articles in one file at the site root. AI agents use it to ingest an entire knowledge base in a single request, and AI-readability scorers check for it. Platforms like Mintlify generate it automatically (example: 1password.dev/llms-full.txt ). Since Document360 hosts our site, only the platform can serve this file. The building blocks already exist: per-article .md rendering and the llms.txt pipeline. Same trigger (publish/modify/delete), same exclusion flags. Use case: developer.rocket.chat (~750 pages, 400-endpoint API reference), heavily consumed by AI coding assistants.

The customer requests that the SEO description character limit on the AI & Search Optimization page be increased. The current 150-character restriction limits the customer when updating SEO descriptions.

The customer requests an option on the AI & Search Optimization page to directly open the corresponding article in the editor. This would allow users to review the full article content before creating or updating the SEO description, without having to manually locate and open the article.

Implementation of "hreflang" attribute will help improving SEO performance

A customer has requested enhancements to the SEO Description report, specifically the ability to filter articles by status (Draft/Published) and visibility (Hidden/Visible) of the article. Currently, the report includes all articles, leading to very large and difficult-to-navigate outputs with limited filtering and no sorting flexibility. Introducing these filters would greatly improve usability by allowing them to focus only on relevant, user-facing content.

When the SEO title (Meta title) of a source article is updated, the change does not propagate to its replicated articles. This results in inconsistent metadata, especially when articles are replicated across different categories. We would like to update the SEO title of the replicated articles. Thank you.

Currently, we can select only 20 articles in one stretch (20 articles on the screen), we want to use this AI feature for all the published articles in one click.

Customers are looking for the <link rel="alternate" hreflang="x-default" href="" /> tag within our website's HTML structure. This tag plays a major role in SEO, helping search engines understand which version of a webpage should be served to users when no specific language or regional version is available.

We are raising a feature request on behalf of the customer (M Babajan). The customer wants the Canonical URL to be present regardless of the number of languages and workspace. Currently, when there is only one language, the canonical tags are not visible because there is only one URL directing to the article. Therefore, the customer, who uses only one language, desires to implement the canonical tag for all articles. Some SEO tools indicate that there is a lack of canonical tags across their entire knowledge base site.