GEO GROWTH ECOSYSTEMCompany knowledge · Real observations · Ongoing deliverySign in to workspace ↗
GEOgrowthCONNECTED INTELLIGENCE
中文Get a free audit ↗
BUYER QUESTIONS

Procurement FAQ

Confirm the work, evidence and responsibilities before you commit. Platforms, quantities, prices, dates and acceptance criteria belong in the written scope.

Scope and observation channels

What work can an engagement cover?

Start with your company facts, buyer questions and an agreed visibility baseline. A wider scope can cover content preparation, client records, contracted delivery and comparable follow-up measurement. Agree the actual stages and responsibilities first; a website review or a saved request does not mean that the whole operating cycle has been completed.

Which AI platforms and markets are included?

Name each observation channel, provider, model, language, market, question set, repetition count and budget in the scope. Current code implements API model observations, but a configured connection is not evidence of a completed observation. Real calls, evidence review and production client acceptance remain separate checks. Consumer interfaces, search-enabled APIs and search AI summaries require their own agreed access and method.

Does an API answer show what buyers see in ChatGPT, DeepSeek or Kimi?

Treat it as an API observation only. A consumer product interface and a model API are separate observation channels, and their search tools, settings and context may differ. One returned answer cannot establish a brand's position across those products, an overall ranking or a trust score. Keep the channels and their evidence separate.

Can I submit a public request or see verified client results now?

The public website and its published pages are available to browse. Anonymous requests are currently closed; the protected intake currently permits only the owner account allowed by the access policy. This content update has not run real model observations or completed production client acceptance. Sample methods and implemented execution code are not presented as real client results.

Price, payment and scheduling

Are the published prices a binding quotation?

The USD figures on the service-plan page are planning ranges. Your written scope must confirm the final price, platform coverage, question and content quantities, deliverables, payment milestones and exclusions. Confirm any model-call budget and third-party charges separately before work begins. A planning range does not authorize additional spending.

How does an introductory audit differ from a paid engagement?

An introductory baseline is narrower than the paid L1 planning scope. Agree the questions, available channels and intended output before any observations. Request access is currently invitation-based. Recording an application does not run the audit, produce findings or promise a delivery date; actual findings need observations and review.

What must happen before a project starts, and how is payment handled?

The scope must be signed, the agreed advance payment must be confirmed as received, and a delivery owner must be assigned. The current process registers offline signatures and uses manual bank-receipt checks. A pending receipt is not confirmed funding; a reversal can pause new delivery if funding becomes insufficient. Electronic signing and automatic reconciliation, debits or refunds are not connected.

How long should we allow for the work?

An illustrative sequence is materials review, question-set confirmation, observations and evidence review, draft delivery, then client review and any agreed retest. Put stage dates, review windows and dependencies in the contract. Timing depends on scope, material readiness, access, platform availability and revisions. This sequence is a planning example, not a fixed service-level or results deadline.

Materials, permissions and privacy

What should our team prepare first?

Prepare your company and product websites, target markets and languages, typical buyer questions, relevant competitors, and the location and date of supporting documents. Identify who can confirm facts and approve content. The current delivery format supports text and source references; attachment uploading is not connected. Do not put API keys, bank credentials or unrelated personal information into an application.

What if our company materials are incomplete or disagree?

Keep the source, date and owner of each important claim. Separate company statements from third-party documents and independently verified facts. Flag missing or conflicting evidence instead of silently choosing the most favourable version. Certification, capacity, performance and customer claims need their own support; repeating a statement on more pages does not verify it.

Does sending information authorize its publication or marketing use?

No. Permission to handle a service request is separate from optional marketing consent. It does not authorize public reports, client case studies, customer logos or use in a cross-client benchmark. Agree the material, channel and permitted identification before publication. Saving information does not automatically send an email or publish anything externally.

How are retention, confidential information and cross-border requirements agreed?

Before public collection opens, the operator, public contact channel and practical retention and deletion rules must be stated. Anonymous intake is currently closed. If you have confidentiality, data-location, cross-border or industry requirements, review them before sharing materials and confirm the agreed handling in writing. This website does not establish an unagreed compliance certification, data-residency commitment or automatic deletion schedule.

Deliverables and acceptance

What should a usable report or delivery contain?

Agree the required question set, markets, languages, observation channels, model or question-set versions, timestamps, original answers, returned references, failure records and review status. Findings must point to actual evidence; unexecuted work stays marked as planned. Current delivery uses reviewed text and source versions. Attachment upload and external publication integrations are not connected; any publication needs a separate scope and a real publication receipt.

Who can access the client portal?

A client needs an explicitly registered login email and permission in the website access policy. The current policy allows only the owner; client access still needs to be arranged and accepted. A self-reported email or company domain does not grant ownership or portal access. Approved portal views show the client's contract summary, actual projects, tasks and reviewed deliveries, while internal notes, bank evidence and signing records remain internal.

How do we request changes and confirm a delivery?

An authorized client can review an approved version, leave modification comments and confirm the reviewed delivery. Revisions create a new preserved version with its sources and another internal review; an older confirmation does not approve a newer version. Keep feedback and confirmations in the actual client account. An owner's read-only preview cannot confirm on the client's behalf.

What counts as project completion?

The current workflow requires the full contract amount to be confirmed as received, all project tasks to be complete, and the latest version of every delivery to have client confirmation. Agree the deliverable checklist and review responsibility in advance. A saved draft, internal approval or payment awaiting verification is a different state. Project completion does not itself prove external publication, improved AI visibility or new orders.

Measurement, retesting and outcomes

How are coverage, mentions and failed observations counted?

Report planned observations, valid observations and the metric denominator separately. For illustration only: if 15 of 20 planned observations are valid and three valid answers mention the brand, coverage is 75% and the valid-answer mention rate is 20%. The five failures are missing observations, not five negative answers. This arithmetic example is not a client result.

Does a returned citation prove that a source or claim is verified?

A returned URL or citation records what the model referred to. It does not by itself establish that the page is accessible, supports the specific claim, is current or is authorized for publication. Check those points separately and retain the relevant source location. An unchecked citation remains unchecked; it is not a third-party endorsement or certification.

What makes a retest comparable?

Keep the question-set version, language, market, observation channel, model identifier, available parameters and repetition plan consistent, and record observation times. API answers can vary even under similar conditions. Separate platform, model or search-condition changes from like-for-like comparisons; show changed conditions and missing observations instead of treating every difference as an effect of the work.

Can you guarantee AI inclusion, recommendations or sales?

No. The commitment is to the agreed work, evidence and review process. Google also states that meeting its website requirements does not guarantee crawling, indexing or display. In evaluation, distinguish brand mentions, citations, attributable visits, customer-reported sources, qualified inquiries and confirmed revenue. Unknown attribution stays unknown; a mention-rate increase cannot be converted into an assumed number of orders.

Agree the scope before the work starts.

Requests currently use invited access. Review the entry process and required information. A recorded request is not an executed audit, a sent email or a client result.

Review invited request access ↗