1

When I go to the search console site and go to Crawl -> Sitemaps 

https://www.google.com/webmasters/tools/sitemap-list?hl=en&authuser=0&siteUrl=myURL.com

I see the table with 1 entry /sitemap.xml and 45 submitted, no data about indexed and the indexed column says Pending.

However a call against the webmasters v3 api for this sitemap returns 45 submitted, 0 indexed and pending = false.

That last bit is giving me a lot of trouble in our automated error reporting since the sitemap is clearly not done processing (indexed is normally between 43 and 45) but the cron job that looks at the API flags an alert with 0 indexed.

Has anyone encountered this issue and can help out?

EDIT: I should mention that at some point the search console UI switches from pending to giving the actual number of indexed pages. The problem is the API always returning false for the is_pending property.

screnshot of api vs search console

Improve this question
3
  • what is the problem, where you want to be helped out? Google isn't quite fast on sitemap eating. i would say: check twice, whether your sitemaps are standard conform, not blocked through robots and contain only canonical urls answering 200. Then wait. Google's tools are distributed on many different datacenters, your data runs and is aggregated through many caches - there i snothing you can do, beside of ensure you provide correct data and wait.
    – Evgeniy
    Oct 17, 2016 at 20:26
  • That sounds like a bug in the API to me. Have you tried reporting it to Google via the product forums? productforums.google.com/forum/#!forum/webmasters
    – Stephen Ostermiller ♦
    Oct 18, 2016 at 8:03
  • I've posted in the product forum but haven't gotten a reply yet. as for @Evgeniy, please read the question carefully. This isn't about the speed of indexing but about the API returning false information (i.e. that the sitemap is "not pending" when it actually is.
    – Killerpixler
    Oct 18, 2016 at 12:16

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.