Forums

[resolved] RSS Error: WP HTTP Error: Could not open... http://blogsearch (4 posts)

  1. caryn@inspiredraw.com
    Member
    Posted 2 months ago #

    Hi!

    I've seen some related threads but not this exact one regarding the error message I'm getting for incoming links:
    RSS Error: WP HTTP Error: Could not open handle for fopen() to http://blogsearch.google.com/blogsearch_feeds?hl=en&scoring=d&ie=utf-8&num=10&output=rss&partner=wordpress&q=link:http://blog.inspiredraw.com/?page_id=721

    First Question
    * What problem does this broken feed create? Does this mean my blog is not being picked up properly by blogsearch.google.com or by google generally? Testing by searching on my key words is yielding mixed results.

    Second question
    * Okay, so any idea how to fix it?
    - I found a thread that had something about changing some files called magpie and I've already done that, but still getting this error.
    - I also had my host open the lines for Akismet to keep working and that doesn't seem to have affected anything here.

    I'm getting the same error re: WP News and development blog, but can live without those.

    Thanks for any help!

    Inspired,
    Caryn

  2. Otto42
    Moderator
    Posted 2 months ago #

    First answer: The only effect of this failure is that the "Incoming Links" section of your dashboard won't work. There is no other impact, Google can still see your site.

    Second answer: You may need to talk to your host to allow your site to contact those URLs, or you may need to use a plugin to alter the default http method it's using here (fopen in this case).

  3. caryn@inspiredraw.com
    Member
    Posted 2 months ago #

    Thanks so much! Unless there's something fabulous in these incoming links that I'm missing out on, I'd be thrilled to take this one off the to-do list. I really appreciate your response.

    Sorry for the slow thanks. Thought I'd set this to auto-ping me if there was a response, but I didn't get it.

  4. caryn@inspiredraw.com
    Member
    Posted 2 weeks ago #

    The feedback from Otto42 was extremely helpful as it allowed me to ignore this problem temporarily. Since I changed hosts, everything's been fine, consistent with the second answer that it was host-related.

Reply

You must log in to post.

About this Topic

Tags

No tags yet.