Some collection types are not been rendering in the sitemap
See original GitHub issueI’m using this plugin at a sitemap in my site, but I get a bug:
I set all collection types in the settings:
As can be seen, both Tags and Categories are collection types with a valid UID field(slug), but, navigation to the site map, we get this:
<url>
<loc>https://localhost/pages/education</loc>
<lastmod>2020-10-20T12:08:32.430Z</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://localhost/pages/work-experience</loc>
<lastmod>2020-10-31T13:42:22.293Z</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://localhost/pages/about-me</loc>
<lastmod>2020-10-20T12:42:11.136Z</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://localhost/pages/projects</loc>
<lastmod>2020-10-18T22:47:14.513Z</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://localhost/pages/posts</loc>
<lastmod>2020-10-18T22:47:14.658Z</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://localhost/pages/read-the-documentation-fool</loc>
<lastmod>2020-11-01T14:22:39.533Z</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://localhost/pages/grid-and-flex-layout-making-responsiveness-handling-easier</loc>
<lastmod>2020-11-01T14:31:31.554Z</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://localhost/pages/home</loc>
<lastmod>2020-11-01T13:16:42.930Z</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://localhost/</loc>
<changefreq>monthly</changefreq>
<priority>1.0</priority>
</url>
No trace of tags or categories, even though there are at least five records in each.
I tested this both in local and production but i am getting the same result. I thought it could be because of the draft system, but both tags and categories do not use this feature.
What could be the problem then?
PD: there is also another collection type which not use a uid field but i would like to add to the sitemap, is there any way to do that?
Thanks
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Common XML sitemap errors
Sitemap errors (General) · 1. You have set the page (or the whole post type) to noindex . · 2. The page's canonical...
Read more >Manage your sitemaps using the Sitemaps report
Use the Sitemaps report to tell Google about any new sitemaps for your property, to see your sitemap submission history, and to see...
Read more >How to Fix the “Your Sitemap Appears to Be An HTML ...
When creating websites, errors can occur. Here we show you what to do when the error "Your sitemap appears to be an HTML...
Read more >SharePoint pages do not render when using unsafe controls
Fixes an issue in which some SharePoint pages do not render when they use controls that are ... The type could not be...
Read more >Configure a sitemap
By default, the sitemap is generated for the whole site and stored in cache. An XML sitemap is created specifically for search engines...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@boazpoolman Thanks.
@SalahAdDin This plugin is by design an integration of the UID field type. Rewriting it to allow all field types would require a lot of work, and also I am of the opinion that only “seo-friendly” URLs should be used in a sitemap, instead of ID based URLs. These URLs are (as the name would suggest) SEO friendly, an that is what a sitemap is for anyways; to improve your SEO.
I will create another issue for this, to see if more people would want this feature.