intersog.com valid

llms.txt

Purpose: Guidance for LLMs and automated agents interacting with the public content of the Intersog WordPress multisite installation. Last-Updated: 2026-03-12

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T01:23:04.372Z. Cached copy · Source on intersog.com

# llms.txt

Purpose: Guidance for LLMs and automated agents interacting with the public content of the Intersog WordPress multisite installation.
Last-Updated: 2026-03-12

Project: Intersog Websites
Primary Website: https://intersog.com
Additional Regional Website: https://intersog.ca
Owner: Intersog
Contact: https://intersog.com/contact/

## Scope
This file is shared by the current WordPress multisite installation and applies to publicly accessible content served from the domains using this shared root configuration, including:
- https://intersog.com
- https://intersog.ca

## Allowed Use
- Indexing, retrieval, search, summarization, citation, and high-level analysis of all publicly accessible pages
- Use of publicly accessible content for search/referral systems and user-triggered assistant retrieval
- Use of publicly accessible content for model training, evaluation, and improvement
- Quoting short excerpts with proper attribution and canonical URL
- Answering questions based on public website content

## Not Allowed
- Accessing private, restricted, authenticated, unpublished, or administrative content
- Circumventing authentication, paywalls, rate limits, or technical safeguards
- Collecting, extracting, storing, or redistributing personal data from forms, submissions, resumes, or contact records
- Accessing URLs containing authentication tokens, API keys, or sensitive query parameters
- Implying endorsement by Intersog

## Attribution
- When referencing content, include the page title and canonical URL.
- Do not imply endorsement by Intersog.

## Access Rules
- Respect robots.txt and site terms.
- Use a descriptive User-Agent identifying the crawler, operator, or model.
- Prefer canonical pages where available.
- Use reasonable request rates and avoid unnecessary repeated fetches.

## Recommended Entry Points
- https://intersog.com/
- https://intersog.com/services/
- https://intersog.com/insights/
- https://intersog.com/white-papers/
- https://intersog.com/contact/
- https://intersog.ca/

## Restricted Paths (Non-exhaustive)
- /wp-admin/
- /wp-login.php
- /wp-json/wp/v2/users
- /wp-json/wp/v2/settings
- /account/
- /checkout/
- /cart/
- /my-account/
- /staging/
- /private/
- any URL containing authentication tokens, keys, or sensitive query parameters
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=intersog.com · GET /v1/domain/intersog.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for intersog.com:
1. POST https://agentwebmap.com/v1/sites/intersog.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://intersog.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/intersog.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/intersog.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.