Doubled search result numbers and displayed results on first search on quoted search (2026.01.11 Responsive HTML5 output)
Issue summary
Search results on live(published) RoboHelp ResponsiveHTML5 outputs display incorrect total result counts and broken pagination behavior. This issue does not occur inside RoboHelp project search or on locally generated output. It reproduces consistently across multiple projects, environments, and hosting configurations once the project has been published.
RoboHelp environment
-
RoboHelp version: 2026.01.11(Updated for testing, previous version had it too)
-
Output type: ResponsiveHTML5
-
Output language: English (US) (same result if unspecified)
Search settings
-
Search context: Text around the search term (Have also tried Starting text of topic)
-
Search context character limit: 100
-
Enable autocomplete in search box
-
AutoCorrect search query
-
Number of results per page: 20
-
Show definitions from glossary
-
Enable substring search
-
Add special characters for search: ";"
-
Excluded file types: PDF, PowerPoint
Projects affected
-
All internal corporate help sites I tested
-
Non-corporate RoboHelp site (personal site)
The issue reproduces across multiple independent help systems.
Core symptoms
On live published sites, when an exact phrase (quoted) search is performed:
-
The corporate systems are copied using an file copy script RoboCopy to an in network web server.
-
Total result counts are inflated or incorrect (Typically doubled)
-
Pagination appears even when the real number of results does not require it
-
Clicking to the next page returns no results if the real number of results was lower than the pagination settings
-
The second page without results shows result counters display impossible ranges, such as:
-
241 of 13
-
361 of 19
-
1 to 20 of 168 (first page), followed by 21 to 40 of 81
-
-
Identical articles may appear multiple times as separate results (usually twice)
-
Repeating the same search may return different counts on different runs (Usually either twice the number of articles, or the correct number.
On local generated output:
-
Result counts are correct
-
Pagination behaves correctly
-
Results align with RoboHelp project search
-
No duplicate entries appear
Reproduction examples
Example 1: Chemical Management
Steps:
-
Search for "add material"
-
There are 13 real results
-
The count says 26 results
-
It is showing 20 results, 7 of them are repeats
-
Click the next page arrow
-
No results displayed on the next page
-
Footer shows 241 to 13 of 13
Local output:
-
Shows only 13 results
-
Count matches RoboHelp project search
Example 2: Environmental Accounting
Steps:
-
Search for "add property"
Observed on live site:
-
Sometimes reports 20 results while displaying only 10
-
Sometimes alternates between 1 and 2 results
-
When 20 results are shown, It is the same 10 repeated
Local output:
-
Shows the correct number of results
-
Matches RoboHelp project search
Example 3: Control of Work
Steps:
-
Search for "Isolation plan"
Observed:
-
First page shows 20 results
-
Footer shows 1 to 20 of 168
-
Clicking next page shows another 20 results
-
Footer changes to 21 to 40 of 81
Analysis:
-
The first page result list usually appears doubled
-
Pagination logic changes mid-search based on incorrect totals
Example 4: Non-corporate RoboHelp site
Site:
-
Personally owned and maintained
-
Hosted on Ubuntu 20.04.23
-
Files deployed manually using FTP
-
No corporate infrastructure
-
No scripted publishing or folder swaps
Steps:
-
Search the live site for the phrase "release notes"
Observed:
-
7 results displayed
-
Header reports 14 total results
Local output:
-
7 results displayed
-
Header correctly reports 7 total results
Analysis
-
RoboHelp project search (in application, not in the web browser)consistently reports the correct number of matching articles
-
Local copy of ResponsiveHTML5 output matches RoboHelp project search
-
Only the live deployed sites show incorrect behavior
-
The article lists themselves appear correct
-
The total result count used for pagination is incorrect
-
Pagination logic is operating on inflated totals rather than real article counts
-
When pagination advances beyond the real result count, result calculations become corrupted
-
The issue reproduces across:
-
Multiple projects
-
Different servers
-
Different deployment methods
-
Different hosting environments
-
Conclusions
-
This is not a content issue
-
This is not a project configuration issue
-
This is not specific to corporate hosting, SCN access, or server OS
-
This is not caused by file copy or publish scripting
-
The issue appears to originate in the live RoboHelp search implementation, specifically in how total hit counts are calculated and exposed to pagination logic in deployed ResponsiveHTML5 outputs on a first search by user. Searching the same exact phrase again will be correct.
Impact
-
Users see misleading or impossible result counts
-
Pagination frequently leads to empty result pages
-
Search reliability and trust are reduced
-
The issue affects multiple production help systems
