Content - https://ibge.gov.br BeaverCheck Audit

F

Open Graph

Action

No Open Graph tags found — social sharing previews will be generic.

FIX

No Open Graph tags found — social sharing previews will be generic.

No Open Graph meta tags found

Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

Why this matters

Without Open Graph tags, social shares show a broken or empty preview card.

Learn more ▾

When someone shares your URL on Facebook, LinkedIn, Slack, iMessage, or any modern chat app, the preview comes from <meta property="og:*"> tags. Without them you get either no card or whatever fragment the social platform guesses — usually unflattering. The four core og: tags (title, description, image, url) cover what every major platform actually reads.

Source: Open Graph Protocol

Preview

No image set

ibge.gov.br

No title set

No description

Preview quality · Twitter/X F · 20/100

twitter:card — Add <meta name="twitter:card" content="summary_large_image">
twitter:title — falling back from <title>
twitter:description — falling back from <meta name=description>
twitter:image — Add twitter:image — preview card without an image looks broken

twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)

No image set

IBGE.GOV.BR

No title set

No description

Preview quality · Facebook F · 10/100

og:title — falling back from <title>
og:description — falling back from <meta name=description>
og:image — Add og:image — preview card without an image looks broken
og:type — Add og:type — Recommended — tells Facebook the content category
og:url — Add og:url — Recommended — canonical URL for the share
og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

No preview image for Facebook
→ Add og:image (recommended 1200×630)

No image set

No title set

ibge.gov.br

Preview quality · LinkedIn D · 55/100

og:title — falling back from <title>
og:description — falling back from <meta name=description>
og:image — Add og:image — preview card without an image looks broken

No preview image for LinkedIn
→ Add og:image (recommended 1200×627)

ibge.gov.br

No title set

No description

Preview quality · Slack C · 70/100

og:title — falling back from <title>
og:description — falling back from <meta name=description>
og:image — Add og:image — preview card without an image looks broken

No preview image — Slack unfurl will be text-only
→ Add og:image or twitter:image

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

F · 38/100

Field	Twitter/X	Facebook	LinkedIn	Slack
og:title		⚠	⚠	⚠
og:description		⚠	⚠	⚠
og:image
og:type
og:url
og:site_name
twitter:card		—	—	—
twitter:title	⚠	—	—	—
twitter:description	⚠	—	—	—
twitter:image		—	—	—

D

Brand Presence

Action

Site-name consistency, favicon, social image, meta tags, schema, and contact signals

FIX

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

D

44/100

Site name appears as

Page title	Twitter
og:site_name	—
twitter:site	—
Organization.name	Instituto Brasileiro de Geografia e Estatística

Inconsistent — names differ across channels

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

0/20

Meta completeness

4/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

5/10

tel link

Findings

Brand name differs across channels — users see inconsistent identity
No social share image — shared links render as bare URLs
og:title missing
og:image missing
twitter:card missing
Consider adding contactPoint — helps appear in "contact us" rich results
Only partial contact info discoverable — consider adding a dedicated contact page or mailto/tel link

How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.

B

Links

200 links checked, 196 healthy, 4 broken

REVIEW

200 links checked, 196 healthy, 4 broken

196 of 200 links are healthy

Broken link: https://www.googletagmanager.com

Found in <link href>. Returns HTTP 404.

Got: HTTP 404

Broken link: http://www4.planalto.gov.br/legislacao/

Found in <a href>. Get "http://www4.planalto.gov.br/legislacao/": read tcp 92.38.149.11:60482->170.246.255.25:80: read: connection reset by peer

Got: unreachable

Broken link: https://www.ibge.gov.br/estatisticas/todos-os-produtos-es...

Found in <a href>. Get "https://www.ibge.gov.br/estatisticas/todos-os-produtos-estatisticas.html": context deadline exceeded

Got: unreachable

Broken link: https://www.ence.ibge.gov.br/

Found in <a href>. Get "https://www.ence.ibge.gov.br/": tls: failed to verify certificate: x509: certificate is valid for *.ibge.gov.br, ibge.gov.br, not www.ence.ibge.gov.br

Got: unreachable

200 total 189 healthy 4 broken 7 redirects

Broken Links (4)

Status	URL	Found in	Error
404	https://www.googletagmanager.com	`<link>`	Not Found
ERR	http://www4.planalto.gov.br/legislacao/	`<a>`	Get "http://www4.planalto.gov.br/legisla...
ERR	https://www.ibge.gov.br/estatisticas/todos-os-prod...	`<a>`	Get "https://www.ibge.gov.br/estatistica...
ERR	https://www.ence.ibge.gov.br/	`<a>`	Get "https://www.ence.ibge.gov.br/": tls...

Redirects (7)

URL	Destination	Found in
https://sidra.ibge.gov.br/	https://sidra.ibge.gov.br/	`<a>`
https://agenciadenoticias.ibge.gov.br/ag...	https://agenciadenoticias.ibge.gov.br/ag...	`<a>`
https://agenciadenoticias.ibge.gov.br/ag...	https://agenciadenoticias.ibge.gov.br/ag...	`<a>`
https://agenciadenoticias.ibge.gov.br/ag...	https://agenciadenoticias.ibge.gov.br/ag...	`<a>`
https://agenciadenoticias.ibge.gov.br/ag...	https://agenciadenoticias.ibge.gov.br/ag...	`<a>`
https://www.ibge.gov.br/cidades-e-estado...	https://www.ibge.gov.br/cidades-e-estado...	`<a>`
https://sidra.ibge.gov.br	https://sidra.ibge.gov.br	`<a>`

200 https://scripts.clarity.ms/0.8.60-beta/clarity.js <script>

200 https://www.clarity.ms/tag/m0ro3ivus6?ref=gtm2 <script>

200 https://www.google-analytics.com/analytics.js <script>

200 https://www.googletagmanager.com/gtag/js?id=G-0VE4HSDTTT&cx=... <script>

200 https://www.googletagmanager.com/gtm.js?id=GTM-5ND2WBQ <script>

200 https://www.googletagmanager.com/gtag/js?id=UA-285486-1 <script>

200 https://ibge.gov.br/templates/novo_portal_base/imagens/icons... <link>

200 https://fonts.googleapis.com/css?family=Open+Sans:400,400i,7... <link>

200 https://ibge.gov.br/templates/novo_portal_base/css/grid.css <link>

200 https://ibge.gov.br/templates/novo_portal_base/css/estilos.m... <link>

200 https://ibge.gov.br/templates/novo_portal_base/css/menu.min.... <link>

200 https://ibge.gov.br/templates/novo_portal_base/css/estilos_c... <link>

200 https://ibge.gov.br/templates/novo_portal_base/css/menu_cont... <link>

200 https://ibge.gov.br/templates/novo_portal_base/css/modulos_c... <link>

200 https://ibge.gov.br/media/util/jquery-3.4.1.min.js <script>

200 https://ibge.gov.br/media/util/tool.js <script>

200 https://www.ibge.gov.br/ <link>

200 https://www.ibge.gov.br/templates/novo_portal_base/js/gtrans... <script>

200 https://gov.br/ <a>

200 http://www.gov.br/acessoainformacao/ <a>

200 https://www.gov.br/pt-br/participacao-social/ <a>

200 http://www.gov.br/pt-br/orgaos-do-governo <a>

200 https://www.ibge.gov.br/includes/barraBrasil.js <script>

200 https://www.ibge.gov.br/pt/inicio.html <a>

200 https://www.ibge.gov.br/templates/novo_portal_base/imagens/l... <img>

200 https://www.ibge.gov.br/?lang=pt-BR <a>

C

Structured Data

Action

2 JSON-LD block(s) found — some improvements recommended.

REVIEW

2 JSON-LD block(s) found — some improvements recommended.

Missing or invalid @context in block #1

The @context should be "https://schema.org" for search engines to recognize the data.

Got: https://schema.org/ Expected: https://schema.org

Missing required property "name" for WebSite

The "name" property is required for the WebSite schema type.

Missing recommended property "sameAs" for Organization

Adding "sameAs" can improve how search engines display your content.

Missing recommended property "description" for WebSite

Adding "description" can improve how search engines display your content.

2 JSON-LD blocks found

URL: https://schema.org/

The @context should be "https://schema.org" for search engines to recognize the data.

Expected: https://schema.org

Why this matters

JSON-LD without @context is invalid structured data — Google ignores the entire block.

Learn more ▾

@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.

Source: JSON-LD spec / schema.org

The "name" property is required for the WebSite schema type.

Why this matters

Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.

Learn more ▾

Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.

Source: Google Search Central / schema.org

Adding "sameAs" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

Adding "description" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

JSON-LD Blocks

Block 1 : Organization

7 properties Valid

Missing or invalid @context

{
  "@context": "https://schema.org/",
  "@type": "Organization",
  "name": "Instituto Brasileiro de Geografia e Estatística",
  "url": "https://www.ibge.gov.br",
  "logo": "https://www.ibge.gov.br/explica/images/logo.jpg",
  "email": "ibge@ibge.gov.br",
  "telephone": "0800 721 8181"
}

Block 2 : WebSite

4 properties Valid

Missing required property: name

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "url": "https://www.ibge.gov.br/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": {
      "@type": "EntryPoint",
      "urlTemplate": "https://www.ibge.gov.br/busca.html?searchword={search_term_string}"
    },
    "query-input": "required name=search_term_string"
  }
}

A+

Mixed Content

No mixed content detected — all resources use HTTPS.

PASS

No mixed content detected — all resources use HTTPS.

No mixed content detected — all resources use HTTPS