---
title: 关于安企CMS
---
---
title: 安企CMS授权价格-安企CMS企业版价格
---
---
title: 谷歌推送助手使用帮助
---
Google Indexing API 是Google 提供的的URL推送接口。 它允许网站管理员在添加、删除或更改某些网站元素、页面或内容时通知搜索引擎。 以这种方式添加的 URL 可以快速的告知 Google，提示 Google 抓取页面并快速索引新元素 - 这可以让您的网站流量增加并提高搜索结果排名。
这就是为什么这真的值得付出额外的努力。
- 排名更快（对于时间敏感的内容尤其重要）
- 增加您在竞争对手中排名的机会
- 保持搜索结果最新以获得更高质量的用户流量
使用这种方法，您可以通过确保您的网站被抓取并有机会在他们的网站之前排名，从而在竞争中领先一步，这对于时间敏感且具有竞争力的内容来说非常重要。
使用 Google Indexing API 的门槛曾经很高，但现在您只需要跟着下面的步骤，您将很容易的使用上 Google Indexing API 功能，并可以加速的提升您的网站排名！所以，事不宜迟——让我们直接进入设置步骤吧！
**前置条件：您得有Google账号，且拥有Google Search Console的控制权。**
## 创建 Google Indexing API 项目
快捷访问地址：[https://console.cloud.google.com/projectcreate](https://console.cloud.google.com/projectcreate)
在出现的界面上输入项目名称，需要填写英文名称，然后点击创建按钮完成创建。
创建完成后会来到项目页面，如果你有多个项目，则这里可能不是显示刚创建的项目，则需要点击顶部的项目名称下拉框，来选择刚创建的项目。
选择刚创建的 Google Indexing API 的项目后，您将进入以下页面，通过点击【转到项目设置】链接，进入 IAM 和管理。你也可以通过点击页面左上角按钮展开左侧菜单，然后点击【IAM 和管理】。
在这个界面中，点击【服务账号】菜单，来到服务账号界面，然后点击【创建服务账号】按钮。
在创建服务账号界面中，输入服务账号名称，并填写服务账号说明。
**复制电子邮件地址，因为您稍后会需要它。**
然后点击【创建并继续】按钮，完成账号的创建。
接着在下一步的操作中，完成向此服务账号授予对项目的访问权限。
您需要将角色更改为“ Owner”。
如上所示将角色设置为Owner后，务必单击【继续】以保存更改。第3步“向用户授予访问此服务账号的权限”不需要管，最后点击【完成】完成创建账号即可。
然后，来到账号管理界面，在这里可以下载包含您的API密钥的文件。在此，只需单击“操作” 列中的三个垂直点，然后选择“管理密钥”，如下所示：
进入下面的页面后，单击【添加密钥】，然后选择【创建新密钥】选项，如下所示：
在弹窗中出现提示时选择默认的JSON格式，然后单击【创建】：
单击“创建”后，.json 文件将自动下载到本地电脑中，这意味着您已成功创建API密钥并可以继续下一步。
## 启用 API 和服务
在 Google Indexing API 项目页面，点击页面左上角菜单，展开左侧菜单，然后点击【API和服务】，然后点击【库】，来到 API 库页面。
在搜索框中搜索 indexing api，然后选择 Web Search Indexing API:
在产品详情中，点击启用按钮，完成启用操作。
至此，你就可以使用 Google Indexing API 了。
## 将服务帐号添加为您的Google Search Console资源的所有者
如开始的提示，您需要使用Google Search Console注册并验证您的网站（如果您还没有这样做），这非常简单，这里不再做说明。
打开Google Search Console，地址：\[[text](https://search.google.com/search-console)]([https://search.google.com/search-console](https://search.google.com/search-console))，在左侧选择您的资源（如果出现提示），然后单击底部附近的设置：
点击用户和权限：
点右上角的【添加用户】按钮，在弹出的对话框中，输入刚才复制的电子邮件地址，权限选择拥有者。
您现在应该会看到列为新所有者的服务帐户。
您可以跨多个站点使用单个项目、服务账号和JSON API Key，只需确保将服务账号添加为 Search Console 中所有站点的所有者。
> 重要提示：如果你要在不同的网站使用前面申请的JSON API Key，就务必在Search Console中对应的每一个网站重复执行服务帐号添加为拥有者的操作。
## 下载并使用 谷歌推送助手
下载和软件授权请联系微信：wangzhenglei83 手机号：13613852792
运行 googleindex.exe，在使用推送任务之前，你需要先设置 代理IP。
点击推送任务，新建任务，在弹出的窗口中，填写Sitemap地址，如果网站没有Sitemap，填网址也行，它会自动生成Sitemap，但最好是填写Sitemap地址。选择AccountJson，这个Json就是刚才下载的那个Json文件。填写每天推送数量，这个数量有一定的额度限制，根据实际限制填写。默认是200。
这样就完成了任务添加操作，现在你可以在结果中查看推送结果了。
---
title: AnQiCMS授权查询
---
---
title: ANQICMS 隐私政策
---
生效日期：2025年07月06日
### 一、信息收集范围
1. 用户主动提交信息：包括但不限于注册时的姓名、联系方式、账户凭证等
2. 自动采集数据：通过Cookies和日志文件记录IP地址、设备信息、浏览行为等
3. 第三方共享信息：与支付网关、社交媒体等合作方必要的数据交互
### 二、信息使用方式
- 提供并优化核心服务功能
- 安全验证和风险控制
- 通过统计分析改进产品体验
- 在法律要求时配合监管机构
### 三、数据保护措施
1. 采用TLS/SSL加密传输技术
2. 敏感信息存储于隔离的安全服务器
3. 定期进行系统安全审计
4. 员工访问权限分级管理制度
### 四、用户权利保障
- 通过账户设置查阅、修改个人信息
- 提交书面申请删除非必要留存数据
- 通过 privacy@anqicms.com 行使投诉权
### 五、政策更新机制
重大变更将通过站内公告或邮件通知，持续使用服务视为接受修订条款
### 六、未成年人保护
16周岁以下用户需监护人同意使用服务
---
title: AnQiCMS 服务条款
---
最后更新：2025年07月06日
### 一、服务说明
#### 服务内容
提供基于CMS系统的网站建设、内容管理及相关技术支持
服务范围以官网公示功能模块为准
#### 服务变更
保留因产品升级暂停特定功能的权利，重大变更将提前30日公告
### 二、用户义务
禁止利用服务从事违法活动
不得对系统进行逆向工程或破解授权限制
账户信息需确保真实有效
### 三、知识产权
平台提供的模板、代码等资源均标注授权范围
用户上传内容需确保不侵犯第三方权益
### 四、免责声明
不对因不可抗力导致的服务中断承担责任
用户自行备份数据，系统故障导致损失最高赔偿当月服务费
### 五、合约终止
用户可随时申请注销账户
平台有权终止违规用户服务且不予退款
### 六、争议解决
本协议解释权归ANQICMS所有，争议协商不成应向平台所在地法院诉讼
### 七、联系方式
客服邮箱：legal@anqicms.com
受理时间：工作日9:00-18:00（北京时间）
---
title: License
---
GNU AFFERO GENERAL PUBLIC LICENSE
Version 3, 19 November 2007
Copyright (C) 2007 Free Software Foundation, Inc.
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU Affero General Public License is a free, copyleft license for
software and other kinds of works, specifically designed to ensure
cooperation with the community in the case of network server software.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
our General Public Licenses are intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
Developers that use our General Public Licenses protect your rights
with two steps: (1) assert copyright on the software, and (2) offer
you this License which gives you legal permission to copy, distribute
and/or modify the software.
A secondary benefit of defending all users' freedom is that
improvements made in alternate versions of the program, if they
receive widespread use, become available for other developers to
incorporate. Many developers of free software are heartened and
encouraged by the resulting cooperation. However, in the case of
software used on network servers, this result may fail to come about.
The GNU General Public License permits making a modified version and
letting the public access it on a server without ever releasing its
source code to the public.
The GNU Affero General Public License is designed specifically to
ensure that, in such cases, the modified source code becomes available
to the community. It requires the operator of a network server to
provide the source code of the modified version running there to the
users of that server. Therefore, public use of a modified version, on
a publicly accessible server, gives the public access to the source
code of the modified version.
An older license, called the Affero General Public License and
published by Affero, was designed to accomplish similar goals. This is
a different license, not a version of the Affero GPL, but Affero has
released a new version of the Affero GPL which permits relicensing under
this license.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU Affero General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Remote Network Interaction; Use with the GNU General Public License.
Notwithstanding any other provision of this License, if you modify the
Program, your modified version must prominently offer all users
interacting with it remotely through a computer network (if your version
supports such interaction) an opportunity to receive the Corresponding
Source of your version by providing access to the Corresponding Source
from a network server at no charge, through some standard or customary
means of facilitating copying of software. This Corresponding Source
shall include the Corresponding Source for any work covered by version 3
of the GNU General Public License that is incorporated pursuant to the
following paragraph.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the work with which it is combined will remain governed by version
3 of the GNU General Public License.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU Affero General Public License from time to time. Such new versions
will be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU Affero General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU Affero General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU Affero General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
Copyright (C)
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published
by the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License
along with this program. If not, see .
Also add information on how to contact you by electronic and paper mail.
If your software can interact with users remotely through a computer
network, you should also make sure that it provides a way for users to
get its source. For example, if your program is a web application, its
interface could display a "Source" link that leads users to an archive
of the code. There are many ways you could offer source, and different
solutions will be better for different programs; see section 13 for the
specific requirements.
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU AGPL, see
.
---
title: about us
---
tell me some thing
---
title: 安企CMS下载
---
---
title: 在线演示
---
---
title: 安企商城版
---
---
title: 内容运维回收站定时发布和备份怎么配置
---
---
title: 企业官网SEO配置要点：伪静态Sitemap和主动推送怎么组合
---
---
title: 批量导入与定时发布：高效内容运营的自动化工具
---
---
title: 内容安全防护：敏感词过滤、防采集与reCAPTCHA的组合策略
---
---
title: AnQiCMS的内容采集功能：从其他网站自动抓取内容的合规实践
---
---
title: 全站替换工具与水印管理：AnqiCMS 的批量运维效率提升技巧
---
---
title: 内容采集与批量导入：AnQiCMS 如何从 ZIP、Excel 与其他网站自动聚合内容
---
---
title: 宝塔面板一键部署 AnQiCMS：从 Docker 镜像到 8001 端口的完整流程
---
---
title: 百度主动推送与 Sitemap 配置指南：新站快速收录的实操步骤
---
---
title: 锚文本管理与关键词库：站内 SEO 的精细化运营策略
---
---
title: 伪静态 URL 与 301 重定向：企业 SEO 的基础设施配置指南
---
---
title: SEO 自动化链路：伪静态、Sitemap、主动推送一站式配置
---
---
title: 多站点多语言CMS怎么管理企业多个品牌网站
---
---
title: 定时发布功能如何规划内容上线节奏
---
---
title: 备份与恢复功能如何保障数据安全
---
---
title: 全站替换工具如何批量更新关键词和链接
---
---
title: Docker与宝塔面板：AnQiCMS的三种部署方式对比
---
---
title: 现代AI写作工具集成CMS从初稿生成到内容润色全流程
---
---
title: 构建能在2026年真正排名的AI内容自动化工作流五步法
---
---
title: 多站点多语言管理实战：AnQiCMS配置与运营指南
---
---
title: CMS安全防护清单：JWT认证与防采集干扰码的实战部署
---
---
title: 一键部署AnQiCMS：Docker镜像与宝塔面板实操
---
---
title: 定时发布与多版本：内容工作流的自动化管理
---
---
title: 数据采集成熟度：从外部采集到结构化知识库
---
---
title: 多语言站点搭建指南：整页HTML翻译与SEO本地化
---
---
title: 服务器换 IP 或接入 CDN 之后，解析、证书和收录按什么顺序复查
---
---
title: 内容没改页面还是慢，缓存头的 max-age 和 s-maxage 先查哪个
---
---
title: 全站替换改了栏目名称之后，锚文本和伪静态规则要不要跟着动
---
---
title: 页面改了用户却看到旧版本，从缓存清发到验证按什么顺序排查
---
---
title: robots.txt 里的 Disallow、星号和美元符号分别是什么约定
---
---
title: 在 robots.txt 里写 nofollow 其实不生效，标准到底认哪些字段
---
---
title: 向百度推送接口提交链接后，返回的 remain 和 not_valid 字段怎么读
---
---
title: 刚发的页面引擎迟迟不抓，站点地图和 IndexNow 各管哪一段
---
---
title: 站点地图单文件上限是多少，URL 过万时怎么拆成索引文件
---
---
title: 企业官网用 Docker 部署，端口和数据备份要提前准备什么
---
---
title: 新内容怎么更快进搜索引擎，站点地图和主动推送各管什么
---
---
title: Robots.txt 没写错却漏抓页面，先排查这三处
---
---
title: 改了伪静态规则后已收录的老链接会不会断，怎么兜底
---
---
title: 老站重构搬历史内容，批量导入和 301 重定向先做哪一步
---
---
title: 两个人维护的企业官网，容器部署和面板部署怎么选
---
---
title: 用 Excel 批量导入文章，模板字段怎么填才不丢内容
---
---
title: 程序默认监听 8001 端口，反向代理和域名接入怎么配
---
---
title: 内容审核拦下发布之后，被拦原因怎么查、怎么改
---
---
title: 新站上线第一天的运维清单：端口监听、备份任务和日志各配在哪一步
---
---
title: 升级公告要求备份文件、数据库和自定义模板，三类备份各验什么才算稳妥？
---
---
title: 小版本升级后旧版表格文件格式不再支持，站点的内容导入流程会断在哪几环？
---
---
title: 删掉的正式文档还能从回收站找回，找回之前要不要先备份一次
---
---
title: 换域名或改栏目名之后，站内旧链接怎么批量换掉，改前先留什么
---
---
title: 站点地图放在子目录还是根目录，能覆盖的地址范围由什么决定
---
---
title: 备份里要不要连静态文件一起带走，恢复演练该验哪几项
---
---
title: 批量导入用压缩包还是表格，两种来源各自适合什么场景
---
---
title: 站点地图要不要把翻译页和原文页一起列进去
---
---
title: 关键词库里的词在正文反复出现，锚文本会不会堆得太密
---
---
title: 文章改了标题之后地址要不要跟着变，已收录的旧链接怎么处理
---
---
title: 内容模型加一个字段和改一个字段的成本差在哪
---
---
title: 容器化部署之后，基础镜像里的 Web 服务器补丁由谁跟进
---
---
title: 伪静态落到 Web 服务器时，按顺序找文件的指令回退目标怎么写
---
---
title: 定时发布和批量导入一起用时，内容排期要注意什么
---
---
title: 预览版要不要装到生产站，Release Candidate 和正式版怎么选
---
---
title: 表单和评论被机器人灌水，除了验证码还能做哪几层
---
---
title: 站点地图里的最后修改时间怎么填，才容易被采信
---
---
title: 站点地图单个文件能放多少条地址，超出上限要怎么分片
---
---
title: 给外部脚本加完整性校验，为什么标签里还要显式写跨域属性
---
---
title: 内容安全策略先只上报不拦截，看什么再决定真的拦下来
---
---
title: 上传大附件被挡在413，报错为什么在浏览器里看不明白
---
---
title: 删掉的文章和隐藏的栏目分别返回什么码，统一压成404会带来什么后果
---
---
title: 定时发布的时间带了时区差，前台排序和推送会怎么乱
---
---
title: 网站前面挂了代理，日志里记到的客户端地址为什么全是代理
---
---
title: 容器里跑建站程序时，程序端口和网关端口怎么对上
---
---
title: 线上体验站的后台入口在哪里，试用时该核哪几项能力
---
---
title: 官网推荐的运行环境版本和最低能跑的版本差两档，按哪档配
---
---
title: 上传被拒返回 413，先改程序限制还是先改网关限制
---
---
title: 换完证书后页面样式缺一半，https 页里的 http 外链要怎么清
---
---
title: 从 HTTP 换成 HTTPS，站内地址和跳转要改哪几处
---
---
title: 证书九十天有效，自动续期该配在哪一步
---
---
title: 压缩该在程序里做还是 Web 服务器里做，静态文件要不要预压缩
---
---
title: 静态资源加了版本号还命中旧缓存，缓存头该怎么写
---
---
title: 备份要不要把上传的图片和静态文件一起带走
---
---
title: 自动更新开着时，大版本和小版本的默认行为差在哪
---
---
title: 换服务器或换接入商时，备案号要怎么跟着处理
---
---
title: 面板一键部署和命令行部署，日常维护的动作差在哪
---
---
title: 上了反向代理之后访客来源地址记不准，该补哪个请求头
---
---
title: 后台登录口被反复尝试，除了换访问地址还能做什么
---
---
title: 打开慢该先看程序还是先看服务器，三步分锅怎么做
---
---
title: AI 爬虫的抓取规则要不要单写，匹配优先级怎么算
---
---
title: 站点地图的 lastmod 写页面修改日还是生成日
---
---
title: 二十天里三个版本，安全补丁的跟进窗口怎么排
---
---
title: 导航、单页和友情链接的定期维护，漏掉会带来什么后果
---
---
title: 栏目改名或批量换链接，用全站替换怎么避免漏改和错改
---
---
title: 评论垃圾突然变多，验证码、内容审核和频率控制各管哪一段
---
---
title: 站内锚文本怎么配才不像堆砌，关键词库和投放范围怎么定
---
---
title: 网站被插入恶意代码后的处置顺序，先断入口还是先清文件
---
---
title: 网站依赖的PHP大版本还在安全维护期里吗，三步自查怎么做
---
---
title: 宝塔面板部署和Docker镜像部署，建站运维差在哪
---
---
title: 从WordPress迁移内容到独立CMS，导出字段和链接怎么接
---
---
title: 网站改版后旧链接的301跳转怎么配才不会丢位次
---
---
title: 文章状态、回收站与备份：CMS日常运维容易漏的三处
---
---
title: 网站收录慢怎么排查：Sitemap生成与主动推送的配置顺序
---
---
title: 安企CMS MCP 功能详解：内置 108 个工具，让 AI 直接帮你管理网站
---
---
title: 安企CMS的安装-常见安装问题排查
---
---
title: 安企CMS 无法登录后台 解决方案
---
---
title: 在服务器上安装多个安企CMS的方法
---
---
title: 安企CMS(AnQiCMS)默认小程序使用说明
---
---
title: 安企CMS如何在网页正确使用Markdown以及显示数学公式和流程图
---
---
title: 安企CMS(AnqiCMS)在线演示站点
---
---
title: AnqiCMS 开发计划
---
---
title: AnqiCMS 常见问题汇总
---
---
title: 认识 AnqiCMS
---
---
title: 为什么在外部编辑器修改模板不生效
---
---
title: 模板的标签和使用方法
---
---
title: 模板制作的目录和模板
---
---
title: 模板制作的一些基本约定
---
---
title: 网站导航设置使用帮助
---
---
title: 首页TDK设置使用帮助
---
---
title: 联系方式设置使用帮助
---
---
title: 内容设置使用帮助
---
---
title: 全局功能设置使用帮助
---
---
title: 后台功能介绍
---
---
title: 内容模型使用帮助
---
---
title: 文档标签使用帮助
---
---
title: 文档分类使用帮助
---
---
title: 添加文档使用说明
---
---
title: 文档管理使用说明
---
---
title: 图片资源管理使用帮助
---
---
title: 页面管理使用帮助
---
---
title: 多语言站点功能使用教程二：单站翻译插件架构多语言方式
---
---
title: 多语言站点功能使用教程一：独立多站点架构多语言方式
---
---
title: 安企CMS多语言站点功能介绍
---
---
title: AnqiCMS(安企CMS)如何使用滴滴友链自动上链功能
---
---
title: 链接推送使用帮助
---
---
title: 伪静态规则使用帮助
---
---
title: 安企CMS搜索页面不同模型使用自定义模板的方法
---
---
title: 获取产品SKU标签
---
---
title: 文档参数筛选标签
---
---
title: 文档参数标签
---
---
title: 相关文档标签
---
---
title: 下一篇文档标签
---
---
title: 上一篇文档标签
---
---
title: 文档/产品详情标签
---
---
title: 文档列表标签
---
---
title: 城市分站详情标签
---
---
title: 城市分站列表标签
---
---
title: 单页详情标签
---
---
title: 单页列表标签
---
---
title: 分类详情标签
---
---
title: 分类列表标签
---
---
title: Tag详情标签
---
---
title: Tag文档列表标签
---
---
title: 文档Tag列表标签
---
---
title: 文档模型详情标签
---
---
title: 首页 Banner 列表标签
---
---
title: 统计代码标签
---
---
title: 面包屑导航标签
---
---
title: 导航列表标签
---
---
title: TDK标签
---
---
title: 联系方式标签
---
---
title: 系统设置标签
---
---
title: Json-LD 自定义调用标签
---
---
title: 自定义内容标签
---
---
title: 用户分组详情标签
---
---
title: 用户详情标签
---
---
title: 留言验证码使用标签
---
---
title: 友情链接标签
---
---
title: 分页标签
---
---
title: 留言表单标签
---
---
title: 评论列表标签
---
---
title: 格式化价格标签
---
---
title: 阻止模板引擎解析标签内的内容
---
---
title: 获取多语言站点列表标签
---
---
title: 模板文字翻译标签
---
---
title: 生成随机文本
---
---
title: 通用标签-if逻辑判断标签
---
---
title: 通用标签-算术运算标签
---
---
title: 通用标签-移除逻辑标签占用行
---
---
title: 通用标签-for循环遍历标签
---
---
title: 格式化时间戳标签
---
---
title: 通用标签-定义变量赋值标签
---
---
title: 更多过滤器
---
---
title: 其他辅助标签
---
---
title: 过滤器：获取图片的缩略图
---
---
title: 过滤器：渲染Markdown内容为HTML
---
---
title: 过滤器：将变量转换成JSON输出
---
---
title: dump过滤器：打印变量的结构类型和值
---
---
title: 或与非三种状态
---
---
title: 长文本自动换行
---
---
title: 计算字符串中单词数量
---
---
title: 查找并将文本中的url字符串解析成可点击的a标签
---
---
title: url参数转义
---
---
title: 对字符串或html代码进行截取并添加...
---
---
title: 将任意值格式化成字符串输出
---
---
title: 字符串按指定分隔符切割成数组
---
---
title: 截取符串、数组中指定位置的元素
---
---
title: 将HTML代码解析输出，不转义
---
---
title: 移除html代码中的html标签
---
---
title: 返回字符串、数组中的随机一个字符、值
---
---
title: 单词的复数形式
---
---
title: 将手机数字键盘字母转换为数字
---
---
title: 将多行文本按换行符转换成html标签
---
---
title: 获取字符串、数组、键值对的长度
---
---
title: 将数组按指定拼接字符链接成字符串
---
---
title: 转换数字字符串为浮点数或整数
---
---
title: 获取数字中指定位置的数字
---
---
title: 浮点数保留指定位数小数点
---
---
title: 字符串或数组第一个值或最后一个值
---
---
title: 将一行文字按空格拆分成数组
---
---
title: 将字符串、js代码中的特殊字符转义
---
---
title: 判断一个数字是否可以作为被除数
---
---
title: 数字或字符串、对象默认值设置
---
---
title: 将时间值按指定格式显示
---
---
title: 移除字符串任意位置中的指定字符
---
---
title: 将字符串按指定长度格式居中、靠左、靠右显示
---
---
title: 将英文字符串字母转换为大写或小写
---
---
title: 预定义字符前添加反斜杠
---
---
title: 数字或字符串相加
---
---
title: 指定重复多次输出字符串
---
---
title: 替换字符串中某个特定关键词为另一个关键词
---
---
title: 在模板中定义数组
---
---
title: 获取某个关键词在一行字符串或数组中出现的位置
---
---
title: 过滤器：将一行文字按空格拆分成数组
---
---
title: 计算某个关键词在一行字符串中出现的次数、数组中出现次数
---
---
title: 删除字符串所有前导和尾随空格、特定字符
---
---
title: 判断文字、数组是否包含指定关键词
---
---
title: AnQiCMS MCP Server实战：让Claude和Cursor直接操作你的CMS
---
---
title: MCP Server 如何让外部 AI 客户端接入 AnQiCMS
---
---
title: MCP Server 与外部 AI 客户端：AnQiCMS 如何被 Claude、Cursor 接入调用
---
---
title: MCP 协议接入指南：让 Claude、Cursor 直接操作你的 CMS
---
---
title: MCP Server实战：将AnQiCMS接入Claude和Cursor
---
---
title: 公开接口能读写站内哪些能力，接口文档按什么分类查
---
---
title: 批量导入内容时按标题查重，接口返回的字段该怎么读
---
---
title: 官网要对接外部系统，接口文档里的认证方式和字段约定先确认哪个
---
---
title: 公开接口被刷时，限速、验证码和暴露范围各挡哪一段
---
---
title: 外部 AI 客户端接入站内 MCP，鉴权和回合级审批分别怎么配
---
---
title: 接口批量导入内容时能带上哪些字段，哪些状态要靠后配
---
---
title: 用接口批量入库文章时，分类、标签和定时发布分别由哪些字段决定？
---
---
title: 外部系统批量入库前想先按标题查重，接口侧要确认哪几件事
---
---
title: 对外内容接口要不要附一个纯文本版本，字段该怎么约定
---
---
title: 重复提交的写接口要怎么防重，幂等键放在请求头还是放在业务字段里
---
---
title: 附件用编码内容通过接口上传时，体积和校验该注意什么
---
---
title: 推送接口要求把密钥文件放在站点根目录，公开可读有没有风险
---
---
title: 内容通过接口对外可读时，哪些数据必须挡住
---
---
title: 后台高频接口能力有哪几类，公开接口文档该写清什么
---
---
title: 批量导入时同名文章怎么处理，按标题查重该放在哪一步
---
---
title: 让外部AI客户端连进后台之前，先把接口权限收在哪三层
---
---
title: 批量导入文章：Excel、压缩包和接口三种方式怎么选
---
---
title: CMS里的AI Chat、技能与MCP接入分别能做什么
---
---
title: 公共 HTTP 头定义
---
---
title: API 概览
---
---
title: 十、商城站点API调用示例
---
---
title: 九、博客站点API调用示例
---
---
title: 八、实践
---
---
title: 七、调试与测试
---
---
title: 六、认证与授权
---
---
title: 五、响应数据结构
---
---
title: 四、请求参数详解
---
---
title: 三、API 部分接口分类详解
---
---
title: 二、API 基础结构
---
---
title: 一、快速入门
---
---
title: 获取产品SKU接口
---
---
title: 检查是否收藏接口
---
---
title: 移除收藏接口
---
---
title: 添加收藏接口
---
---
title: 获取收藏列表接口
---
---
title: 验证文档密码接口
---
---
title: 检查指定文档是否支付了接口
---
---
title: 文档发布接口
---
---
title: 获取文档参数接口
---
---
title: 获取文档参数筛选条件接口
---
---
title: 获取下一个文档接口
---
---
title: 获取上一个文档接口
---
---
title: 获取产品/文档详情接口
---
---
title: 获取文档列表接口
---
---
title: 获取标签文档列表接口
---
---
title: 获取标签详情接口
---
---
title: 获取标签列表接口
---
---
title: 获取城市分站列表接口
---
---
title: 获取城市分站详情接口
---
---
title: 获取模型详情接口
---
---
title: 获取模型列表接口
---
---
title: 获取单页列表接口
---
---
title: 获取单页详情接口
---
---
title: 获取分类详情接口
---
---
title: 获取分类列表接口
---
---
title: 页面元数据接口文档
---
---
title: 获取自定义内容接口
---
---
title: 邮件订阅接口
---
---
title: 统计页面访问数据
---
---
title: 获取多语言列表接口
---
---
title: 微信官方授权接口
---
---
title: 微信公众号服务地址接口
---
---
title: 生成小程序码接口
---
---
title: 获取首页TDK接口
---
---
title: 获取首页 Banner 列表接口
---
---
title: 调用图形验证码接口
---
---
title: 上传图片资源接口
---
---
title: 获取导航列表接口
---
---
title: 获取联系方式接口
---
---
title: 获取系统设置接口
---
---
title: 添加留言接口
---
---
title: 获取留言表单字段接口
---
---
title: 评论点赞接口
---
---
title: 发布评论接口
---
---
title: 获取评论列表接口
---
---
title: 获取友情链接列表接口
---
---
title: 获取城市列表接口
---
---
title: 获取国家省份/州列表接口
---
---
title: 获取国家列表接口
---
---
title: 地址自动补全接口
---
---
title: 获取谷歌登录跳转地址接口
---
---
title: 重置用户密码接口
---
---
title: 验证Email地址接口
---
---
title: 发送Email验证接口
---
---
title: 退出登录接口
---
---
title: 更新用户头像接口
---
---
title: 修改用户密码接口
---
---
title: 获取用户分组列表接口
---
---
title: 获取用户分组详情接口
---
---
title: 更新用户信息接口
---
---
title: 获取用户详情接口
---
---
title: 注册接口
---
---
title: 登录接口
---
---
title: 获取配送信息接口
---
---
title: 获取订单服务列表接口
---
---
title: 保存订单自定义表单接口
---
---
title: 获取订单自定义表单接口
---
---
title: 获取活动列表接口
---
---
title: 获取活动详情接口
---
---
title: 获取商品活动信息接口
---
---
title: 发表产品/订单评价接口
---
---
title: 获取产品/订单评价列表接口
---
---
title: 发送沟通定制订单信息接口
---
---
title: 获取沟通定制订单沟通信息列表接口
---
---
title: 沟通定制订单接受报价接口
---
---
title: 更新沟通定制订单接口
---
---
title: 获取沟通定制订单详情接口
---
---
title: 创建沟通定制订单接口
---
---
title: 获取沟通定制订单列表
---
---
title: 获取沟通定制订单字段接口
---
---
title: 更新购物车接口
---
---
title: 移除购物车商品接口
---
---
title: 添加购物车接口
---
---
title: 获取购物车列表接口
---
---
title: 领取优惠券接口
---
---
title: 获取我的优惠券列表接口
---
---
title: 获取可用优惠券列表接口
---
---
title: 移除愿望清单接口
---
---
title: 添加愿望清单接口
---
---
title: 获取愿望清单列表接口
---
---
title: 获取订单地址列表接口
---
---
title: 获取商品Checkout信息接口
---
---
title: 获取订单统计图表接口
---
---
title: 获取订单统计数据接口
---
---
title: 检查订单是否支付接口
---
---
title: 获取订单列表接口
---
---
title: 订单申请退款接口
---
---
title: 订单创建支付接口
---
---
title: 订单确认收货接口
---
---
title: 获取订单详情接口
---
---
title: 创建订单接口
---
---
title: 取消订单接口
---
---
title: 保存用户收货地址接口
---
---
title: 获取用户收货地址接口
---
---
title: 获取提现列表接口
---
---
title: 申请提现接口
---
---
title: 更新分销员真实姓名接口
---
---
title: 获取分销员统计信息接口
---
---
title: 获取分销订单列表接口
---
---
title: 获取分销团队列表接口
---
---
title: 获取分销员详情接口
---
---
title: 获取分销员收益列表接口
---
---
title: GraphQL API 参考
---
---
title: 查询（Queries）
---
---
title: 对象（Objects）
---
---
title: 标量（Scalars）
---
---
title: 检查文档存在接口
---
---
title: 检查友情链接是否可用接口
---
---
title: 导入图片资源接口
---
---
title: 手动更新Sitemap接口
---
---
title: 删除友情链接接口
---
---
title: 添加友情链接接口
---
---
title: 获取文档分类接口
---
---
title: 导入文档接口
---
---
title: v3.6.6修复两项高危问题后升级要注意什么
---
---
title: AnQiCMS v3.6.7 更新说明
---
---
title: AnQiCMS v3.6.6修复两项高危安全问题升级建议
---
---
title: AnQiCMS v3.6.3三大AI能力上线：可视化编辑、MCP Server与自动标签
---
---
title: AnQiCMS v3.6.5 MCP意图目录重建：回合级批量审批的新能力
---
---
title: AnQiCMS v3.6.5版本重要功能更新详解
---
---
title: v3.6.5 新增邮件订阅、留言列表、文件搜索与 base64 上传功能详解
---
---
title: v3.6.6安全更新详解：排序参数注入与凭证伪造修复
---
---
title: v3.6.6 升级当天清单：先换站点签名密钥还是先改管理员密码
---
---
title: MCP 工具层重建与邮件订阅，v3.6.5 更新记录里该看哪几项
---
---
title: 一次版本更新修掉排序参数注入和登录凭证可被伪造，密钥为什么要一起换
---
---
title: 安企CMS - AnQiCMS v3.6.6 更新日志（合并 v3.6.5）
---
---
title: AnQiCMS 2026年9月更新：AI可视化编辑器、MCP支持与多项修复
---
---
title: 安企CMS - AnQiCMS v3.6.2 更新日志
---
---
title: 安企CMS - AnQiCMS v3.6.1 更新日志
---
---
title: 安企CMS - AnQiCMS v3.6.0 更新日志
---
---
title: 安企CMS - AnQiCMS v3.5.9 更新日志
---
---
title: 安企CMS - AnQiCMS v3.5.8 更新日志
---
---
title: 安企CMS - AnQiCMS v3.5.7 更新日志
---
---
title: 安企CMS - AnQiCMS v3.5.6 更新日志
---
---
title: 安企CMS - AnQiCMS v3.5.5 更新日志
---
---
title: AnQiCMS v3.5.2 更新记录
---
---
title: AnQiCMS v3.5.0
---
---
title: AnQiCMS v3.4.8 新版发布，多语言功能全新亮相
---
---
title: 安企CMS(AnQiCMS) v3.4.1 版
---
---
title: 安企CMS(AnQiCMS) v3.3.12 版
---
---
title: 安企CMS(AnQiCMS) v3.3.10 版
---
---
title: 安企CMS(AnQiCMS) v3.3.8 版
---
---
title: 安企CMS(AnQiCMS) v3.3.6 版
---
---
title: 安企CMS(AnQiCMS) v3.3.5 版
---
---
title: 安企CMS(AnQiCMS) v3.3.4 版
---
---
title: 安企CMS(AnQiCMS) v3.3.3 版
---
---
title: 安企CMS(AnQiCMS) v3.3.0 版
---
---
title: 安企CMS(AnQiCMS) v3.2.8 版
---
---
title: 安企CMS(AnQiCMS) v3.2.6 版
---
---
title: 安企CMS(AnQiCMS) v3.2.5 版
---
---
title: 安企CMS(AnQiCMS) v3.2.4 版
---
---
title: 安企CMS(AnQiCMS) v3.2.2 版
---
---
title: 安企CMS(AnQiCMS) v3.2.0 版
---
---
title: 安企CMS(AnQiCMS) v3.1.6 版
---
---
title: 安企CMS(AnQiCMS) v3.1.5 版
---
---
title: 安企CMS(AnQiCMS) v3.1.4 版
---
---
title: 安企CMS(AnQiCMS) v3.1.0 版
---
---
title: 安企CMS(AnQiCMS) v3.0.7 版
---
---
title: 安企CMS(AnQiCMS) v3.0.6 版
---
---
title: 安企CMS(AnQiCMS) v3.0.5 版
---
---
title: 安企CMS(AnQiCMS) v3.0.0 版
---
---
title: 安企CMS(AnQiCMS) v2.5.4 版
---
---
title: 安企CMS(AnQiCMS) v2.5.1 版
---
---
title: 安企CMS(AnQiCMS) v2.3.6 版
---
---
title: 安企CMS(AnQiCMS) v2.2.9 版
---
---
title: 安企CMS(AnQiCMS) v2.2.5 版
---
---
title: 安企CMS(AnQiCMS) v2.1.9 版
---
---
title: 安企CMS(AnQiCMS) v2.1.1 版
---
---
title: 安企CMS(AnQiCMS) v2.1.0 版
---
---
title: 安企CMS(AnQiCMS) v2.0.1 版
---
---
title: 安企CMS(AnQiCMS) v2.0.0-alpha7 版
---
---
title: 安企CMS(AnQiCMS) v2.0.0-alpha5 版
---
---
title: 安企CMS(AnQiCMS) v2.0.0-alpha2 版
---
---
title: 安企CMS(AnQiCMS) v2.0.0-alpha 版
---
---
title: 安企CMS(AnQiCMS) v1.0.0-alpha 版
---
---
title: 安企CMS(AnQiCMS) v0.5 版
---
---
title: 安企CMS(AnQiCMS) v0.1 版
---
---
title: AI写作自动标签和配图在CMS里能省多少人工
---
---
title: 内容模型和自定义字段怎么设计才不返工
---
---
title: 文档状态管理：草稿、待发布与回收站的工作流设计
---
---
title: 多站点多语言管理：企业级CMS的核心能力解析
---
---
title: 敏感词过滤与内容审核：AnQiCMS 的内容安全设置详解
---
---
title: 自定义内容模型：AnQiCMS 如何灵活定义文章结构与字段
---
---
title: 微信公众号对接与分销管理：AnQiCMS 的电商与社交整合能力
---
---
title: 定时发布与回收站：AnQiCMS 的内容生命周期管理机制
---
---
title: Go 语言 CMS 性能优势解析：内存降低约 80% 背后的技术原理
---
---
title: 多站点与多语言管理：AnQiCMS 如何支撑集团化网站集群
---
---
title: AI 驱动的内容创作：AnQiCMS 智能写作与自动标签实践
---
---
title: AnQiCMS 多站点管理：一套系统运营多个品牌网站
---
---
title: CMS内置AI写作与自动标签功能如何提升内容创作效率
---
---
title: 文档回收站机制如何防止误删内容
---
---
title: reCAPTCHA验证码如何保护表单免受机器人攻击
---
---
title: 微信公众号对接与分销管理：AnQiCMS的电商扩展能力
---
---
title: AI可视化模板编辑：用自然语言直接修改网站代码
---
---
title: Rytr经济实惠的AI写作工具2026年多场景内容生成实测
---
---
title: AnQiCMS的MCP Server如何支持外部AI客户端接入
---
---
title: AI驱动的内容创作：AnQiCMS智能化工具集详解
---
---
title: Go语言CMS性能优势：内存占用降低约80%的技术原理
---
---
title: AI可视化模板编辑：非前端也能定制站点样式
---
---
title: 后台留言列表和评论审核怎么分工，未发布内容的留言谁能看到
---
---
title: 草稿、待发布和回收站之间怎么流转，误删的内容从哪里找回
---
---
title: AI 写作、自动标签、自动配图各接管哪几步，TDK 能不能一起自动化
---
---
title: 邮件提醒和邮件订阅是两个入口，通知怎么配到对的人
---
---
title: 定时发布配合草稿和待发布，把内容更新节奏排稳的用法
---
---
title: 内容采集功能很省事，防采集干扰码又是在防谁
---
---
title: 多语言站点上线，整页翻译和字段级翻译怎么选
---
---
title: 外部 AI 客户端接入 MCP 时，高危操作域默认关闭意味着什么
---
---
title: 同一套内容按用户组分级展示，权限和 VIP 分组怎么配
---
---
title: 官网表单被垃圾提交刷，验证码该加在哪些入口
---
---
title: 发布前怎么用内容审核和敏感词过滤拦住违规表述
---
---
title: 站点要不要专门给大模型准备 LLMs.txt，它解决什么
---
---
title: 关键词库和锚文本管理怎么配合，把站内内链做顺
---
---
title: 不改代码调整栏目样式，可视化模板编辑适合哪类团队
---
---
title: 内容系统里的技能是什么，和站内智能体、外部 AI 客户端什么关系
---
---
title: 图片被盗图才想起水印，该在上传时加还是展示时加
---
---
title: 企业官网接微信公众号做会员和订单，后台的用户组、财务和分销怎么配
---
---
title: 原创内容被批量抓取时，干扰码与采集功能怎么用
---
---
title: 跨境电商官网要多语言站点还是多站点，先分清两件事
---
---
title: 站点根目录的 LLMs.txt 该写什么，模型才读得懂结构
---
---
title: 文档回收站与数据备份恢复分别应对哪种误操作
---
---
title: 关键词库和锚文本管理怎么搭配，站内布局才有章法
---
---
title: AI 助手批量生成的内容，落进哪个状态再进审核
---
---
title: AI 绘画、自动标签、自动配图分别管写作流程的哪一段
---
---
title: reCAPTCHA 配了没生效，先查密钥、表单还是代理出口
---
---
title: Iris 框架和 GORM 数据层，建站者和模板开发各该看技术栈哪里
---
---
title: 防采集干扰码在访客视角长什么样，会影响正常阅读吗
---
---
title: 测量里被 AI 引擎引用最多的内容形态是排名清单页，约占全部引用的 21%，站内怎么承接？
---
---
title: 后台里的 AI 对话和一堆 AI 工具，能不能让它连着做完一件事
---
---
title: 站点要出多种语言，整页翻译和逐字段翻译怎么选
---
---
title: 把内容系统接到外部 AI 客户端时，高危操作为什么要默认关掉
---
---
title: 批量导入几千篇文档时，AI 自动标签和标题配图要不要一起开
---
---
title: 站内内容不想被整页搬走时，拦截发生在抓取层还是展示层
---
---
title: 发一篇文章时，标题关键词描述、标签和配图能一起自动生成吗
---
---
title: 表单被机器人反复提交时，验证环节加在哪一步，需要什么前置配置
---
---
title: 回收站里的文档长期不清会怎样，恢复前该确认什么
---
---
title: 多个站点共用一套模板时，样式和配置怎么分别覆盖
---
---
title: 站点说明文件真正强制的只有一个一级标题，其余能省到什么程度
---
---
title: 给大模型的站点说明文件要不要标内容时效，和定时发布怎么配合
---
---
title: 内容模型的自定义字段怎么设计，才不会做一半就得改表
---
---
title: 防采集干扰码和拒绝抓取是两件事吗，各挡在哪一层
---
---
title: 多站点共用一套后台，站点之间要隔离哪些配置和数据
---
---
title: 面向大模型的站点说明文件要写哪些内容，格式上有什么硬性要求
---
---
title: 改模板前想留一份回退，模板备份要覆盖到哪一层
---
---
title: 后台文件搜索支持两级通配后，批量改动前先怎么圈定范围
---
---
title: 站里表单接人机验证，不弹图片只按风险决定要不要勾选框，后端还要验什么
---
---
title: 下载附件时中文文件名乱码，响应头里两个文件名参数为什么要一起写
---
---
title: 接口文档已经公开了，还要不要另外给模型留一份站点说明
---
---
title: 同一套系统管多个品牌站时，域名、语言和模板怎么分开配
---
---
title: 发布时自动生成的标签和关键词库里的词会不会互相盖掉，两处怎么分工
---
---
title: 评论反垃圾和留言审核是同一件事吗，两处配置各管什么
---
---
title: 友情链接和锚文本是两套东西吗，交换链接在哪一处维护
---
---
title: 站内长尾词分散在几十篇文章里，关键词库和锚文本怎么接起来
---
---
title: 伪静态规则想换成另一套地址形式，改动会牵到哪些地方
---
---
title: 内容站开了分销，订单和财务在后台哪一处对账
---
---
title: 绑定公众号之后，粉丝身份和站内账号要不要打通
---
---
title: 新文章发布和收到留言时，邮件提醒分别挂在哪个事件上
---
---
title: 营销活动页要不要单独建内容模型，还是放在栏目里
---
---
title: 后台的站点健康检查技能跑一遍，能查出哪些影响收录的问题
---
---
title: 常见问题单独建成内容模型，问答式检索时更容易被抓到吗
---
---
title: 内容管理系统里和搜索大模型相关的模块，一次上线该开哪几项
---
---
title: 给大模型的站点说明文件放在哪个路径，站群要不要各放一份
---
---
title: 站点关键词库能不能按站点分开管，多品牌站怎么不串词
---
---
title: 后台里的 AI 工具能不能自己连着调用，哪些动作要先确认
---
---
title: 批量导入支持压缩包和表格，导入入口要不要单独加校验
---
---
title: 删掉的文章还能找回吗，回收站里保留的是哪部分内容
---
---
title: 定时发布和待发布是两个状态吗，到点自动上线怎么配
---
---
title: 多语言站点的地址怎么排，译文和原文是不是同一个域名下
---
---
title: 同一套后台管多个品牌站，站点之间哪些东西能共用
---
---
title: 后台登录状态多久失效一次，会话时长该怎么权衡
---
---
title: 草稿的预览链接会不会被抓走，预览参数该怎么收口
---
---
title: 让 AI 改模板时，改动怎么回到站点里生效
---
---
title: 备份和升级这类全站级操作，接口为什么默认不对外开放
---
---
title: 做活动落地页是用单页面还是用文章模型，后台该怎么分
---
---
title: 发布前的内容审核和敏感词过滤，分别在哪一步生效
---
---
title: 内容站要做会员分层和接单，后台要开哪几块能力
---
---
title: 加水印和防采集能不能拦住内容被拿走，该放在哪一步
---
---
title: 更新要发给订阅者时，邮件订阅列表归谁管
---
---
title: 海南 GESP | CSP 认证-信息学奥赛-椰程信奥-海南科技特长生
---
---
title: 基因检测与遗传咨询一站式服务平台 - 八方基因
---
---
title: 幺林灵（100）- 为您提供经典名言名句
---
---
title: 探索各行各业的精选网站集合 - 行业网站大全
---
---
title: 400电话办理申请
---
---
title: 亿力清洗机-YILI
---
---
title: 素雅营销-网站建设服务
---
---
title: 安企CMS多站点中默认GO项目站点迁移教程之迁入到默认Go项目站点
---
---
title: 安企CMS多站点中其它PHP项目站点迁移教程之迁入到其它PHP项目站点
---
---
title: 安企CMS多站点中其它PHP项目站点迁移教程之迁入到默认Go项目站点
---
---
title: 安企CMS多站点中默认GO项目站点迁移教程之迁入到其它PHP项目站点
---
---
title: 在Linux上使用宝塔安装安企CMS多站点教程
---
---
title: 在Linux上使用宝塔的Go项目安装安企CMS教程
---
---
title: 安企CMS怎么安装到二级目录，安企CMS安装到二级目录教程
---
---
title: 在Windows下使用域名访问安企CMS
---
---
title: 安企CMS在Windows下使用教程
---
---
title: 安企盒子TXT文章发布功能使用视频教程
---
---
title: 安企CMS在Linux服务器上的启动问题处理
---
---
title: 安企CMS在LNMP环境下安装教程
---