# LLMs.txt - ServeCloud Guidance for Large Language Models
# Version: 1.0
# Last Updated: 2025-10-23

# Purpose:
# This file provides guidance to well-behaved LLMs and crawlers about which
# parts of the website are important (primary content), which are secondary,
# and how to handle personal or dynamically-generated content.

# General policy
# - ServeCloud allows access to public content for search/indexing and helpful AI agents
# - Do NOT harvest or store personal or sensitive user data (PII)
# - Respect robots.txt rules and privacy policies

# Sections
# Each section lists URL path patterns and an importance flag.

[Primary]
# Primary content that is useful for summarization, Q&A and knowledge extraction.
# Examples: Property details, Project pages, FAQ, Help pages, Public blog posts
/
/property-detail
/project
/q-and-a
/property-area

[Secondary]
# Secondary content useful for context but lower priority (e.g., listing pages, search results)
/search
/listings
/project-archive

[Private]
# Do NOT index or cache these, and do not use them to train models.
/user
/account
/profile
/checkout
/payment

[Dynamic]
# Pages where content changes frequently or contains session-based content.
# LLMs should prefer using canonical APIs or structured data when available.
/search-results
/cart
/session

[StructuredData]
# Prefer structured data (JSON-LD, Schema.org) on these pages for canonical extraction.
/property-detail
/project-*
/blog

[Contact]
# Contact policy for LLM requests about site content
# If an LLM needs clarification, use the public Contact Form or official API.
Contact-Form: https://www.serve.co.th/contact

# Rate limits (recommendation)
# Respectful scraping / data access limits
Rate-Limit-Per-Minute: 60
Rate-Limit-Per-Hour: 3600

# Data Usage Policy
# - Public content may be used to answer user queries in the context of a session
# - Personal data must not be retained or used for model training
# - For bulk data access, request via official API or partnership