Skip to main content

​
Direct answer

Use Monitor > Insights > Local Businesses with location-specific configured prompts. Review whether your business appears, how its details are represented, and which DIRECT businesses appear in the same selected results. Verify material details against your current business records.

​
Data required

Use configured local prompts, location and radius or market scope where available, provider and model, run date, observed local-result records, stored answers, SELF/DIRECT classification, business name, address, phone, website, and approved location data.

​
Workflow

1

Define the local scope

Choose the locations, audience need, and prompts that matter. Avoid combining cities or service areas with different competitive conditions.
2

Review observed results

Inspect Local Businesses and the associated answers for SELF and DIRECT presence, position where available, and displayed business details.
3

Verify business information

Compare observed name, address, phone, website, category, and availability claims with the approved current record.
4

Compare stable cohorts

Repeat the same location, prompt, provider, and model filters before interpreting changes.

​
Interpretation

Presence in an observed local result shows that the business appeared in that selected run. It does not guarantee a recommendation to every user, a map ranking, or a visit. Missing or inconsistent details are investigation signals, not proof of their source.

​
Possible next actions

  • If business details are inaccurate, test corrections in authoritative owned listings and public pages.
  • If SELF is absent while relevant DIRECT businesses appear, inspect their recorded source and category context before choosing a local-content hypothesis.
  • If results vary by location, test location-specific evidence rather than applying one conclusion to every market.

​
Limitations

Local outputs can depend on location, personalization, data providers, model version, and time. Qwairy observes selected runs only. The REST local endpoint is a separate contract; verify its fields, filters, and units before comparing it with the product.

Local Insights

Build location reporting from the documented source.

Local Businesses

Review observed local results in the product.

Local API

Read the separate REST local-data contract.

Products in AI shopping

Review observed commerce results separately.

Top-of-funnel visibility

Analyze early-stage brand presence.

Websites influencing answers

Inspect recorded sources without inferring causation.