Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @smolgiant, another thing to try is to add credits/money to your open AI API account. The key wasn’t working for me either till I topped up my account.

    I’m not associated with the dev btw, just started using the plugin a few days ago.

    Thread Starter st27

    (@st27)

    Thanks for getting back to me! I was also distracted by a million things but finally back to this issue.

    I think I might have not explained the issue correctly, with my use of the terms of products and pages.

    If you set the query limit to 250 and have 50 pages and 500 products, you’ll see 50 pages and 250 products = 300 URLs in the sitemap. If you publish a new product, it’ll be the 51st URL after the older page.

    Yes, I understood that. My limit is 250, and I have 6 pages including the homepage, and they always stay on top. That is ok.

    The issue is with the 244 products.

    When I add a new product, the link is added to the sitemap as the 7th link, as expected. But when I UPDATE it (change price, name, description, etc):

    • If the product is already on the sitemap, the last updated date is updated. Which is expected and the desired functionality.
    • If the product is NOT already on the sitemap, it is not added as the 7th link. Which is believe is what should be happening? Based on:

    Since TSF v5.0.5, the plugin lists products in the sitemap by order of 'lastmod' (product last modified) instead of 'date' (product created). This means that the product you last updated should spawn on top of the sitemap, pushing out older pages exceeding the 250 page-query limit. This is ideal because it is likely that Google will have already reparsed the removed sitemap entries.

    I tried out the filters you suggested, but unfortunately they did not make a difference.

    Thread Starter st27

    (@st27)

    Hi Sybre, thank you for your response.

    Since TSF v5.0.5, the plugin lists products in the sitemap by order of 'lastmod' (product last modified) instead of 'date' (product created). This means that the product you last updated should spawn on top of the sitemap, pushing out older pages exceeding the 250 page-query limit.

    This isn’t happening for my website. I see that the ‘lastmod’ is updating for products already on the sitemap, but other edited products are not spawning on top of the sitemap, and the old pages are not being pushed out.

    I’m currently on Version 5.0.6, so it should be working. Anything I can do to investigate why this issue is taking place? I’ve also verified that the sitemap does indeed update when new products are added and when products on the sitemap are updated. Happy to provide more details.

Viewing 3 replies - 1 through 3 (of 3 total)