How to arrange JIRA for company that has few comparison sites + internal tool to manage those?

[filip.stachak]

I would appreciate the help with this one.

So I started to work in a company that is a publisher and earns from affiliate programs. They send traffic to banks and lenders from their websites. The use comparison tables and ranks and such to show users different offers and let them decide which bank or lender to take. The company is mostly using SEO and Content creation to gain traffic. 

The company has a small development team + Designer, SEO, Copy, Sales teams. The Jira know is a total mess where you cannot see what is what, what are the priorities, no estimation, sprints are 1-5 weeks depending on....I don't know. Mess like hell.  

I am wondering how to set jira so this will be effective to handle all of this and still to have a good visibility and control over this. So below you can find the structure I would appreciate some suggestions. The company doesn't have any customer portal or anything like this.

Main sites - different comparison websites about financial products (6 crucial+ a lot of satellites sites).The business model is roughly the same on all of them, but there are some small differences. For example,  some sites ask users to fill the form on website, then through API receives callbacks with potencial offers for customer and provides him/her with an option (still on customer panel, everything on the website). Other websited just send user via affiliate link to lenders to do all the work on their sites. So those are 2 different business models. 

Other sites - company has also other comparison sites about other products (vpn's and sports betting) Those are small sites that just started, but I suppose there might be more to come from different segments.

Internal tool - the company has an internal tool to manage the comparison tabels, offers, adding new partners or excluding old ones. A tool that manages the offer, ranking position on all of those websites. Used mainly by Sales and SEO team.

My thought was to create one project for all of this and keeping one backlog where I would prioritize all of PBI in one place depending on the value, user traffic, stakeholder inputs and so on - so just basic stuff. I would differentiate it using some fields, custom fields or tags, for example:
Component: site / internal system A / internal system B / Mailing system / xxx / zzz 
site: site1 / site2 / site3
type of site: Finanse / VPN / Betting 

I could easily see the backlog for any site if a use filters and see the whole backlog as well. 

The questions is whether this is a good idea to have it all in 1 project? It's impossible to make projects for each site (there are around 50, but 4 actually make 95% of the money)
At some point I will need to have some sites in one project. 

What do you thinks? How would you solve that?