Skip to content
New issue

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

Allow setting of custom alternateName(s) #670

Open
sybrew opened this issue Mar 12, 2024 · 0 comments
Open

Allow setting of custom alternateName(s) #670

sybrew opened this issue Mar 12, 2024 · 0 comments
Labels
[Impact] Structured Data [Type] Enhancement Improves anything we already have.
Milestone

Comments

@sybrew
Copy link
Owner

sybrew commented Mar 12, 2024

Follow up from #663. See https://developers.google.com/search/docs/appearance/site-names#alternative.

Google proposed this Schema.org markup for 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.

@sybrew sybrew added [Type] Enhancement Improves anything we already have. [Impact] Structured Data labels Mar 12, 2024
@sybrew sybrew added this to the 6.0.0 milestone Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Impact] Structured Data [Type] Enhancement Improves anything we already have.
Projects
None yet
Development

No branches or pull requests

1 participant