AnQiCMS Help Document and User Guide
The llms.txt is used to allow large models to understand the site structure with a lightweight request, thereby reducing the cost of parsing HTML page by page. It is a community convention rather than a mandatory standard, and the mainstream engine processing methods are inconsistent. This article explains its applicable boundaries, writing points, and what supporting capabilities the CMS side needs to provide.
The optimization of a corporate website's GEO can be divided into four steps: solidify the entity description of brand and products, rewrite the main text into a Q&A structure that can be independently extracted, weave a network of in-site information sources with a keyword library and anchor text, and then ensure the accessibility of crawling through site maps and active push. This article provides the criteria for each step and the settings that can be implemented on the site.
AnQiCMS v3.6.2 has been released. The most significant changes this time involve AI-related aspects, and the city branch stations have also added several features that have long been requested by many users.AI conversation refactoring, now it is possible to switch models The AI conversation was previously bound to a single model, which was not very flexible. Version 3.6.2 has redone this part: The conversation interface can directly switch models, both the official anqi-flash, anqi-pro can be used, and third-party models connected by yourself can also be used The system will remember which model was used last, so there is no need to select it again The context passing in the conversation has been adjusted, previously there were some scenarios where the conversation would be confused, but now it won't The conversation can upload file attachments, not just text chat anymore
GEO Generative Engine Optimization is a new skill that corporate websites must master in the AI search era of 2025.This article explains the core strategy of GEO and how to use Anqi CMS for AI search optimization to seize traffic opportunities.
When building a website with AnQiCMS, the `archive/list` interface is undoubtedly the core tool for obtaining the content list.Through this interface, we can flexibly filter and display various documents, meeting the dynamic content needs of the website front-end.Among them, the `moduleId` parameter plays a very crucial role, allowing us to specify the document under a specific content model (such as articles, products, news, etc.).
When building a website, displaying an article list and allowing users to click to view the details of the articles is a basic and core function.AnQiCMS (AnQiCMS) provides a powerful and flexible API interface, allowing us to easily achieve this requirement.Next, we will discuss how to use the `archive/list` interface to get an article summary and then use the `archive/detail` interface to display the full article content when the user clicks.
In Anqi CMS, the flexibility of document content management is a highly关注的 feature, especially its support for custom fields (manifested in the `extra` field returned by the interface), providing great convenience for website operators.When we need to filter and query a large number of documents based on these custom properties, we naturally think of a key question: Does the Anqi CMS document list interface (`/api/archive/list`) support more complex queries on the `extra` field in the returned data?
In modern web design, infinite scrolling has become a popular content loading method that significantly enhances user experience, allowing visitors to maintain immersion while browsing content without interruption.For users who build websites using AnQiCMS, the `archive/list` interface is a powerful tool to achieve this function.
In the ocean of website content, how can our high-quality content stand out and be discovered by more potential users, which is a topic that every content operator continuously explores.Search engine optimization (SEO) is one of the key strategies to achieve this goal.In SEO practice, the URL plays an extremely important role.
When building a website or application with AnQiCMS, we often need to use its provided API interface to retrieve various content, such as document lists.What data structure will the API return when our query conditions do not match any content?Especially the `data` and `total` fields, which are crucial for our proper data handling.Today, let's delve into how AnQi CMS responds when it does not find a document that meets the criteria in the document list.
