• Resolved wasanajones


    I’ve been exploring this issue and it seems to come back to asking if Transient Caching is something that could be added to the plugin?

    I use content blocks with spintax to add some relevant content to posts coming from a news feed.

    each page refresh loads new versions of this add-on content, which is fine for users, but googlebot is going to see too many changes without good reason. a little good, a lot bad…

    exploring options on how to deal with this by preventing the shortcodes from functioning or some other way keep coming back to controlling transients – maybe let them expire every 30 days. I really don’t know how they work, but people offering ideas suggest asking the plugin developer (you).

    I use WP Supercache but it doesn’t have anything for this.

    would add a lot of benefit for SEO,


Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Loomisoft


    Hi @wasanajones

    Just to make sure I understand this right … you’re in essence constantly injecting content from a news feed into one our plugin’s content blocks.

    This content block is then used in pages/posts.

    The problem is that the content is being updated too quickly and you want to slow it down.

    If that’s the case, wouldn’t it make sense to slow down the refresh rate during the injection process?


    Hi – thanks for following up – actually the scenario is different than that… sort of the other way around

    I’m autoposting posts from news RSS feeds. These posts have content blocks added to them. Inside the content block is spintax. Well written, useful, related, maybe even valuable (or whatever else google thinks curated content should provide) …

    the issue is that when/if Googlebot returns to the post (usually looking for user engagement [comments] or editorial updates to current events) – it sees new blocks of content. too much change.

    so the idea would be to somehow prevent the contact blocks from calling the new content every time the page loads. periodic, occasional changes are good – big blocks of change every time – not so good.

    asking around people keep coming back to the idea of transient caching – so if the block could have a transient cache assigned to it and expire every 30 days it would be perfect for this application.

    I have no clue how to actually do that.


    • This reply was modified 1 year, 8 months ago by  wasanajones.
    Plugin Author Loomisoft


    Hi @wasanajones.

    The more we look at this, the more it seems the best option would be to slow the rate of your spintax update to once every 30 days (or whatever duration serves best in the instance). Is there no way you can do this?

    In all honesty, caching the content block would detract from the core purpose of the plugin, which is to modularise content so as to allow a change to be made in a single place that is then reflected in any page/post that references it.

    As for cache plugins, our understanding is that they normally operate on the public facing pages/posts and not on non-public elements like the content blocks.

    We keep coming back to this … the best option would really be to slow the rate of your spintax update if possible.



    thanks for the followup

    I’m afraid there isn’t going to be a simple fix

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Transient Caching’ is closed to new replies.