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
Thanks for the great library and I think its the only nodejs sitemap parser which is upto date. I was wondering is there any way to check whether the sitemap is having valid syntax?
I basically needs a validator for sitemap but I am sure that this parser will be already using rules for the schema of sitemap. So does it throws any errors on detecting invalid syntax or is it forgiving?
I am happy to help and submit a PR if that can be implemented using the code already in place.
Kind Regards
The text was updated successfully, but these errors were encountered:
Since the time I have submitted the issue, I have been researching on the solutions for my own problem as well. As sitemap is xml so it can be validate against xsd formats and sitemaps.org provides two xsd files, one for sitemap's index and one for the actual sitemap. (E.g https://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd)
Libraries like xml.js provides the utility to validate xml files against xsd. I am not sure whether it should still be incorporated in the sitemapper or not? Will love to hear your thoughts/decision on it
I haven't come across an invalid sitemap yet, so I'm not sure how important this is. I'm sure it would be useful for others, in the case that the process crashes in the event of an invalid sitemap.
Hi,
Thanks for the great library and I think its the only nodejs sitemap parser which is upto date. I was wondering is there any way to check whether the sitemap is having valid syntax?
I basically needs a validator for sitemap but I am sure that this parser will be already using rules for the schema of sitemap. So does it throws any errors on detecting invalid syntax or is it forgiving?
I am happy to help and submit a PR if that can be implemented using the code already in place.
Kind Regards
The text was updated successfully, but these errors were encountered: