2
You should be fine considering it will change the meaning as the first will be different.
Also, at times when you have more images, it becomes hard to have the level of uniqueness.
So, any more changes if you can bring would be good.
Note: Focus more on content quality (Maintain the uniqueness) in general and do not worry too much about it.
2
If the text is too similar, then Google are likely to assume the pages are the same and only list one of them. It won't get you a penalty, but you might want to consider adding a canonical tag back to the main gallery page to make sure they treat that as the priority page to index.
As for H1s, they are good for semantic HTML, but there is not much evidence ...
1
If your Image page URL is varied in different device sizes like www.example.com/image-page in desktop and www.example.com/m/image-page in mobile; in that case you have to set canonical URL for image pages.
But if your URL's are same for all devices and responsive then no need to define it.
1
I agree that ImageGallery is not a suitable type for your case.
There are two alternatives to Collection, but they have drawbacks, so I think Collection is the best solution here.
hasPart
The most simple solution would be to use multiple values for the hasPart property:
<article itemscope itemtype="http://schema.org/Article">
<div itemprop="...
1
This is a good resource explaining what you need to do with either escaped fragments or using the pushState and history API in HTML5 to provide content to search engines.
I do want to note that both Google and Bing do crawl javascript via pushState and escaped fragments might possibly be deprecated in the coming months by Google. So to be safe, move over ...
1
resulting in multiple rel=canonical links on the same page pointing to different galleries
That is not allowed. Only one canonical per page.
If you use hashbangs, then Google will call the escaped fragment version of the page to your server. It should serve the HTML version of the page with the corresponding gallery.
Another solution is to add a parameter ...
1
They are somewhat similar:
Show pieces of content one at a time
Controls for forward and backwards
Autoplay feature that can be configured to transition automatically on a timer
However, I would draw the following distinctions:
Slideshow
Primarily for viewing a set of images one at a time.
May support a very large number of images.
Preloads the next ...
answered Jun 26 '14 at 19:30
Only top voted, non community-wiki answers of a minimum length are eligible