When to Use See, See Also, or a Second Index Entry

A reader looks up a familiar term and finds “See” followed by another heading. That instruction may save space and clarify terminology. It may also send the reader on a needless hunt for two page numbers that could have appeared immediately.

The choice between a see reference, a see also reference, and a second entry is a choice about the reader’s route. Decide what that route should accomplish before deciding how to format it.

Use “see” to redirect a lookup term

A see reference says: look under this other heading for the treatment you want. It is useful when a reader may search for a variant name or a synonym, but the index gathers that subject under one preferred term.

• Rainwater harvesting. See Rainwater collection
• Rainwater collection: household systems, 42–46; storage, 71–74; urban policy, 118–121

Here the imagined book uses the two phrases for the same practice. The reference preserves a plausible lookup term without repeating a structured entry. Its destination supplies the access the source heading promises.

Do not equate related subjects merely to consolidate entries. If the book distinguishes rainwater harvesting from a broader category of water collection, retain that distinction. The text and the intended audience determine whether two terms are equivalent.

The University Press of Florida’s indexing guidance distinguishes a see reference following a heading alone from a see also reference following locators. It also requires the target wording to match the destination entry. These examples follow that basic pattern; confirm the house rules for the book you are indexing.

Use “see also” to extend a search

A see also reference says: this entry already gives you useful access, and another entry offers relevant additional material. It connects subjects without claiming they mean the same thing.

• Rainwater collection, 42–46, 71–74. See also Drought planning
• Drought planning, 118–125

The reader can go straight to the collection discussion or follow the connection to a separate planning discussion. The reference earns its place because a reader interested in one subject may benefit from the other.

A stricter check appears in Hopkins Press’s indexing guidelines: the destination of a see also reference should supply additional page references, rather than repeat those already given. Follow that requirement for a Hopkins index. More generally, identify the extra access a reference provides before retaining it.

Use a second entry when direct access helps

For a short treatment, repeating the locators under another useful term may be kinder than redirecting the reader. Indexers often call this double posting or double entry. The American Society for Indexing’s award criteria favor double posting over see references that lead to very few locators.

• Rainwater collection, 42–46
• Rainwater harvesting, 42–46

If these are equivalent terms in this imagined book and both are likely lookup choices, either one now takes the reader directly to the discussion. There is no need to add a see also link between entries that provide exactly the same access.

A second entry can also expose a treatment through two distinct subjects. A passage on school rainwater tanks might belong under both “Rainwater collection: schools” and “Schools: rainwater tanks.” Shared pages alone do not prove wasteful duplication; check whether each heading answers a different reader’s question.

Balance direct access against space and maintenance. Repeating two locators is a different proposition from repeating twelve subheadings. A reference can preserve a useful alternative lookup without creating two large structures that must be kept consistent.

Check for broken and burdensome routes

Read each reference as an instruction you must carry out. These failures need different repairs:

• Missing target: “Rainwater harvesting. See Rainwater capture” fails if “Rainwater capture” is absent. Restore an appropriate destination or correct the reference; do not create an empty heading merely to make it resolve.
• Cycle: “Rainwater harvesting. See Rainwater collection” and “Rainwater collection. See Rainwater harvesting” send the reader back to the starting point. Choose a page-bearing destination and direct the alternative term there.
• Chain: “Rainwater capture. See Rainwater harvesting,” followed by “Rainwater harvesting. See Rainwater collection,” requires two lookups. Point both alternatives directly to “Rainwater collection.”
• Duplicate reference: “Rainwater collection, 42–46. See also Drought planning; Drought planning” repeats one instruction. Keep it once.
• Valid but cumbersome: “Rainwater harvesting. See Water management” resolves, but “Water management” has thirty subheadings. If the relevant treatment is buried there, target its specific subheading, following house style, or provide a direct entry.

These are more than spelling checks. Scribe’s index-checking procedure checks whether references lead to entries rather than further see references, and separately asks whether they are useful. A destination can exist while the route remains poor.

Also inspect the finished alphabetical neighborhood. “Rainwater collection” and “Rainwater collections” pointing to the same distant target may give readers no meaningful additional choice. Remove a redundant variant only after considering how readers search; alphabetical adjacency alone does not make different lookup terms interchangeable.

A final reader-route check

• ✓ What will readers type or scan for? Preserve useful lookup terms.
• ✓ Does “see” redirect an equivalent term, or wrongly suppress a distinct subject?
• ✓ Does “see also” add a relevant route beyond the access already supplied?
• ✓ Would a short second entry save a lookup at an acceptable space cost?
• ✓ Does every specific target match an existing heading or subheading and lead to usable locators?
• ✓ Have you removed chains, cycles, repeated instructions, and avoidable detours?
• ✓ Do the final wording, placement, italics, and punctuation follow the agreed publisher style?