SEF Pagination on Userslists goes away after page 1

A large part of my site is made up of userslists, and the keywords worked into their alias/paths are very important to my SEO. Using Joomla 3.4 & CB 2.0.9, the first page of a list looks fine, ie:

example.com/illinois/springfield.html

but when I use any of the pagination links at the bottom of the list, it turns into a version of this:

example.com/index.php?option=com_comprofiler&view=userslist&listid=92&Itemid=779&limitstart=25&searchmode=0&search=&cbsecuritym3=cbm_1495e89e_7f87c94c_794dae862342224673b6d9002e8ea319

I've tried to modify the router file, but I can't get it to display properly. All my lists are generated from custom SQL queries I set, I don't allow users to search and I don't display a list drop down selector. I have over 300 lists and dozens of pages for each, so I am losing the SEO benefits on many pages. Is there a way to fix this pagination to display the correct SEF links in the pagination?

Wasn't there a guarantee of a response in 24 hours with the purchase of a professional membership??

Search URLs and pagination URLs of a Userlist won't SEF. This is due to it being a form GET submit instead of an actual URL so there's nothing to rewrite. We've already a feature ticket to redo how the userlist form functions in a later release. There's no simple fix or workaround at this time as the entire userlist form handling behavior needs to be redone.

Wasn't there a guarantee of a response in 24 hours with the purchase of a professional membership??

Missed your post, sorry. If this happens just PM me the link to your topic. See my signature for direct URL to PM me.

Is that because CB doesn't use Joomla's pagination? I have SEF pagination links in the component I developed, and it's all GET, no POST variables, the router set-up was easy. Could one just hack in JRoute in CB's code where the links are generated? If so, what file(s) deal with pagination (besides the router)?

There's no routing behavior ran on the pagination links. The only routing behavior we have for userlists is direct access, which just adds the userlist generated alias (from title) to the URL. We've already a ticket to rewrite the form behavior for a later release.