search

TheScienceMuseum / collectionsonline

Science Museum Group Collection Online
https://collection.sciencemuseumgroup.org.uk
MIT License
47 stars 3 forks source link

Title being omitted on paginated pages #1175

Closed jamieu closed 1 month ago

jamieu commented 6 years ago

Search for this url in Google https://collection.sciencemuseum.org.uk/search/categories/aeronautics

https://collection.sciencemuseum.org.uk/search/categories/aeronautics?page[number]=3

Screenshot 2019-03-18 at 16 46 42 screen shot 2018-08-30 at 16 50 23
SimonLab commented 5 years ago

The title meta tag is defined as Search our collection | Science Museum Group Collection on the search result pages. From https://support.google.com/webmasters/answer/35624?hl=en Goggle doesn't seem to like repeated titles (the title is the same when a search result returns multiple pages): image

In this case Google generate a slightly different title by adding the page number: image

jamieu commented 5 years ago

Well spotted :-)

Can we make it more specific ie. Category, Object Type, Gallery/Museum name, Search query etc. -- In fact thought we were already doing that (on my mobile so can't see the current titles)

Might also be nice/better to append " | Page 2" etc. rather than letting Google simply append a number, but not sure if that is tricky?

On Tue, 26 Mar 2019 at 15:45, Simon notifications@github.com wrote:

The title meta tag is defined as Search our collection | Science Museum Group Collection on the search result pages. From https://support.google.com/webmasters/answer/35624?hl=en Goggle doesn't seem to like repeated titles (the title is the same when a search result returns multiple pages): [image: image] https://user-images.githubusercontent.com/6057298/55011559-f4816c00-4fdd-11e9-976e-ee4141c9f7d1.png

In this case Google generate a slightly different title by adding the page number: [image: image] https://user-images.githubusercontent.com/6057298/55011637-0fec7700-4fde-11e9-851e-953dead3a85c.png

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/TheScienceMuseum/collectionsonline/issues/1175#issuecomment-476711576, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFk5QAZz57Rk1f9bSegfiGftfUOwgqZks5vakCNgaJpZM4WUKOU .

jamieu commented 5 years ago

Might be most sensible to copy the pattern in there URL structure ie.

ie. for al the filters in currently in the url ie. object name, category, museum, galley etc.

I think we can safely omit Search our collection | when we have specific filter conditions.

(...aslo append Page 2, 3 to the end on any pages (after the first. ie. don't display Page 1 in the title)

evancp87 commented 5 months ago

@jamieu now that i've fixed and closed this page title ticket i'm wondering how to approach this one?

I did have a brief look and i'm not seeing pagination numbers in google, not sure if that's something i've introduced with my changes in the above ticket. I could look into appending the page number onto the title if on page 2 onwards.

image

jamieu commented 5 months ago

I think that's probably the correct behavior

We DON'T want pagination numbers in our title tags (..despite what I may have said in my comment above from 2019!!)

But we do want the filters to appear in the tags.</p> <p>But I think there is a probably limit here and after 3 (?) filters, we want want to prioritise what the most important ones to display are, otherwise the <title> tag will be too long for Google. But it starts to get tricky. <a href="https://developers.google.com/search/docs/appearance/title-link">This is the latest (2024) guidance from Google</a>.</p> <p>Here's a 'starter for 10' but <strong>not wedded to it (so don't feel you have to follow this pattern exactly)</strong>. </p> <p>There is probably a sensible tradeoff here between overtly complex logic and titles that are 'good enough' for Google and bookmarking. So maybe tackle it in two passes. Adding the below to get my thoughts down, rather than as a final spec — feel free to amend, suggest changes or improvements.</p> <p>But I think getting good titles for our 'landing pages' is probably crucial in terms of SEO so this is hopefully well worth the effort.</p> <h3>Top level type</h3> <p>Objects, People, Document and (soon) Groups.</p> <ul> <li><strong>objects</strong> -> <code>Objects | Science Museum Group Collection</code></li> <li><strong>documents</strong> -><code>Documents and Archives | Science Museum Group Collection</code></li> <li><strong>people</strong> -><code>People and Companies | Science Museum Group Collection</code></li> <li><strong>groups</strong> -><code>Explore objects by Group | Science Museum Group Collection</code> (need to think about wording on this one)</li> </ul> <h3>1st class object filters (on their own)</h3> <p>These apply only to <strong>objects</strong> so we can exclude the 'Object' label if these filters are selected. </p> <ul> <li>Category filter -> <code>Motive Power | Science Museum Group Collection</code> </li> <li>Museum (On Display) filter -> <code>On display at the National Railway Museum, Warehouse | Science Museum Group Collection</code> ie. <em>(<code><museum></code>, <code><gallery></code>)</em></li> <li>Named Collection (Collection) filter -> <code>Kodak Collection | Science Museum Group Collection</code> </li> <li>SubGroup (Group) filter -> <code>COVID 19 | Science Museum Group Collection</code> </li> </ul> <p>These apply only to <strong>documents</strong> so we can exclude the 'Document' label if these filters are selected. </p> <ul> <li>Archive filter -> <code>Documents in the Babbage Archive | Science Museum Group Collection</code> </li> </ul> <h3>2nd class filters</h3> <p><strong>Use long form if these are the only filters (other than top level type)</strong></p> <ul> <li><strong>maker</strong> (object)-> <code>Objects by John Smith | Science Museum Group Collection</code> </li> <li><strong>maker</strong> (document) -> 'Documents by John Smith | Science Museum Group Collection` </li> <li><strong>place</strong> (object) -> <code>Objects from Manchester | Science Museum Group Collection</code> </li> <li><strong>place</strong> (document) -> <code>Documents from Manchester | Science Museum Group Collection</code></li> </ul> <p><strong>Use shorter form if multiple 1st or 2nd level filters</strong></p> <ul> <li><strong>place</strong> + <strong>named collection</strong> -> <code>Kodak Collection : Manchester | Science Museum Group Collection</code> </li> <li><strong>place</strong> + <strong>sub-group</strong> -> <code>COVID 19 : Manchester | Science Museum Group Collection</code> </li> <li><strong>maker</strong> + <strong>named collection</strong> -> <code>Kodak Collection : John Smith | Science Museum Group Collection</code> </li> <li>*maker<strong> + </strong>sub-group -> <code>COVID 19 : John Smith | Science Museum Group Collection</code> </li> <li><strong>place</strong> + <strong> maker</strong> -> <code>Manchester : John Smith | Science Museum Group Collection</code> </li> </ul> <h3>3rd class filters</h3> <p>Append these these using a colon ie. <code><as above> : <3rd class filter> : <3rd class filter> | Science Museum Group Collection</code>.</p> <ul> <li>material </li> <li>object type </li> <li>date</li> </ul> <p><em>(we maybe should treat dates differently, esp. if it's the <strong>only</strong> filter ie. 'Objects made in 1982' but for now let's just append it to the end of the other filters).</em></p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/evancp87"><img src="https://avatars.githubusercontent.com/u/65721884?v=4" />evancp87</a> commented <strong> 1 month ago</strong> </div> <div class="markdown-body"> <p>Complete</p> </div> </div> <div class="page-bar-simple"> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>