> ## Documentation Index
> Fetch the complete documentation index at: https://docs.baselayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enhanced Search

> Raise officer and address match rates by adding online sources to a Business Search.

Enhanced Search is the recommended way to run a Business Search when you want the full Online Presence dataset alongside registered records. It bundles Website Analysis, Industry Prediction, Social Profiles, and Reviews into a single `POST /searches` call, and - most importantly for match rates - merges addresses and officers discovered online back into `business.addresses[]` and `business.business_officers[]`.

This is the single biggest lever for improving officer and address match rates without changing your submitted data.

***

### When to use it

* You want to improve officer or address match rates without restructuring your onboarding form
* You are onboarding newer businesses with thin Secretary of State records
* You want the full Online Presence dataset returned in one call rather than running Business Search and Web Presence requests separately

> **If your team is asking how to raise officer or address match rates, this is the answer.** Enhanced Search merges online-sourced candidates into `business.business_officers[]` and `business.addresses[]`. A submitted officer or address can match against a Secretary of State record OR an online record.

***

### How to request it

Enhanced Search is only available via `POST /searches`. `Order.Enhanced` must be requested alongside `Order.WebsiteAnalysis` and `Order.NaicsPrediction` — without these, the request will fail.

```json theme={null}
{
  "name": "Acme Corp",
  "address": "123 Main St, New York, NY 10001",
  "website": "acmecorp.com",
  "officer_names": ["Jane Smith"],
  "options": [
    "Order.Enhanced",
    "Order.WebsiteAnalysis",
    "Order.NaicsPrediction"
  ]
}
```

#### What's included

`Order.Enhanced` covers the same four sub-products as requesting Website Analysis, Industry Prediction, Social Profiles, and Reviews individually, but it does something none of those individual orders do: it **merges discovered addresses and officers back into the business object**.

* **Website Analysis**: returned via `orderables[]` tracking objects, not inline. Fetch via `GET /website_analysis_requests/{id}`.
* **Industry Prediction**: returned via `orderables[]` tracking objects, not inline. Fetch via `GET /naics_prediction_requests/{id}`.
* **Social Profiles**: returned inline at `business.social_profiles[]`
* **Reviews** (profile-level data only): returned inline at `business.reviews[]`
* **Expanded officer discovery**: candidates discovered online merged into `business.business_officers[]`
* **Expanded address discovery**: candidates discovered online merged into `business.addresses[]`

> **Not included in Enhanced Search:**
>
> * **Directory Listings**: only available via `POST /web_presence_requests` with `Order.DirectoryListing`
> * **Individual review text**: `business.reviews[]` on this path returns profile-level data only. For per-review text and dates, use `Order.ReviewFull` on `POST /web_presence_requests`.

#### Latency

Because `Order.Enhanced` performs a broader discovery across multiple sources, it takes on average around 25 seconds to complete - longer than a standard `POST /searches` call.

`Order.WebsiteAnalysis` also runs inside the search and adds time. `Order.NaicsPrediction` can finish after the search completes unless `Order.Enhanced` is requested. For high-value KYB use cases where match rate matters more than speed, it is the recommended default.

#### When Business Search fails

> If the submitted business doesn't match any registration record, `/searches` returns `state: FAILED` and **orderables are not triggered**. The `orderables[]` array will be empty and no online presence data will be returned - even when valid `options` were included in the request.
>
> If your platform onboards applicants who may not have an SoS registration, use `POST /web_presence_requests` instead to ensure online presence data is always returned. See [The Web Presence API](https://docs.baselayer.com/docs/web-presence-api.md).

***

### Response fields

Enhanced Search returns a standard Business Search response, with online presence data merged into existing fields and added in new ones. The fields that drive match-rate improvements are the expanded officer and address arrays.

#### Expanded `business.business_officers[]` and `business.addresses[]`

Each entry carries a `sources` field, an **array** indicating where that candidate was discovered.

| `sources` value | Origin |
| :- | :- |
| `SOS` | Secretary of State filing |
| `Online` | Discovered from the business's online presence (website, social, or reviews) |

A single officer or address can carry both values: `sources: ["SOS", "Online"]`. This means the same candidate was found in the state registry **and** corroborated independently online.

Example officer entry from Enhanced Search response:

```json theme={null}
{
  "name": "Jane Smith",
  "sources": ["SOS", "Online"],
  "titles": ["CEO", "chief executive officer", "director"]
}
```

#### Online presence fields

| Field | Source |
| :- | :- |
| `business.social_profiles[]` | Same shape as `found_social_profiles[]` on `/web_presence_requests`. See the Social Profiles guide. |
| `business.reviews[]` | Same shape as `found_reviews[]` (profile-level only). See the Reviews guide. |
| Industry Prediction | Retrieved via `GET /naics_prediction_requests/{id}` using the orderable in `orderables[]`. |
| Website Analysis | Retrieved via `GET /website_analysis_requests/{id}` using the orderable in `orderables[]`. |

***

### Interpreting results

The objective of Enhanced Search is straightforward: **increase match rates by enriching officer and address profiles with online information**. Every interpretation rule below is in service of that goal.

**Match rate improvements come from `Online` entries.** A submitted officer name or address that doesn't appear in SOS filings may still appear on the business's website, LinkedIn, or Google review profile. Enhanced Search makes those candidates available for matching automatically, your submitted data and matching logic don't need to change.

**Use `sources` to differentiate signal strength.** A candidate with `sources: ["SOS"]` is a registered record. A candidate with `sources: ["Online"]` is corroborated from public-facing online sources. A candidate with `sources: ["SOS", "Online"]` is the strongest possible identity signal. If you need a stricter standard for a given decision, you can filter to `SOS`-only entries; if you want the broadest coverage, accept matches against both.

**Don't treat absence of `Online` entries as a fail.** B2B businesses, professional services firms, and digital-native businesses often have minimal online presence. Match rates will still be high through SOS records alone.

***

### Related guides

* [Online Presence: Basics](https://docs.baselayer.com/docs/online-presence-basics.md) — integration path decision guide and data model
* [Online Presence: Best Practices](https://docs.baselayer.com/docs/web-presence-orderables.md) — full decisioning framework
* [Online Presence: Response Reference](https://docs.baselayer.com/docs/online-presence-response-reference.md) — full field definitions and path-specific response shapes
* [Website Analysis](https://docs.baselayer.com/docs/website-analysis-basics.md) — sub-product included in Enhanced
* [Industry Prediction](https://docs.baselayer.com/docs/industry-prediction-user-guide.md) — sub-product included in Enhanced
* [Social Media Profiles](https://docs.baselayer.com/docs/social-media-profiles.md) — sub-product included in Enhanced
* [Customer Reviews](https://docs.baselayer.com/docs/customer-reviews.md) — sub-product included in Enhanced (profile-level only)
* [Directory Listings](https://docs.baselayer.com/docs/directory-listings.md) — **not** included in Enhanced; request via `/web_presence_requests`
* [Business Search API Reference](https://docs.baselayer.com/api-reference/search/post-search.md) — full endpoint documentation


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.