I have a regular view in a layout for a WordPress Archive page because it used to be the only way to have infinite scroll pagination. Now that WordPress Archive Views supports this feature, I started to compare the two and found something strange. Both view types display pagination correctly in the page's source code - for example:
HOWEVER, when you manually go to these pages (as search robots would), the regular view shows the exact same 12 posts (I have show 12 posts set) on each 'page'
The WordPress Archive View, however, does in fact show different posts on different pages.
Is this a bug or an intended feature? I am stuck in a bit of a hard place because SEO is important, but my view also needs the layout and filters split up, which the WordPress Archive View may not support yet (I just asked this in another thread).
Those pagination links are generated by the theme and won't necessarily work correctly with your views. They appear in the header before the rest of the page is generated, and Views has no way of controlling them, and there are sundry complications that can arise because a page can contain multiple views, and which view should the header pagination links refer to etc.
This was one of the key motivations for adding custom WordPress archives to Views where all of the pagination and SEO issues can be handled correctly.
Unfortunately, that doesn't help with your other ticket.