Automailer Pulling Up Old Content No Longer On My Blo!
AnsweredHi all,
I really love the automailer but lately it seems to have a mind of its own! Today it pulled a logo into the automailer that I have not used in FOUR YEARS. The logo is defnitely no longer on my website; the media file isn't stored anywhere on the server or in the trash (we had someone confirm this). I have no idea where it is pulling stuff from. It is also showing articles no longer on our blog that we've directed with 410 content deleted errors and picking seemingly random articles to showcase. Is there any way to fix this?
I've temporarily shut it off but would love to run it again if it would stop picking up things no longer on our website.
Thanks,
Jeanne, homegardenjoy.com
-
Official comment
Hey Jeanne!
Do you mean the logo featured in Automailer is pulling an older logo, or the featured images for the posts served in Automailer? A little more information could help us better troubleshoot that.
In general, this sounds like a caching issue. Clearing your site's cache, any caching plugins, and asking your host to clear serverside caching is the first step. After all caches are clear, you'll want to go to Grow Publisher Portal > Grow Settings > Recommended Content and click Refresh Posts. This tells Grow to comb through all the post bookmarks it has created and update them, which should remove the deleted posts. Depending on where the site logo pulled in, this could resolve that issue as well.
Refreshing posts can take up to 24 hours, but if you're still seeing deleted posts appear in Automailer or other Grow features after that, let us know and we can take another look. -
Thanks! Yes, it pulled up an old logo that was from 7 years ago. We confirmed it is nowhere on the site but it is in Bing search (I just found it). I'm wondering - does the automailer pull from search engine data or from the site itself?
0 -
It should pull from the site itself, specifically your OpenGraph meta data. If there is a cached file somewhere (and it sounds like Bing is accessing that as well), clearing the cache should help!
0
Please sign in to leave a comment.
Comments
3 comments