What does a web presence request return, and how is the response organized?

A web presence request looks for a business online and tells you what it found and how well it matches what you submitted. The response follows one rule: top-level fields are your inputs echoed back, and everything Baselayer discovered sits in nested objects.

What you can submit. Business name and address are required. Optionally add a website, phone number, email, officer names, alternative names or DBAs, known social profile URLs, and a two-letter country code (US if omitted). The more you provide, the more we can match against.

What you order. The options array controls which checks run and what you are billed for:

• Order.WebsiteAnalysis: find and analyze the business website.

• Order.SocialMedia: find social profiles.

• Order.ReviewSummary or Order.ReviewFull: find review listings, with or without the full review text.

• Order.DirectoryListings: find the business’s profiles on third-party business directories such as BBB, YellowPages, and Manta.

• Order.NaicsPrediction: predict the industry.

What comes back.

• Match fields: business_address_match, phone_number_match, email_match, and people_match, each with a companion _sources field saying where the match was found.

• Website: found_website, business_website_match, and website_analysis.

• Social and reviews: found_social_profiles, found_reviews, and found_directory_listings.

• Industry: industry_prediction, when ordered.

Results arrive on the WebPresenceRequest.completed webhook or by fetching the request by ID. In the console, order the same checks by ticking them when you submit a search or upload a batch; a section showing "analysis not ordered" means that option was not selected.