Find on Page

Overview

Find on Page answers a question by pointing, not just by typing. Instead of writing you a paragraph, Evelant scrolls to the exact spot on the page that contains the answer and highlights it — useful when you know an answer is somewhere on a long page and just want to be shown where, rather than have it re-typed at you.

This is a read-only feature: it locates and highlights text. It does not click buttons, fill forms, or navigate anywhere on your behalf — Evelant only points at what's already on the page.

Why point instead of type

Some questions are faster to answer by showing than by telling. If you're reading a long terms-of-service page and want to know where the cancellation clause is, a written answer still makes you scroll to go read it in context. Find on Page skips that step — it takes you straight there, already highlighted, so you can read the surrounding paragraph in place instead of trusting a paraphrase of it.

It's also useful for pages you don't fully trust an AI to summarize accurately — pricing, legal terms, specifications — since you end up reading Evelant's exact source, not its interpretation of it.

Three ways to trigger it

You don't need to remember special phrasing. Any of these work:

The /find command. Type /find followed by what you're looking for, e.g. /find the refund policy. This is the most reliable trigger — it always runs Find on Page, never a normal chat answer.
Just ask naturally. Typing something like "where does it mention the warranty period" or "find the pricing table" is often enough on its own — Evelant recognizes the intent without the slash command. If you've attached a file or image to your message, natural-language detection is skipped (you're asking about the attachment, not the page), so use /find explicitly in that case.
Say it out loud. Press Alt+S (the same shortcut as Voice Ask — see the Voice Ask guide) and speak your question. If what you say sounds like a locate request ("find the return address"), Evelant runs Find on Page instead of answering out loud.

What you'll see

A brief "Evelant is searching this page…" indicator while it looks.
If it finds a match: the page scrolls to the passage, an animated cursor travels to it, and the exact text is highlighted.
The highlight stays for about 7 seconds, then fades on its own — or you can dismiss it early.
If it can't confidently find anything, it falls back to answering your question normally instead of pointing at the wrong spot.

A worked example

Say you're on a long software pricing page with several tiers, and you want to know whether the mid-tier plan includes API access, without reading the whole comparison table yourself.

Type /find does the Pro plan include API access and send it.
Evelant scans the page, finds the pricing table, and identifies the row and column that answers your question.
The page scrolls to that exact cell, the cursor travels to it, and it's highlighted for about 7 seconds.
You read the actual table cell yourself — not a rephrased version of it — and can immediately ask a follow-up like "what about the Enterprise plan" in the same way.

If the page had used vague labels instead of "Pro" (say, unlabeled columns identified only by price), a more specific query — quoting the exact price or plan name shown on the page — would help Evelant land on the right column with more confidence.

Cancelling a search

Press Escape at any point to stop it immediately.
Click or tap anywhere on the page — a pointer press cancels a search or dismisses a landed highlight instantly.
Scrolling the page on your own does not cancel it — you're allowed to keep reading while it travels to the answer.

If you cancel, Evelant treats that as your answer: it won't also try to respond in the chat, and it won't charge you for a completed request.

Where it works

Find on Page runs on whatever page you currently have open in your browser — regular web pages, documentation sites, articles, product listings, and PDFs viewed in your browser's own PDF viewer, as long as the text is rendered and selectable rather than an image. It always works on the page in your current tab, not a page you describe or link to.

Tips for good results

Be specific about what you're looking for, not just the general topic. "Find the section on cancellation fees" works better than "find the important part."
Use /find on long or repetitive pages — the more the page repeats similar wording (pricing tiers, FAQ entries), the more useful it is to say explicitly what makes the passage you want unique.
It reads what's rendered, not what's hidden. If a passage is behind a "Read more" toggle or a collapsed accordion, expand it first so Evelant can see and point at it.
One page at a time. Find on Page only searches the page you're currently viewing, not other open tabs.
Quote wording from the page itself when you can. If you remember a specific word, number, or heading near what you want, including it in your query narrows things down far more than a purely conceptual description.
If the first attempt lands nearby but not exactly right, try again with a query that describes what's immediately around the passage you actually wanted — "right after the section on refunds" — rather than repeating the same phrasing.

Example requests

/find the phone number for support
"where in this article does it mention the release date"
"find the row for the Enterprise plan in this table"
"point me to the paragraph about data retention"
(spoken, via Alt+S) "find the shipping cost"

Cancelling a search

Nothing happens when I ask a natural-language question. Natural-language detection is intentionally conservative — it only triggers when your phrasing clearly reads as "find/where is X," not every question. Use /find explicitly if you want to guarantee it runs.

It answers normally instead of pointing at something. This means it looked and wasn't confident enough in a match to highlight it — rather than guess and point at the wrong sentence, it falls back to a written answer. Try rephrasing with more specific wording from the page itself.

"Daily limit reached" message. Find on Page has its own daily usage limit, separate from your regular chat credits, to keep it fast and reliable for everyone. It resets the next day.

The highlight is on the wrong passage. Cancel it (Escape or a click) and try again with more specific phrasing — quoting a nearby word or number from the passage you actually want usually resolves it.

Frequently asked questions

Does this cost a chat credit? Find on Page draws from its own daily allowance, not your regular message credits — so using it doesn't reduce how many chat messages you can send.

Can it click things or fill out forms for me? No — that's a different, not-yet-available capability. Find on Page only locates and highlights; it never interacts with the page on your behalf.

Does it work on PDFs? It works on rendered page text. If you're reading a PDF opened directly in the browser, results depend on whether the browser's own viewer exposes selectable text the same way a regular web page does.

Why does voice sometimes answer out loud instead of pointing? If what you said doesn't sound like a locate request, Alt+S falls back to answering your question the normal Voice Ask way — you don't need to choose in advance, just ask naturally.

Does it work the same way in the web dashboard as in the extension? Find on Page needs to see and highlight the actual rendered page you're looking at, which is a browser-extension capability — it isn't available from the web dashboard on its own, since the dashboard isn't looking at any particular website.

Can I use it more than once in the same conversation? Yes — each request is independent. Ask it to find one thing, read the answer, then ask it to find something else on the same or a different page.

Will it highlight more than one place at once for a broad question? No, it points at a single passage. If your question could reasonably be answered by several different spots on the page, narrow the question so there's one clear best match.

Does it work on very long pages that need scrolling through many screens? Yes — it can travel across a long page to reach a passage far below where you started, scrolling as it goes.

Related features

Structured Data Extraction — for pulling out an entire table or list, rather than pointing at one specific answer.
Voice Ask — for asking a spoken question that gets answered out loud, the sibling capability that shares the Alt+S shortcut.
Full-Page Deep Scan — for reading an entire long page as context for a normal written answer.