Search Results for Documents With the Same Title: Visible Version Descriptors That Help People Choose
A site that publishes manuals, price lists, policies or guides often ends up with several revisions sharing one title. A visitor searching for "Delivery Terms" sees three identical lines and cannot tell which applies. This article proposes a publication workflow that adds visible version descriptors to each result. It is an example process, not an observed client result. It makes no claims about how any search engine ranks or displays pages; it concerns what a person sees in your own results list.
Principle
Two results with identical titles must differ in something a reader can see without opening them. The descriptor is a short line shown with every result for revisions of the same document.
Inputs
Use a hypothetical sample. A fictional shop has three documents titled "Delivery Terms": one effective from an early date and now superseded, one current, and one scheduled to take effect later. For each document collect:
- Title and document family identifier (the thing that makes them revisions of the same document).
- A revision label chosen by the publisher, such as "Revision 3".
- Effective date, and end date if superseded.
- Status: current, upcoming, superseded.
- A one-line change note written by a human.
Decision branches
Step 1: Are there two or more results in the same family? If not, no descriptor is needed beyond the title. Showing descriptors everywhere is optional; some teams prefer to add them only when a clash exists.
Step 2: Build the descriptor from fixed parts in a fixed order: status, revision label, effective date. Example: "Current, Revision 3, effective 1 March". Keep the order identical across the site.
Step 3: Add the change note as a second line when it helps distinguish revisions: "Adds a section on islands deliveries".
Step 4: Decide default ordering. Suggested: current first, then upcoming, then superseded. State the rule on the results page in plain words.
Step 5: Decide whether superseded revisions appear by default. Options: show them labelled, or hide them behind a "Show older versions" control. Pick one and document it. Hiding is reasonable when older revisions would mislead; showing is reasonable when customers may hold orders under the old terms.
Stop conditions
Stop if two revisions have the same label and date, because the data cannot support a descriptor; fix the data. Stop if a revision lacks a status. Stop if the change note is missing for a document where the reader needs it; assign it to the author rather than inventing text.
Worked example
Searching "delivery terms" returns:
Delivery Terms. Current, Revision 3, effective 1 March. Adds a section on islands deliveries.
Delivery Terms. Upcoming, Revision 4, effective 1 September. Changes the cut-off time for same-day dispatch.
Delivery Terms. Superseded, Revision 2, 1 January to 28 February. Replaced by Revision 3.
The superseded entry is visually quieter but still readable. Each opens a page that repeats the same descriptor at the top, so the reader confirms they landed on the intended revision.
Consistency on the document itself
The descriptor on the document page must match the one in results. Build both from the same fields so they cannot disagree. Avoid relying on colour alone to show status; include the word.
Acceptance test
Pick one document family with at least three revisions. Search for its title on your site. Without opening any result, ask a tester to name which one is current and which takes effect later. Then open each and confirm the page header repeats the same descriptor. Change the status of one revision in the source data and confirm both the results list and the document page update together. Finally, create a deliberate duplicate label and confirm the publishing step flags it. The workflow passes if the tester answers correctly from the list alone and the two displays never disagree.
Conclusion
Identical titles are fine when the visible descriptor does the distinguishing. Use fixed fields, a fixed order, a documented default ordering, and refuse to publish ambiguous revisions.