Should I target two pages for the same keyword, but two different intents?

[Wagster]

When people type in a certain keywords in my industry space (animated video), they usually have one of two intents: some want to see videos (for inspiration or entertainment or whatever) and some want to hire a company.

We have pages that meet each intent. Some "Best of..." blog posts for the crowd that want to see videos (that might be top-of-the-funnel prospects, potentially) and a landing page for the buying-intent people.

I'm seeing each ranking page as essentially two, kept in proper balance to meet search intent by click-throughs. So I'm betting that my landing page won't cannibalize the "best of..." page. Is that the right way to see it, or not?

[Wagster]

It might be more than double. Just to give you an example of one of my keywords, "Whiteboard animation"

Some are searching for it to learn how to actually make a whiteboard animation. Some are searching for it because they want to hire a company to make whiteboard animation. Some are searching for it because they want to see whiteboard animation videos, either for the sake of entertainment or to get inspiration to make a video of their own. Really, there could be many intents.

I will certainly make sure that one page is linked to the other, thanks.

[mememax]

I can't think about a query which intent will be double. Can you provide any example?

In my opinion you will surely have a common part of the query, which you can still optimize for but then you need to add the second part which is the one that identifies the page. In this case, considering that the intent is very closely related you want to ensure that the two pages are linked one to the other above the fold. You want to ensure to provide a link to your sales pages from the more informative one. That's useful and very much a must

Anyway if the two queries are really 100% matching, then you should try to merge the two pages by integrating the informative part with the commercial one.

Sorry to not be able to be more specific but I can't find a good example of queries that could face this issue.