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
Sitemap.xml need to aid search engine discovery of Schema.org terms #1483
Comments
Updated robots.txt to link to the produced sitemap Fix for issue (#1483)
I also suggest to create an HTML sitemap listing all the terms / vocabs ( alphabetical / chronological order) linking to single pages. |
Question (and fair warning, it's a bit of a trick question), which one of these two URLs would you select to publish in your sitemap?: Think you can see where I'm going here. Permitting a web page to be accessed under both HTTP and HTTPS is decidedly not a best practice. And in terms of which formulation to prefer, (Google is unambiguous in regard to preference here). Any support this year for my annual proposal that schema.org URIs be canonicalized under HTTPS, with the HTTP version 301 redirecting to the HTTPS version? Apologies if I can't recall some deal-breaking objection as to why this is not possible (i.e. it breaks some functionality). Perhaps absent any quick responses I'll just open a new issue proposing that (and rolling the use of rel="canonical" into this). |
Thanks @AymenLoukil - in fact just came back to this issue to see that I had seen #1325 and so to ignore my comment. :) |
This issue is being tagged as Stale due to inactivity. |
Can we revisit this, now that we're HTTPS'd? |
Current sitemap looks like this:
What needs visiting? |
Odd. When I requested that earlier I got a 404. Never mind! 😆 |
Schema.org terms and descriptions are not always easily discoverable via search engines. This is also reflected in the quality of the schema.org site search powered by Google Custom Search.
Creation of a sitemap file to direct search engine crawlers should go someway towards solving this issue.
The text was updated successfully, but these errors were encountered: