fix(seo): embeds de conjuntos exibem nomes dos conjuntos, e não uma frase genérica - #1658
Open
rdahis wants to merge 1 commit into
Open
fix(seo): embeds de conjuntos exibem nomes dos conjuntos, e não uma frase genérica#1658rdahis wants to merge 1 commit into
rdahis wants to merge 1 commit into
Conversation
next/head only deduplicates <meta> on name/httpEquiv/charSet/itemProp — `property` is not on that list — so the og:* tags in _app.js and the ones in each page were both emitted. _app.js rendered first and crawlers take the first occurrence, so every shared URL showed the generic site card instead of the page's own title, description and image. - key the defaults in _app.js (ogtitle, ogdesc, ogimage, ogurl, ogtype, ogsitename, imagesrc) so page-level tags replace them instead of appending; next/head keeps the last element for a given key - drop twitter:title/description/image/url from _app.js and keep only twitter:card: crawlers fall back to the og:* tags, so each page's Twitter card now matches the og card it already defines - og:url is the current path instead of always the site root, and the dataset page emits <link rel="canonical"> without the ?table= param - key og:type/og:url in blog/[slug] and docs/[slug], which were also being overridden by the defaults (og:type read "website", not "article") - strip markdown and truncate dataset descriptions at a word boundary via formatMetaDescription in utils.js Dataset pages now preview with their own name in the domain's language (pt/en/es), verified against the production backend on all three locales.
rdahis
force-pushed
the
fix/dataset-og-metadata
branch
from
August 24, 2026 00:40
db34614 to
077ee61
Compare
rdahis
changed the title
Member
Author
|
@giovanecarusoredacao @AldemirLucas esse PR faz com que os embeds de páginas de conjuntos exibam os nomes dos conjuntos, e não só aquela frase genérica de "Conjuntos de dados abertos". |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Dataset pages (and every other page) were serving two og:title / og:image tags — the generic one from _app.js first, which is the one crawlers use. Keys the defaults so page-level tags replace them. Verified locally against the production backend across pt/en/es: 0 duplicate tags on 21 pages.