Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we add "no-index" to old spec versions? #170

Open
tomcrane opened this issue Dec 6, 2018 · 4 comments
Open

Should we add "no-index" to old spec versions? #170

tomcrane opened this issue Dec 6, 2018 · 4 comments
Assignees

Comments

@tomcrane
Copy link
Contributor

tomcrane commented Dec 6, 2018

I suspect that's far too drastic, but https://iiif.io/api/search/0.9/ always comes up in Google search and 1.0 doesn't when I look for "iiif search".

Any gentler form of nudging search engines to 1.0?

@glenrobson glenrobson self-assigned this Feb 24, 2022
@glenrobson
Copy link
Member

IIIF search is OK now but:

"iiif content state" -> goes to 0.3
"iiif change discovery" -> goes to 0.9.2

@hadro
Copy link
Contributor

hadro commented Feb 25, 2022

I'm not sure this is the right solution, but it looks like we could request the removal old version from indexing via the Google Search Console

@hadro
Copy link
Contributor

hadro commented Feb 25, 2022

I should add that they have a field for "outdated content", which I think would cover this case, seems like it is potentially treated differently than DMCA removals or other more urgent/legal reasons why people request things to be removed from indexing via the Google Search Console.

@glenrobson
Copy link
Member

I had a look at the removal tool but it seemed to be for content that had been deleted but still appeared in google search results but we can give it a try and see how it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants