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

Add SEO properties to the collection pages #3917

Closed
obulat opened this issue Mar 14, 2024 · 4 comments · Fixed by #3999
Closed

Add SEO properties to the collection pages #3917

obulat opened this issue Mar 14, 2024 · 4 comments · Fixed by #3999
Assignees
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟧 priority: high Stalls work on the project or its dependents 🧱 stack: frontend Related to the Nuxt frontend

Comments

@obulat
Copy link
Contributor

obulat commented Mar 14, 2024

These changes depend on the code changes from #3886

Problem

The collection pages do not have the SEO-related properties.

Description

The collection.vue pages added in #3886 need to have the SEO and Open Graph properties:

  • title
  • description
  • thumbnail

The Implementation plan does not give the final texts we should use for the title and description. These texts should be accessible and i18n-friendly. For instance, if the text uses the tag name in a sentence ("Cat images"), it will not be possible to translate it in some languages grammatically because the tag name ("cat" here) will need to be in a specific form, and we cannot deduct the case automatically. In Russian, for instance, "cat" is "кот", but in the "Cat images" sentence, it could be translated as "Картинки с котом"

Alternatives

Additional context

Section on SEO in the Additional search views Implementation plan: https://docs.openverse.org/projects/proposals/additional_search_views/20230719-implementation_plan_additional_search_views.html#seo

@obulat obulat added 🟨 priority: medium Not blocking but should be addressed soon 🌟 goal: addition Addition of new feature 💻 aspect: code Concerns the software code in the repository ⛔ status: blocked Blocked & therefore, not ready for work 🧱 stack: frontend Related to the Nuxt frontend labels Mar 14, 2024
@zackkrida zackkrida added 🟧 priority: high Stalls work on the project or its dependents and removed 🟨 priority: medium Not blocking but should be addressed soon labels Mar 25, 2024
@zackkrida
Copy link
Member

zackkrida commented Mar 25, 2024

@WordPress/openverse-frontend we can use this issue to discuss the specific language to be used. I would propose very simple initial titles, with the automatic " | Openverse" suffix on each:

  • {tag} {mediaType} | Openverse: "Dog images", "Field-recording audio tracks"
  • {creatorName} | Openverse: "zackkrida", "sarayourfriend" [Deliberately non-specific in the future event of multi-media type creators]
  • {provider} {mediaType} | Openverse: "Flickr images", "ccMixter audio tracks"

@obulat obulat removed the ⛔ status: blocked Blocked & therefore, not ready for work label Mar 25, 2024
@sarayourfriend
Copy link
Contributor

Those look good to me.

@obulat
Copy link
Contributor Author

obulat commented Mar 26, 2024

  • {tag} {mediaType} | Openverse: "Dog images", "Field-recording audio tracks"

  • {creatorName} | Openverse: "zackkrida", "sarayourfriend" [Deliberately non-specific in the future event of multi-media type creators]

  • {provider} {mediaType} | Openverse: "Flickr images", "ccMixter audio tracks"

As discussed previously, I asked about these titles in the #polyglots channel of Make Wordpress Slack channel.

@obulat
Copy link
Contributor Author

obulat commented Mar 29, 2024

Based on the replies in Slack channel, I think we should use these titles and add notes to translators in the comments on the dynamic nature of the tag, asking to adjust the sentence if necessary. We could include an example translated Spanish sentence: {mediaType} etiquetadas como {tag} | Openverse

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟧 priority: high Stalls work on the project or its dependents 🧱 stack: frontend Related to the Nuxt frontend
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants