Closed derivadow closed 6 years ago
All great suggestions. Especially integral before moving from next.
.
Change from 302 to 301 (perm redirect)
The reason for this is that we are on next.
and will change when we hit the route.
Another task here is to setup Google Webmaster Tools.
There's no harm in 301 from blog. to next. and then in the future to root. The only reason not to use a perm redirect is if we wanted to return to using blog. etc. and therefore wanted Google to continue to associate inbound links + pagerank with the original URL. Because we won't be doing that there is no harm in setting up a perm redirect to next. and then to www/root. But the absence of a perm redirect is actively harming our SEO today.
Reopening this for further discussion and action on missing structured data, index page descriptions, breadcrumb trails and other metadata concerns.
Another task here is to setup Google Webmaster Tools.
This was done as #1103. Webmaster Tools is now Search Console.
description
needs some loveAlso relating to #534, I've asked Danny for some content team input on the meta descriptions https://wellcomecloud-my.sharepoint.com/personal/j_phillips-bacher_wellcome_ac_uk/_layouts/15/WopiFrame.aspx?sourcedoc={9e6848a3-a114-40e1-a574-77983a01ec34}&action=editnew
All pieces that haven't been done have their own tickets:
Type
Explore index
Articles
Missing Structured Data Errors:
Also consider adding:
Breadcrumb trail
Consider adding crumb trail mark-up e.g. Wellcome Collection > Explore > :articleTitle
For Digital Stories consider: Wellcome Collection > Explore > :DigitalStoryTitle > :articleTitle (although this would require us to link to e.g. https://next.wellcomecollection.org/series/the-outsiders
Redirect from blog.wellcomecollection.org This means that google is indexing blog. rather than next. dot. Without this none of the above changes will appear of the Google SERP.