Jump to content

IndexNow appears to be reporting an incorrect file path?


Go to solution Solved by Daniel F,

Recommended Posts

I enabled IndexNow today as I had only just come across this feature.

It's now logging consistent errors:

403 invalid_api_key Array
(
    [host] => www.XXX.com/forums/
    [key] => b0742bd1dded481993be712b9deXXXX
    [keyLocation] => https://www.XXX.com/b0742bd1dded481993be712b9de6XXXX.txt
    [urlList] => Array
        (
            [0] => https://www.XXX.com/forums/topic/534459-wtb-exposure-2510-integrated-amplifier/
        )

)

I can see the file being referenced above in the key location has the wrong path.

That file is present at /forums/ but not at the base level as the error log shows.

As there are no settings related to this integration, I cannot address it?

Link to comment
Share on other sites

13 hours ago, Daniel F said:

I have pushed a fix which is awaiting review.

For those not familiar, what does this actually mean? It will be included in a future patch or minor update? Or is it something we can obtain soon, separately? Should we just leave IndexNow disabled until that happens? Can we get some clarity for those that are not developers or inside the 'Team' please?

Link to comment
Share on other sites

9 hours ago, Emediate said:

For those not familiar, what does this actually mean? It will be included in a future patch or minor update? Or is it something we can obtain soon, separately? Should we just leave IndexNow disabled until that happens? Can we get some clarity for those that are not developers or inside the 'Team' please?

This would mean it will be available in a future release, likely the next monthly release.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...