Skip to content

How to write a useful DeepSearch query

Choose the right lookup mode, format identifiers cleanly, add only useful context, and write bounded research questions that can be verified.

Quick answer

Quick answer to How to write a useful DeepSearch query

Start with the strongest identifier you genuinely know and enter it in the matching mode: a complete name, exact username or email, internationally formatted phone number, legal company name or domain, valid 17-character VIN, or original image. Add one or two known public disambiguators instead of a long list of guesses. For Deep Search, state the subject, precise question, time or geographic scope, and the evidence standard you want.

  • Use structured lookup fields for exact identifiers and Deep Search for a bounded question across sources.
  • One stable public anchor is more useful than several speculative details.
  • Run separate searches for separate people, identifiers, entities, or images so their evidence does not mix.

Topics: Search queries · DeepSearch lookup modes · Query disambiguation · Research prompts

A useful DeepSearch query starts with the strongest identifier you actually know and puts it in the matching lookup mode. Use a complete name, exact email, full international phone number, exact username, company name or domain, valid VIN, or the original image. Add only a small amount of context that can separate real candidates. A long list of guesses usually makes the search harder to interpret, not more accurate.

Decide whether you need a lookup or a research question

The lookup field and Deep Search mode solve different problems.

  • Use a lookup when you have a structured identifier and want candidates or a focused result: a name, username, phone, email, company, VIN, or image.
  • Use Deep Search when you have a question that needs several public sources to be compared, such as a company's ownership history or what a public figure said about a topic over a stated period.

Do not paste an essay into a phone, email, username, or VIN field. Conversely, do not ask the research assistant to guess an identifier that you can enter exactly in its dedicated mode.

Use the most distinctive input you already possess

Choose the input that creates the fewest plausible matches.

Starting informationBetter queryAvoid
Person's nameFull name plus one known public context signalA first name or a biography made of guesses
UsernameExact handle and, when useful, a platform focusAssuming the same handle has one owner everywhere
PhoneFull number with country calling codeA local-format number without a country
EmailThe complete addressSearching only a common local part such as info or alex
CompanyLegal or trading name plus jurisdiction or official domainA generic industry phrase
VINThe exact 17-character VINA registration number, owner name, or partial VIN
ImageThe clearest original file or direct imageA screenshot containing several unrelated images

For a name search, useful public context includes a city, employer, school, profession, known handle, or official domain. Treat it as a disambiguation hint, not as a fact the result must be forced to match.

Format identifiers cleanly

Names

Use the person's full public name. If they use a stage name, former name, or a name in another script, run those as separate searches and compare the sources. Do not join several aliases into one oversized query.

Usernames

Enter the exact handle; the leading @ is optional. Platform focus can reduce noise, but it should not turn a handle collision into an identity claim. A cross-link from a known profile is stronger than visual similarity alone.

Phone numbers

Include the country calling code, such as +1, +44, or +971. A correctly normalised number lets DeepSearch distinguish the country and numbering plan. Carrier, region, and caller-label fields describe the line or a registry signal; they do not automatically prove who currently uses it.

If you receive a suspicious call or text in the UK, you can forward the text to 7726 (free of charge) so your mobile provider can investigate. Be cautious with numbers beginning 070, 076, 084, 087, 090, 091, or 118, which can be premium-rate. Remember that number spoofing makes displayed caller ID unreliable for verifying identity. If you think you have been charged for making calls because of a scam in England or Wales, contact Report Fraud online or call 0300 123 2040. In Scotland, report the crime to Police Scotland on 101.

Email addresses

Use the complete address exactly as received. An email search can find public connections and domain or incident metadata, but it cannot inspect the inbox. Never test a password-reset form to discover whether someone has an account.

If you receive a suspicious email in the UK, forward it to report@phishing.gov.uk for investigation by the National Cyber Security Centre. If you think you have lost money or been hacked because of an online scam or fraud in England or Wales, contact Report Fraud online or call 0300 123 2040. In Scotland, report the crime to Police Scotland on 101.

Companies and VINs

For a company, add its jurisdiction or official domain when the name is generic. For a vehicle, enter the VIN as printed on the vehicle or its documents. A VIN lookup describes the vehicle; it does not identify its private owner.

In the UK, you can check a vehicle's MOT history online using its registration number (number plate). The service shows limited official MOT and registration records only. The DVLA vehicle enquiry service provides tax status, MOT expiry, and technical specifications, but does not show registered keeper identity without a separate written request to DVLA.

Images

Use the least edited, highest-quality version available. Cropping, overlays, compression, and screenshots can remove useful context or produce weaker matches. Reverse-image search finds reuse and similarity; photo location uses metadata and visual clues. Neither is a face-identification tool.

Write a bounded Deep Search question

A strong research prompt contains four parts:

  1. Subject: the person, company, public topic, or VIN.
  2. Question: the specific fact, comparison, or timeline you need.
  3. Scope: a date range, country, product, event, or public role.
  4. Evidence request: which claims need primary sources, dates, or direct quotations.

For example:

Compare the public statements made by Jordan Avery, the renewable-energy founder in Manchester, about battery recycling from January through June 2026. Separate direct statements from reporting and link each claim to its source.

The fictional occupation and city in this example are known disambiguators, not instructions to invent matching details.

Keep one subject and one purpose per search

Run separate searches when you have:

  • two people with the same name
  • an old and a new email address
  • a personal and a company phone number
  • several possible company entities
  • an image collage rather than one target image

This makes the evidence trail legible and prevents a field from one subject from being read as if it belonged to another.

Interpret 'nothing found' carefully

Before broadening a query, check for a typo, wrong country code, alternate name, or outdated identifier. Then try one justified variant. If the result remains empty, record that the available search found nothing; do not convert absence into a claim about the person.

The DeepSearch terms say results can be incomplete or inaccurate and must be verified before use. Continue with the common-name workflow or choose a different lookup type only when you have a real alternate anchor.

Continue reading

Tools mentioned in this guide