You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noticed today that artworks' "related works" menus, which provide gene or tag labels for clicking, no longer link to the corresponding pages. That leaves gene and tag pages almost completely inaccessible, except from direct term search or the /categories page.
This isn't just best-practice. The client-side UI enabled by these elements isn't accessible to Google's crawler, which instead sees the ?_escaped_fragment_= [static] version of the page where these would be actual links that would build relevance, page-rank, etc. for the destination pages. We're even investing in outreach for those pages now, which can hardly get far if the pages aren't discoverable.
The text was updated successfully, but these errors were encountered:
I'd like to reopen this since I think there is some benefit to making these links actual links. Currently we don't link to gene or tag pages from anywhere except the /categories page. They continue to rank poorly (as a result, in my opinion).
These might operate like tabs, but they're highly contextual and artsy.net in fact has excellent general pages corresponding to each, so it could be valuable to make them real links even if only for Google's crawler.
I agree this is worth addressing. It used to be that when you click on any of those selectors that are gene names, above the rail of artworks there was a link to "Explore all works in [gene]".
This would also display if that selector were a tag, eg. "Profile".
Noticed today that artworks' "related works" menus, which provide gene or tag labels for clicking, no longer link to the corresponding pages. That leaves gene and tag pages almost completely inaccessible, except from direct term search or the
/categories
page.This isn't just best-practice. The client-side UI enabled by these elements isn't accessible to Google's crawler, which instead sees the
?_escaped_fragment_=
[static] version of the page where these would be actual links that would build relevance, page-rank, etc. for the destination pages. We're even investing in outreach for those pages now, which can hardly get far if the pages aren't discoverable.The text was updated successfully, but these errors were encountered: