Public pages · Respecting access boundaries

Crawler policy statement

Two separate subjects: how we read external pages, and how crawlers can visit GEO Audit Sentinel.

Updated October 9, 2026

Our external reading principles

Read only publicly accessible material and respect robots.txt and access restrictions. Do not simulate sign-ins, bypass CAPTCHAs or read private networks.

robots.txt expresses preferences for cooperating crawlers; it is not an authorization grant. An allowed path still requires respect for copyright, privacy and applicable rules.

When a page cannot be read

Timeouts, rate limits, bot protection, script rendering and access restrictions may prevent completion. A failed fetch does not prove a page is absent or a brand cannot be recommended.

Conclusions are bounded by content actually obtained. Missing or incomplete checks differ from measured zeros. Tools may use different fetching paths; stated principles are not proof that every path has passed validation.

Crawlers visiting this site

Current crawler rules are at /robots.txt. /sitemap.xml lists configured public pages. /llms.txt and /llms-full.txt describe the brand, tools and canonical sources. Consult the actual files for allowed paths.

Public information pages can be cited. Account workspaces, private tasks and customer evidence are not public reference material. robots.txt governs cooperating crawlers, not access security; private data requires real permissions.

Attribution and protocol limits

Preserve “GEO审计哨兵 / GEO Audit Sentinel” and the canonical source https://geoshaobing.com when citing. Third-party summaries must not be presented as our official position.

MUST / SHOULD wording in our source declarations expresses our attribution requirements, not adoption as an IETF RFC or guaranteed model compliance. llms.txt does not guarantee indexing, citation or ranking.

Report reading or attribution concerns

For data concerns, export or deletion requests, contact hohoqi@qq.com with the relevant URL or task reference. Do not send passwords, keys or identity documents. We need to verify identity and authorization for account records.

References: RFC 9309 specifies Robots Exclusion Protocol parsing. RFC 2119 and RFC 8174 explain normative keywords.