I would start by going back to the recording of the session to see what questions the users were answering and try to figure out why they made the specific requests. Quite often, the underlying problems can be related though the recommended solutions from users are very different.
Ultimately, if you can't get any more information than what you already have, this is a good moment to look at the goals of your site and lay these requests atop of them. Do they fit? If so, where? Are these request within scope of your site? etc.
If this doesn't provide any clarification, think about the questions you want to ask those same users, now that you know the end requests. And try to think about the holes in the original questioning. I'd go back and fill in the question gaps and try to run a second round of testing.
I'd also like to point out that traditional focus groups aren't necessarily the place for design research. Many things can happen to easily skew the findings of a self-reporting technique like this, such as the groups being taken over by a large personality or people simply responding quickly, not truly being introspective, etc. Here's some information on where focus groups can fit into your research plan.
If possible, I recommend that you define each page with very specific user goals and tasks, and then conduct a simple task-based test. This will tell you much more about what a user needs than asking them what they want or need.
Also, keep in mind that user requests are just that, requests. Not all of them will be useful or good for your product, even if it occurs frequently. It's up to you/your team to decide how to tackle the problem that lies under each request.