# Jump to the page a search match is on

*Collection: Displaying Libraries · Category: Search · Availability: FileDeck Pro · Canonical URL: https://www.getfiledeck.com/docs/hit-navigation/*

[Full-text content search](https://www.getfiledeck.com/docs/content-search/) finds documents by what's
*inside* them. That's useful, but on its own it leaves the reader with a
60-page policy document and the knowledge that the phrase is in there
somewhere.

FileDeck Pro closes that last step. When a search matches inside a PDF, the
result shows **Found on page 7** underneath the title. Click it and the document
opens at page 7.

> **FileDeck Pro** — this is part of content search. It needs no setup beyond
> having content search enabled and your library indexed.

## How to use it

Search your library as normal. Matches that were found inside a document's text
gain a small "Found on page N" control below the title; hovering it shows the
surrounding sentence, so you can tell a passing mention from the section you
actually want.

Clicking it opens the document at that page — in the [preview
lightbox](https://www.getfiledeck.com/docs/document-preview/) if the document is previewable, otherwise in a
new tab. Page jumping relies on the reader's PDF viewer honouring a page anchor,
which every current browser's built-in viewer does.

## When no page is shown

The control only appears when FileDeck can be certain which page a match is on.
It is deliberately absent when it can't:

- **The match is in the document's metadata, not the file.** Searching for a word
  that only appears in the title, description or a category matches the document
  but has no page — there is nothing to jump to.
- **The file isn't a PDF.** Word, Excel, PowerPoint and OpenDocument files are fully searchable,
  but they have no fixed pagination to point at, so no page is offered.
- **The PDF was scanned and read by OCR.** [OCR](https://www.getfiledeck.com/docs/scanned-pdf-ocr/) returns
  the document's text as a single block without page structure, so scanned
  documents are searchable but not page-navigable.
- **The PDF's pages couldn't be read individually.** A small number of PDFs are
  built in a way the text extractor can't split into pages. They stay fully
  searchable; they just don't offer a page jump.

In every one of these cases the document still appears in the results exactly as
before. The page jump is an addition, never a filter.

## Which match does it point to?

The first one. If your term appears on pages 3, 9 and 40, the control points at
page 3 and the hover snippet is the text around that first occurrence. When you
search several words at once, FileDeck goes to the earliest occurrence of any of
them.

## Large libraries

Libraries big enough to switch to server-side paging get page jumps too — the
page numbers are calculated for the rows on screen, so the feature doesn't slow
down as the library grows.

## FAQ

### Do I need to re-index for this to work?

Page positions are recorded when a document is indexed. Documents indexed before
you updated will keep working for search but won't offer a page jump until they
are re-indexed. Run **Documents → Settings → Search → Rebuild search index** once
to pick them all up, or simply re-save an individual document.

### Does it highlight the search term in the document?

It opens the document at the right page. Highlighting inside the file is up to
the reader's PDF viewer, and browsers differ too much to promise it — so FileDeck
promises the page, which is the part that reliably works.

### Is the snippet visible to people who can't open the document?

No. Snippets and page numbers are only ever calculated for documents the visitor
is already allowed to view — the same access check that governs whether the
document appears in results at all.

A document behind lead capture, view-only, PDF watermarking or another download
check shows its page number without a snippet.
