Fixed the error 'Unable to parse JSON-LD tag. Malformed JSON found' #59
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
petermann
force-pushed
the
hotfix/fix-json-ld-error
branch
from
35b0658 to
88095f9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request fixes the JSON-LD parsing error in the script, which was causing the error "[Meta Pixel] - Unable to parse JSON-LD tag. Malformed JSON found:" in the browser console and reporting as "Invalid escape sequence in string" in the Google Search Console.
Browser Console
Google Search Console
I replaced the code that was causing the error with a corrected version that follows best practices for formatting and generating JSON-LD.
This fix is important to ensure that the correct information is being transmitted to search engines and other systems that consume JSON-LD. Additionally, the proper formatting of JSON-LD improves accessibility and content indexing by search engines.
Please review the changes.
Thank you!