Displaying serp with both results that stay in context and results that send the user off to a different website

hope you can help.

I'm working on a rather large job search product, and thus far, we've managed to display in our ads in a reasonably consistent way despite there being 5 different major ad sources and hundreds of thousands of job advertisers, all with their own personal way of writing job ads. We have three new major changes on the horizon that have got me really concerned about how the user experience will be affected; so please, if you have any tips on how you'd approach this, or similar services with similar challenges, I would be eternally grateful. The major changes are:

  1. Our organisation has decided that they want to use a scraping service that increases our ads displayed by approximately 80%. This is a major bonus for our users, aside from the fact that we have no way (or more so - intention) of displaying them the same way we do our usual ads. So for example, for some ads, you will have a consistent flow and design from search through to the ad page, and the application process (in some but not all cases); but for the new ads, you would get as far as the search results page and then the user (upon clicking on the ad) would be sent to whatever site it's been scraped from. My concern is that we are supposed to display both of these on the same search results page, and so the user will get a very choppy experience if they decide to just click through their results. Sometimes they'll get to stay in context and in other cases they'll be sent away. How can we best: a.) display the two very different types of results on the same page based on relevance, whilst b.) setting the right expectations for users regarding what's about to happen and c.) maintaining a good user experience

  2. We are about to introduce multiple ad types. For instance, instead of only finding job ads, the users will also be able to find ads for franchises. I've considered two ways of displaying these; one being in the search itself, so you can see in the auto display which ad typ options provide results; and the other as a toggle feature on the search results page. What is the best 'discovery' option for users (avoiding cognitive overload)?

  3. We have been asked to offer our users a translation function, of which Arabic will be one of the 3 first languages to be introduced. We don't want our users to assume to be able to apply in the language that they're reading the ads in. How would you go about empowering the users to search and find job ads in their own language, whilst indicating to them that the application itself needs to be done in the local language? Where should one draw the line between helping and misguiding?

And last but not least ..

Which order would you approach these changes in?

Sorry for a super long question and thanks in advance for your answers.