IndexNow governance · Updated October 23, 2026
ShadowX IndexNow release manifest
Create a release manifest that limits IndexNow notifications to changed ShadowX URLs. This guide treats ShadowX and ShadowX Market search terms as research labels, not as proof that a destination is official or safe.
List the release changes
Before deployment, record each new, revised or removed public URL and the reason its visible meaning changed. Keep admin and preview routes out of the list.
This manifest turns notification scope into an auditable decision.
Map changes to canonicals
Use the final HTTPS canonical rather than a redirecting alias or tracking parameter. Include an index page only when its visible links or copy changed.
A stylesheet update alone normally does not require URL submission.
Validate the site-specific key
Confirm that the IndexNow key file is reachable on the same origin and that the submitted key matches it exactly.
Separate site keys reduce accidental cross-property notifications.
Record API acceptance
Save the response class and timestamp without presenting acceptance as a crawl result. Follow up with Bing reports after processing.
Resubmit only after another material update or correction.
Frequently asked questions
Should admin pages appear in an IndexNow manifest?
No. Submit only public canonical URLs.
What does API acceptance mean?
It means the notification was received, not that the page was indexed.