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

Sitemap.xml need to aid search engine discovery of Schema.org terms #1483

Closed
RichardWallis opened this issue Jan 19, 2017 · 8 comments
Closed
Assignees
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). site tools + python code Infrastructural issues around schema.org site. Most can ignore this!

Comments

@RichardWallis
Copy link
Contributor

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.

@RichardWallis RichardWallis added the site tools + python code Infrastructural issues around schema.org site. Most can ignore this! label Jan 19, 2017
@RichardWallis RichardWallis self-assigned this Jan 19, 2017
RichardWallis added a commit that referenced this issue Jan 19, 2017
Updated robots.txt to link to the produced sitemap
Fix for issue (#1483)
@AymenLoukil
Copy link

I also suggest to create an HTML sitemap listing all the terms / vocabs ( alphabetical / chronological order) linking to single pages.

@Aaranged
Copy link

+1 @RichardWallis

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?:
http://schema.org/Thing
https://schema.org/Thing

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).

@AymenLoukil
Copy link

@Aaranged There are already some issues about http / https :

#1486 and #1325

@Aaranged
Copy link

Thanks @AymenLoukil - in fact just came back to this issue to see that I had seen #1325 and so to ignore my comment. :)

@github-actions
Copy link

This issue is being tagged as Stale due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Jul 31, 2020
@jonoalderson
Copy link

Can we revisit this, now that we're HTTPS'd?

@RichardWallis
Copy link
Contributor Author

Current sitemap looks like this:

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://schema.org/3DModel</loc>
<lastmod>2020-11-30</lastmod>
</url>
<url>
<loc>https://schema.org/AMRadioChannel</loc>
<lastmod>2020-11-30</lastmod>
</url>
<url>
<loc>https://schema.org/APIReference</loc>
<lastmod>2020-11-30</lastmod>
</url>
<url>
<loc>https://schema.org/Abdomen</loc>
<lastmod>2020-11-30</lastmod>
</url>

What needs visiting?

@jonoalderson
Copy link

Odd. When I requested that earlier I got a 404. Never mind! 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). site tools + python code Infrastructural issues around schema.org site. Most can ignore this!
Projects
None yet
Development

No branches or pull requests

4 participants