Hi,
is this better after updating to version 6.8 of SEOPress?
Can you confirm you have not set custom canonical tag different than the post permalink? (you can see this from the SEO metabox, Advanced tab, canonical tag)
Thx
Thread Starter
proguid
(@procarmanuals)
No, this was still on version 6.7.2, after updating to 6.8 no change.
Yes, I have canonical links installed. It has no effect on adding the post to sitemap.
Found the WP Auto Poster plugin that just updates the date of the post and after that the posts are added to the sitemap.
Thread Starter
proguid
(@procarmanuals)
Clarification:
I have all pages with custom canonical link excluded from sitemap. Only posts that are themselves canonical (without manually specifying the canonical link) are added to the sitemap.
I have an empty sitemap. Is this normal?
If the canonical URL is different from the default permalink, so yes this is normal to exclude these content from the XML sitemap.
Thread Starter
proguid
(@procarmanuals)
I have a series of questions that I would like to get answers to:
- Is the migration process from Rank Math (https://ww.wp.xz.cn/support/topic/migrate-from-rank-math-to-seopress-big-site/) complete?
- What is the reason for the absence of posts in the indexing files? (After updating a post without making any changes, it gets added to the sitemap)
- Why are there empty post-sitemap.xml files and is it possible to remove them to avoid errors in Google Console?
Here are my answers to your question:
- yes it is
- do you use a plugin or a script to create your post in WordPress?
- for performance reasons, this is not always possible to handle this automatically.
Thread Starter
proguid
(@procarmanuals)
No, all posts are manually created. After discovering a problem with adding posts to sitemap, a plugin was applied that simply updates the posts and sets the new post date. After this change, all pages were added to sitemap. There were no such problems with categories, only with posts.
We have rechecked the migration tool from RM to SEOPress. Works successfully, so I’m not sure what happened here.