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
Follow up from #663. See https://developers.google.com/search/docs/appearance/site-names#alternative.
Google proposed this Schema.org markup for alternameName:
alternameName
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "WebSite", "name": "Buttered Toast", "alternateName": ["BT", "B-T", "Buttered Toast Shop"], "url": "https://www.example.com/" } </script>
For long names, such as "The SEO Framework," it would be nice to allow "TSF," but there's currently no proper way to add these alternate names.
When implemented, we should forgo automating this field like we currently do.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Follow up from #663. See https://developers.google.com/search/docs/appearance/site-names#alternative.
Google proposed this Schema.org markup for
alternameName
:For long names, such as "The SEO Framework," it would be nice to allow "TSF," but there's currently no proper way to add these alternate names.
When implemented, we should forgo automating this field like we currently do.
The text was updated successfully, but these errors were encountered: