How to test structured data
You can test structured data (JSON-LD) created in Studio.Design using the following tools:
Use Google's Rich Results Test tool to verify the accuracy of your structured data.
A tool that validates structured data schemas and lets you check for errors and warnings.
Use Google Search Console to monitor the performance and errors of your site's structured data.
Common errors and how to fix them
You may see errors in the testing tools, such as "Missing '}' or object member name." Try the common causes and solutions introduced in this article one by one.
1. Unnecessary spaces
Cause:
If your structured data contains unnecessary spaces, they may be detected as errors.
Solution:
Remove any unnecessary spaces in the structured data code.
2. Publication date format
Cause:
If the publication date format is incorrect, an error will occur. The correct format is YYYY-MM-DDThh:mm:ss+hh:mm.
Solution:
Write the publication date in the correct format.
3. Including "author" and "publisher"
Cause:
For sites published with Studio.Design, a format error will occur if you don't include "author" and "publisher" in your structured data (JSON-LD).
Solution:
Follow the steps below to edit the default string and add "author" and "publisher".
Toggle the "Structured Data Markup" switch (ON/OFF)
This resets the content and inserts the default string.
Make the necessary edits
Don't delete the "author" and "publisher" sections. Only change the parts you need to, like the URL, and then "Update" your site.
4. Straight quotation marks in titles or text
Cause:
Straight quotation marks "" in titles or body text may be detected as errors. The image below shows an example of straight quotation marks being used.
Solution:
Replace the straight quotation marks with other appropriate characters.
5. articlesection notation
Cause:
An error occurs when the "Extract body heading" for articlesection is enclosed in "".
Solution:
Remove the "". The image shows the state after removal.
6. Misaligned beginning
Cause:
In the image below, a full-width space has been added right before "@type": "Person", .
Solution:
Make sure there are no unnecessary spaces, and align the beginning of each line properly.
7. Setting multiple types
Cause:
When setting multiple types, an error will occur if the notation format is incorrect.
Solution:
Enclose the entire thing in square brackets [], wrap each individual type's structured data in curly braces {}, and separate them with commas ,. For example:
[
{structured data for Type A} ,
{structured data for Type B} ,
{structured data for Type C}
]
8. Code blocks within CMS article body
Cause:
If a code block is used within a CMS article body and the text inside that code block contains line breaks, an error may occur.
Solution:
Remove any line breaks within the code block (including paragraph breaks).
