I have this problem since version rc1. then i try to update to version rc2, still got same problem.


Category:bug» support
Status:Active» Postponed (maintainer needs more info)

Have you determined why Yahoo doesn't want to allow you access? I don't see this as a problem for xmlsitemap. You have to ask Yahoo what the problem is. I know that too frequent submission to Yahoo will cause them to deny your IP address access to the ping URL. Do you have the "Submit the sitemap when content changes" checkbox set on the admin/settings/xmlsitemap/engines page? If so unset it; yahoo doesn't like that.

Owh i see.. thanks for the guidance. Maybe you can update in documentation. either wise people maybe keep asking this thing again.

thanks for the support. i really appreciate it.

Component:xmlsitemap_engines.module» Documentation
Category:support» task
Status:Postponed (maintainer needs more info)» Active

Document the Yahoo 403 issue.

Status:Active» Fixed

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Version:6.x-1.0-rc2» 6.x-1.x-dev
Status:Closed (fixed)» Active

I have the same issue "Error occurred submitting sitemap to Yahoo!: 403" even though I disabled the "Submit whenever content changes"
I'm using the latest .dev version
my base_url in my settings.php is set correctly
I still get this error in case with Yahoo only (even when I try to submit "manually" through /admin/settings/xmlsitemap/tools)

Do I need to set up an account with Yahoo and go through the same authentication procedure as with Google? (I have no account with Bing, but Bing submission works okey)

Status:Active» Fixed

See the "Access Denied (403) errors when submitting to search engines." on http://drupal.org/node/482550:

Use of the "Submit the sitemap when content changes" checkbox can cause the search engines to give you Access Denied (403) or other errors because of the rate of submission. If your content is mostly static you may use this feature safely but if you have content that is changing with every cron.php run or user entry then the content will be submitted at the next user's page refresh. This was discussed at http://drupal.org/node/534460.

Please also be sure to re-read the information in the issues you re-open, as they may contain this exact information (like in this case).

Thanks. As I have noted in #6 I have indeed disabled the "Submit the sitemap when content changes", and I'm still getting that error in case of Yahoo. (in case of other's I'm not getting any notifications at all, not even about successful submission)
And of course, I've read that link before reopening this issue. I re-opened it precisely because it did not contain the answer to the Yahoo 403 problem!!!
Anyway, I give up on Yahoo (it's a minor search engine anyway), and so I'm not going to reopen this issue. Let someone else re-open it. But that is not to say that there is no bug in this module.

@drupalina Sorry #6 wasn't clear that you had in-fact checked everything out, so my apologies. How often is your sitemap set to be submitted?

in /admin/settings/xmlsitemap/engines
Submit the sitemap when content changes [unchecked]
Frequency of sitemap submission: Hourly

in /admin/settings/xmlsitemap
Front page change frequency: Daily
Front page priority: 1.0
Add all the links to the default language sitemap (unchecked)
Cron limit: 100 lines
Use stylesheet (unchecked)

Promotion priority adjustment: 0.3
Comment ratio priority adjustment: 0.2

I would change your Frequency of sitemap submission to daily, if not less frequent. Search engines aren't going to care about a sitemap that changes every hour. Most search engines don't crawl sitemaps more than every day.

okey. Thanks for that. I'll give it a try and report back on my logs in a day or two ;)

following #11 and #12, I did as asked - daily submissions. But Yahoo is still giving "Error occurred submitting sitemap to Yahoo!: 403." error in my watchdog.

Request: http://search.yahooapis.com/SiteExplorerService/V1/ping?sitemap=http://www.example.com/sitemap.xml

Are you sure that all this should work automatically? Are you sure I shouldn't create an account with Yahoo and go through authentication procedure as is the case with Google?

Oh, of course, definitely register with Yahoo's webmaster service.

I have the same problem (but with 6.x-1.2). The only difference is that my website is registered with Yahoo and I have the information correctly input in the Site Verifications module (6.x-1.0-rc1).

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.