Welcome to WebmasterWorld Guest from 54.162.168.187

Forum Moderators: Ocean10000 & incrediBILL & keyplyr

Message Too Old, No Replies

WordPress

     
2:18 pm on Feb 11, 2011 (gmt 0)

Full Member

10+ Year Member

joined:Dec 20, 2002
posts:234
votes: 0


How do you handle requests associated with WordPress?

I'm seeing HEAD and GET requests from user agents like

WordPress/3.0.2; http://example.website.com

WordPress/MU; http ://exampleblog.wordpress.com

WordPress.com mShots; http ://support.wordpress.com/contact/
(also mentioned here [webmasterworld.com] )

...Or some standard browser user agent with a referer like http : //exampleblog.wordpress.com

I assume it's a link validation tool, but none of the above confirm exactly what it's looking for, and I'm annoyed that Wordpress doesn't care to provide a link to webmaster documentation.

Some of these Wordpress requests seem to originate from spam-friendly hosts like Planetlab... if a Wordpress hit is blocked with a 403 or 503, and assuming it's not a fake user agent, what happens on the blogger's end?
7:44 pm on Feb 11, 2011 (gmt 0)

Moderator This Forum from US 

WebmasterWorld Administrator keyplyr is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Sept 26, 2001
posts:8352
votes: 340


I tried allowing it, assuming it was a link checker. Then I found my content scraped on a wordpress powered blog and dug through my logs to find the scraping event request had WordPress/* as the UA, so I block it now.
8:02 pm on Feb 11, 2011 (gmt 0)

Administrator from US 

WebmasterWorld Administrator incredibill is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Jan 25, 2005
posts:14663
votes: 99


Always blocked.
8:36 pm on Feb 11, 2011 (gmt 0)

Full Member

10+ Year Member

joined:Dec 20, 2002
posts:234
votes: 0


I tried allowing it, assuming it was a link checker. Then I found my content scraped on a wordpress powered blog and dug through my logs to find the scraping event request had WordPress/* as the UA, so I block it now.

I think it can be a link checker, because I looked up the domain in one Wordpress user agent and found an article with a link to our site. On the other hand, there's your example above... If only Wordpress would offer some documentation, I'd know better what to do.
 

Join The Conversation

Moderators and Top Contributors

Hot Threads This Week

Featured Threads

Free SEO Tools

Hire Expert Members