Search query

A search query is what a person types or says to a search engine, the exact words, in their order, with their typos. You plan around keywords, but you earn clicks on queries. This page shows where to see your queries, how to read intent, and what to change on your pages.

By , founder of Porteur · Updated 14 September 2026 · Markdown

What a search query means for a small site

Queries are how real people find you. They reveal language, problems and timing that your keyword list misses.

On a small site, a handful of pages do most of the work. One query pattern per page keeps focus: match one clear intent and answer it well.

Example: yourproduct.com/pricing should match “yourproduct pricing”, “yourproduct cost”, and “yourproduct plans”. Not “how to export CSV”, that belongs on /guides/export-csv.

Search query vs keyword

A keyword is the term you target. A search query is what people actually searched. Your plan sets keywords, your traffic comes from queries.

Queries include variants and typos like “youproduct pricing” or “your product price”. Your page should handle these if the intent matches.

Where to see your queries

Use Search Console’s Performance report. It lists the queries your site appeared for, and filters by page or country. Rare and anonymised queries are omitted.

Use keyword tools for search volume estimates. They estimate at the query level, so check the exact wording when you pick targets.

About 15% of daily queries are new, so your logs will never be complete as of 2026. Focus on patterns, not totals.

Read intent from the results page

Search the query and study the results page. The mix of pages and features shows the intent the engine assigned.

  • Brand or navigational: homepages and sitelinks. Match with your / homepage or /login help.
  • Commercial investigation: comparisons, “vs”, reviews, pricing. Match with /pricing, /comparison-pages, and case studies.
  • Informational: guides, tutorials, People Also Ask, featured snippets. Match with /guides/, FAQs and examples.
  • Visual: image packs or video rows. Add images with alt text, and consider a short video demo.
  • Local: map pack. If relevant, add clear NAP details and a contact page.

If the results show images, add meaningful images on the target page and compress them. If it shows how-to steps, add a clear process with headings.

What to do with query data

  1. Group queries by shared intent

    Export queries for a page from Search Console. Cluster terms that expect the same answer. Drop outliers into ideas for new pages.

  2. Tighten the title and h1

    Use the primary wording people use. Example before: “Plans”. After: “YourProduct pricing and plans”. Keep the title near 60 characters.

  3. Cover the sub-questions

    Scan People Also Ask and top results. Add sections that answer them. Example: add “Billing cycle” and “Discounts” to /pricing.

  4. Fix mismatches

    If /guides/getting-started earns impressions on “pricing”, link to /pricing and clarify the guide scope. Avoid splitting intent across pages.

  5. Track queries to clicks

    Watch CTR by query in Search Console. If impressions rise and clicks do not, improve the snippet: title, meta description, and intro.

A fixed page reads like the query. It loads fast, answers quickly, and links to the next step, like /signup or a relevant guide.

Questions

Sources

Check my site, free

Paste your homepage URL to get a free check that reads your site and the searches around it, and shows three query-led findings in about thirty seconds.

  • Free check, no card
  • Read-only, your own accounts
  • Readable by your agent

Read next