SEO optimization

Prerequisites

• You must publish your website at least once before SEO files are generated. The system creates llms.txt, sitemap.xml, and robots.txt during the publish process.

• In the website management console, click SEO Optimization. The SEO optimization page contains tabs for AI Indexing, Sitemap, Crawler protocol, and Site Verification Files.

Quick start

The following workflow describes the typical process for SEO optimization:

1. Publish your website. The system automatically generates llms.txt, robots.txt, and sitemap.xml.

2. On the SEO optimization page, review the content of each file and confirm that it meets your expectations.

3. Wait approximately 5 minutes after the publish, and then verify that the files are accessible on your production URL.

4. To submit your site to a webmaster platform such as Google or Bing, upload the verification file that the platform provides on the Site Verification Files tab.

5. To customize the content of llms.txt, robots.txt, or sitemap.xml, upload your own file to override the system-generated version.

Automatic maintenance

The system maintains three SEO files on each publish:

• llms.txt — Fully reviewed and regenerated on each publish.

• robots.txt — Updated automatically after a publish.

• sitemap.xml — Generated automatically after a publish.

  When your website content changes, publish the website again to update the file content. For example, if you add a page, llms.txt and sitemap.xml automatically include the new page after the next publish.

AI indexing (GEO)

llms.txt is a standard file that provides information about your website to AI search platforms. The system generates and maintains this file automatically on each publish.

To view and customize llms.txt

1. On the AI Indexing tab, review the preview of the system-generated llms.txt content.

2. To use your own version, upload a file in the upload area. You can drag and drop the file, paste its content, or select the file.

3. After the upload succeeds, the system always uses your uploaded version.

Sitemap (sitemap.xml)

After you publish the website, the system automatically generates sitemap.xml. The indexed scope stays consistent with the public routes of the website: only publicly accessible pages are indexed.

After the publish, you can view the file content by visiting your site domain followed by /sitemap.xml. To use your own version, upload a custom file in the upload area to override the system-generated version. After the upload succeeds, the system always uses your uploaded version.

Crawler protocol (robots.txt)

After you publish the website, the system automatically generates robots.txt with the following default content:

User-agent: *
Allow: /

This default configuration allows all search engine crawlers to crawl all pages of the website. To restrict crawling of specific pages, upload a custom robots.txt file in the upload area to override the system-generated version. After the upload succeeds, the system always uses your uploaded version.

Site verification files

The Site Verification Files tab manages two types of files:

• Ownership verification files for webmaster platforms — When you submit your site to a webmaster platform such as Google or Bing, the platform requires you to place a specified verification file in the root path of the website to confirm site ownership.

• Other root path files — Files that must be placed in the root path of the site, such as favicon and manifest files.

  Uploaded files are accessed by their original file names. The file name serves as the access path. For example, after you upload verify.html and the file takes effect, you can access it at your site domain followed by /verify.html.

The quota for site verification files is 10. The page shows the number of files that you have used, such as 1/10.

To upload a site verification file

1. On the Site Verification Files tab, click the upload area.

2. Upload the file by pasting its content or by selecting the file.

3. After the upload succeeds, the page shows an uploaded message. The file appears in the list with its access path, such as /verify.html, and its file size.

4. After you publish the website, follow the instructions of the webmaster platform to verify on the production address that the file is accessible.

Usage notes

• Development preview versus production environment — sitemap.xml is directly accessible in the development preview environment. In contrast, llms.txt, robots.txt, and site verification files are produced only in the production environment. The development preview environment does not provide them, and requests to these addresses return the website page itself. After you publish the website, verify that the files take effect on the production URL.

• Effective time — SEO files take approximately 5 minutes to take effect after a publish. If the updated content is not immediately visible, wait and try again.

FAQ

Why does the development preview show the website page when I access robots.txt or llms.txt?

The development preview environment does not serve robots.txt or llms.txt. Requests to these addresses return the website page itself. This is expected behavior. Wait approximately 5 minutes after the publish, and then verify the file content on the production URL.

Why does the sitemap subpage show that no sitemap is generated, while sitemap.xml returns content?

In the development preview environment, accessing sitemap.xml returns the content of the development environment, which can differ from the production version shown on the sitemap subpage. Use the content of the production environment after the publish.

Do I need to update the SEO files manually after I add a page?

No. Publish the website again, and the files automatically include the new page.