Methodology and AI results disclaimer

What an audit measures

• Brand mentions and explicit recommendations.
• Observed answer position, top-three and top-five placement where a ranked structure can be detected.
• Citations, normalized source domains and whether a source supports brand or competitor evidence.
• Competitor visibility and prompt-level performance.
• Historical change only between compatible benchmark versions.

Provider execution

The current product supports ChatGPT through OpenAI, Claude through Anthropic, Perplexity, and Gemini. Provider availability still depends on plan entitlement and production configuration. Each provider run records requested and returned model metadata when available, response identifiers, raw answer text, citations, token usage, latency, errors and estimated cost when pricing coefficients are configured.

Search and Agent Readiness

AI Readiness evaluates technical and static signals that can affect Search Readiness and Agent Readiness. Findings are versioned and retained with issue history. Browser-runtime WebMCP inspection is not claimed in this release; static discovery signals are reported only when they can actually be verified.

Scoring and comparison

Scoring weights and benchmark configuration are copied onto each audit. Historical comparisons require the same project and compatible benchmark identity, including prompt set, provider/model configuration, locale, scoring version and repetition count. Failed runs are not counted as successful responses.

Important limitations

• LLM outputs are probabilistic and can vary between repeated runs.
• Results may differ by time, model version, location, language, provider search availability and other provider-controlled factors.
• Entity, position, sentiment and citation extraction is deterministic and inspectable in this version, but heuristic.
• A detected correlation after an implementation does not prove that the implementation caused the change.
• Audit results do not guarantee future visibility, ranking, traffic, revenue or placement.

Website crawling

MonitorMyGEO fetches public HTTP(S) pages for project context, readiness checks and optional change tracking. Requests follow a limited number of redirects, apply timeouts, and reject local, loopback, link-local and private network destinations. It does not create an archival copy of every page.

Questions

For methodology questions or to report an extraction issue, contact viisesh@bigdoor.ai and include the audit identifier. Do not email provider credentials or sensitive raw data.