Google Indexing Trashed Pages

  • Resolved designknight

    (@designknight)


    8 years ago

    We recently migrated to a server that uses Litespeed and LSCache for wordpress. We were coming from an Apache and Varnish setup. Recently, I noticed google has started to index and list our trashed pages on google. This didn’t used to happen.

    We have the same xml and seo plugins that we’ve always had, so the only change that I can think of is Apache to Litespeed. Has anyone had this issue? Is there a way to get it to stop caching trashed pages if that is what google is picking up?

    Google moves fast indexing it, so deleting from the trash really only changes google from sending it to a trashed page to sending it to a 404 page, so simply deleting the page doesn’t help.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support Hai Zheng⚡

    (@hailite)

    8 years ago

    When the pages are moved to trash, what will you see if you directly visit it as a guest? It should be 404 already I guess?

    Thread Starter designknight

    (@designknight)

    8 years ago

    People can still see them.

    The second one shows up in google before the first one. Most likely because it was worked on and cached first before they updated the title.

    Plugin Support Hai Zheng⚡

    (@hailite)

    8 years ago

    If the second one is not a 404 or 301 to your new post, I don’t think Google will remove it. Can’t get the difference between LSCWP and your previous cache system at this point.

    Thread Starter designknight

    (@designknight)

    8 years ago

    I’m guessing it has to do with the fact that future posts in this particular category can be viewed by design. I think the way it does this is to turn “scheduled” into “published” articles behind the scene. I assume when that happens, Litespeed decides to cache it since it thinks its published. It updates when the post updates, but if there is a title/url change, perhaps that old version is sticking around?

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    8 years ago

    Hi, @designknight

    How are you doing that? Setting to Published for future posts? Do you have a plugin?

    Thread Starter designknight

    (@designknight)

    8 years ago

    Looks like it does just that, and allows for comments on future posts. It appears the developer used a plugin.

    Trashed isn’t the only thing, this is a pending article (way back from 2012) that was recently indexed by google:

    http://webcache.googleusercontent.com/search?q=cache:O8thHr6MQNcJ:earthsky.org/%3Fp%3D2168+&cd=12&hl=en&ct=clnk&gl=us

    Cached version if from April 15, which was the day of the server migration.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    8 years ago

    Interesting. We’re going to need to see how that plugin works. It’s almost as if it uses its own versions of “trashed” and “pending” and such, and bypasses the WordPress system. We’ll need to take a look to be sure.

    Please share the site’s Report Number: Navigate to LiteSpeed Cache > Report, press the Send to LiteSpeed button, make note of the “Report Number”, and post it here so we can look up the report on our end.

    If you know the name of the plugin, that would be helpful, too.

    Thanks!

    Thread Starter designknight

    (@designknight)

    8 years ago

    I think the server administers disabled LSCache temporarily as part of their troublshooting. Hopefully that doesn’t mess with the report:

    Number – SOYMZJGQ

    Plugin – https://wordpress.org/plugins/show-future-posts-on-single-post/

    Really old plugin, not sure why the developer used it a couple years back, but it seems to do the job.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    8 years ago

    Thanks for those. And wow! That plugin was last updated eight years ago! I wouldn’t be surprised if it’s doing all kinds of things that are no longer considered standard. We’ll have a look and get back to you.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    8 years ago

    Have you seen this?

    https://wordpress.org/support/topic/bug-also-shows-draft-and-posts-in-the-trash/

    It may solve the problem. I haven’t looked deeply enough to know why LSCache might have discovered these posts when the previous cache plugin did not, but if the developer hasn’t added the above code, they should try that first.

    Thread Starter designknight

    (@designknight)

    8 years ago

    Wow! Surprised we haven’t had issue before, but maybe LSCache did a better job of scanning the old posts when we made the migration?

    I’ll add it now as it will be quicker.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    8 years ago

    Great! Let us know if you have any further issues 🙂

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

The topic ‘Google Indexing Trashed Pages’ is closed to new replies.