We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visit any blog page's source, for example, of https://neon.tech/blog/remember-to-use-primary-keys-vs-unique-constraints-in-postgres shows that ld+json is outside of the <head> tag.
<head>
The ideal place to have the ld+json is in the head tag: https://webmasters.stackexchange.com/questions/77541/where-is-the-ideal-place-in-code-to-use-schema-org-markup-as-json-ld#:~:text=From%20the%20perspective%20of%20HTML,contain%20metadata%20for%20the%20document..
Right now the ld+json is at the bottom of the body tag.
body
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Steps to reproduce
Visit any blog page's source, for example, of https://neon.tech/blog/remember-to-use-primary-keys-vs-unique-constraints-in-postgres shows that ld+json is outside of the
<head>
tag.Expected result
The ideal place to have the ld+json is in the head tag: https://webmasters.stackexchange.com/questions/77541/where-is-the-ideal-place-in-code-to-use-schema-org-markup-as-json-ld#:~:text=From%20the%20perspective%20of%20HTML,contain%20metadata%20for%20the%20document..
Actual result
Right now the ld+json is at the bottom of the
body
tag.The text was updated successfully, but these errors were encountered: