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
The Google's sitemap guidelines says that a sitemap should not include more than 50k links and be smaller than 50Mb.
Beyond this limits, the main sitemap file should be a sitemap index which refers nested sitemaps.
As of today, the plugin just cut the sitemap to 50k links:
To solve this without adding any limitation, the sitemap plugin should handle nested sitemaps.
Because controlling the sitemap file size any time the search bot renders to optimize it would be difficult, what I suggest here is to let the website's admin decide how the sitemap should be cut.
How I see this feature is:
Add a Section model, with a name and a slug
Add a 1:1 relation between Definition and Section and the corresponding relation field in the creation a link Definition form
Generates multiple files when the Definition links limits goes beyond the 50k limit (ie: blogposts_1.xml, blogposts_2.xml, ...)
If no Section model is defined, the plugin would just continue to work as of today.
But if one Section model is defined, the sitemap.xml file would look like this:
While discussing the support for this plugin inside the forum plugin, @bennothommo was skeptical about the need to add all the topics urls, due to the true fact that it can make the sitemap go bigger than accepted by the search bots.
The Google's sitemap guidelines says that a sitemap should not include more than 50k links and be smaller than 50Mb.
Beyond this limits, the main sitemap file should be a sitemap index which refers nested sitemaps.
As of today, the plugin just cut the sitemap to 50k links:
wn-sitemap-plugin/models/Definition.php
Line 19 in ee1d77b
wn-sitemap-plugin/models/Definition.php
Lines 207 to 211 in ee1d77b
To solve this without adding any limitation, the sitemap plugin should handle nested sitemaps.
Because controlling the sitemap file size any time the search bot renders to optimize it would be difficult, what I suggest here is to let the website's admin decide how the sitemap should be cut.
How I see this feature is:
Section
model, with a name and a slugDefinition
andSection
and the corresponding relation field in the creation a linkDefinition
formDefinition
links limits goes beyond the 50k limit (ie: blogposts_1.xml, blogposts_2.xml, ...)If no
Section
model is defined, the plugin would just continue to work as of today.But if one
Section
model is defined, the sitemap.xml file would look like this:The text was updated successfully, but these errors were encountered: