The URLs sent via IndexNow return a 403 error, what should I do?

A 403 response from the IndexNow API means that the key could not be validated: for example, its file is missing or its contents do not match the submitted key. Reducing submissions does not fix an inaccessible or incorrect key.

  1. In the module’s Security key tab, check the configured IndexNow key.
  2. Check that https://www.example.com/YOUR-KEY.txt, replacing the domain and key with your shop’s values and including its subfolder before the filename if applicable, is publicly accessible and contains exactly that key. Password protection, a firewall rule or a blocked file can prevent validation.
  3. If needed, use Delete security key, then Generate security key in the module. Check that the new file is accessible.
  4. Resubmit an affected URL and check the IndexNow response. 200 means the submission succeeded; 202 means the URL was received and key validation is pending. These responses do not guarantee that the page will be indexed.

The module can also display 403 when no submission result was obtained for a page. If the file is accessible and contains the correct key, or if the code persists, contact support with the page URL and the attempt date so that the actual response can be checked.

Sources: IndexNow response documentation.

Other FAQs in this category