Cross-origin resource sharing (CORS) is a mechanism to safely bypass the same-origin policy. In other words, CORS allows a web page to access restricted resources from a server on a domain different than the domain that served the web page. Occasionally, a website's CORS policy will interfere with the process of JSON-LD loading on a page. This support document describes how to confirm your website is being affected by a CORS Policy deployment issue, and some strategies to resolve it.
How To: Identify CORS-Related Deployment Problems
This section is intended to help users identify whether their markup isn't loading because of a CORS-related issue.
Step 1. Confirm Integration Scripts are Present
Either search for the required scripts in the Dev Tools> Elements tab, or enter window.schema_highlighter in the Dev Tools > Console tab.
- If you do not see the scripts: You have integration script issues to investigate.
- If you do see the scripts: navigate to Step 2.
Step 2. Search the Dev Tools>Console for 'CORS', 'schemaapp', or 'highlight.js'
Searching for these strings to see if you are brought to an Error message like the one below.
- If you do see an Error message: proceed to the section on Resolving the CORS-related Deployment Problems.
- If you do not see an Error Message: CORS policy likely isn't affecting your deployment. Review other possibilities.
How To: Resolve CORS-Related Deployment Problems
This section is outlines steps a user can take to address CORS-Related Deployment Issues
Step 1:
Step 2:
Step 3:
Step 4:
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article