Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
The og:description tag controls the description in social sharing previews.
No og:description means social cards either show no subtitle or scrape the first paragraph — usually unflattering.
Learn more ▾ ▴
Without og:description, social platforms either render no subtitle or pull whatever text appears first on the page. The first paragraph is rarely written for share-card context. A purpose-written 150-200 character og:description gives a polished card.
Source: Open Graph Protocol
11 charsIdeal length is 25–60 characters for social sharing previews.
25–60 charsog:title very short — may render with awkward whitespace in social cards.
Source: Open Graph Protocol
The og:type tag helps social platforms categorize the content.
Default og:type is 'website' but the right value (article, product, profile) unlocks richer metadata fields and higher engagement.
Learn more ▾ ▴
og:type controls which other og: fields a platform respects. og:type=article enables og:article:published_time, author, and section — surfaced in news cards. og:type=product enables price/availability fields surfaced by Pinterest and shopping integrations. Default 'website' silently disables those.
Source: Open Graph Protocol
Preview

georgia.gov
Georgia.gov
No description
- twitter:card — summary
- twitter:title — Georgia.gov
- twitter:description — Add twitter:description to give the preview body text
- twitter:image — https://georgia.gov/themes/custom/ga_bloom/assets/images/social/pillars-placeholder-wide-foundation-1.png

GEORGIA.GOV
Georgia.gov
No description
- og:title — Georgia.gov
- og:description — Add og:description to give the preview body text
- og:image — https://georgia.gov/themes/custom/ga_bloom/assets/images/social/pillars-placeholder-wide-foundation-1.png
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — https://georgia.gov/
- og:site_name — Georgia.gov
og:image is below recommended size (1201×629)
→ Upload an image ≥1200×630 for the large preview card

Georgia.gov
georgia.gov
- og:title — Georgia.gov
- og:description — Add og:description to give the preview body text
- og:image — https://georgia.gov/themes/custom/ga_bloom/assets/images/social/pillars-placeholder-wide-foundation-1.png
georgia.gov
Georgia.gov
No description

- og:title — Georgia.gov
- og:description — Add og:description to give the preview body text
- og:image — https://georgia.gov/themes/custom/ga_bloom/assets/images/social/pillars-placeholder-wide-foundation-1.png
Social preview quality
Averaged across Twitter/X, Facebook, LinkedIn, and Slack.
| Field | Twitter/X | Slack | ||
|---|---|---|---|---|
| og:title | ||||
| og:description | ||||
| og:image | ||||
| og:type | ||||
| og:url | ||||
| og:site_name | ||||
| twitter:card | — | — | — | |
| twitter:title | — | — | — | |
| twitter:description | — | — | — | |
| twitter:image | — | — | — |
CBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
C
64/100
Site name appears as
| Page title | Georgia.gov logo | |
| og:site_name | Georgia.gov | |
| twitter:site | — | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
20/20og:image + twitter:image set
Meta completeness
14/20Organization schema
0/15Contact info discoverable
10/10contact page + tel link
Findings
- Brand name differs across channels — users see inconsistent identity
- No Organization schema — Google can't render your logo in the knowledge panel
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.
A+Links66 links checked, 65 healthy, 0 brokenPASS
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
A+Structured Data1 JSON-LD block(s) found — structured data is well configured.PASS
JSON-LD Blocks
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "WebPage",
"breadcrumb": {
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://georgia.gov/georgiagov-homepage"
}
]
},
"publisher": {
"@type": "Organization",
"name": "Georgia.gov",
"url": "https://georgia.gov/",
"logo": {
"@type": "ImageObject",
"url": "https://georgia.gov/themes/custom/ga_bloom/assets/images/icons/logo/ga-logo--gold.svg",
"width": "80",
"height": "90"
}
}
},
{
"@type": "WebSite",
"name": "Georgia.gov",
"url": "https://georgia.gov",
"potentialAction": {
"@type": "SearchAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://georgia.gov/search/results?query={search_term_string}"
},
"query-input": "required name=search_term_string"
}
}
]
}