Skip to content
https://atl30309.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
73
GRADE
C
FIX
3
REVIEW
3
PASS
3
INFO
0
Checks
9
3 PASS 3 REVIEW 3 FIX
F
Open Graph
Action
Open Graph tags need attention — social sharing previews may be incomplete.
FIX
Open Graph tags need attention — social sharing previews may be incomplete.
Warning::
Missing og:title
The og:title tag controls the title shown in social sharing previews.
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
Info::
Missing og:type
The og:type tag helps social platforms categorize the content.
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

The og:title tag controls the title shown in social sharing previews.

Why this matters

Without og:title, social shares fall back to the <title> tag — usually awkwardly truncated or branded for SEO not social.

Learn more ▾

og:title controls what appears as the headline in social-share cards (Twitter, Facebook, LinkedIn, Slack, iMessage). When omitted, platforms fall back to <title>, which is usually optimized for SEO (longer, brand-suffixed) and reads badly in social context. A 50-60-character og:title gives a clean preview.

Source: Open Graph Protocol

The og:description tag controls the description in social sharing previews.

Why this matters

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

The og:url tag specifies the canonical URL for the shared content.

Why this matters

Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.

Learn more ▾

og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.

Source: Open Graph Protocol

The og:type tag helps social platforms categorize the content.

Why this matters

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

The og:site_name tag displays the website name in social previews.

Why this matters

Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.

Learn more ▾

og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.

Source: Open Graph Protocol

Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

Why this matters

Without twitter:card, Twitter renders posts as plain text — no preview image, no structured layout.

Learn more ▾

Twitter requires `<meta name="twitter:card" content="summary_large_image">` (or summary) to render share-cards at all. Without it, links appear as raw text and engagement plummets vs cards. Twitter also falls back to og:image if twitter:image isn't set, so configure both.

Source: Twitter Developer Platform

Preview

atl30309.com

No title set

No description

Preview quality · Twitter/X F · 40/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from <title>
  • twitter:description — Add twitter:description to give the preview body text
  • twitter:image — falling back from og:image

  • twitter:card is missing

    → Add <meta name="twitter:card" content="summary_large_image">

ATL30309.COM

No title set

No description

Preview quality · Facebook F · 35/100
  • og:title — falling back from <title>
  • og:description — Add og:description to give the preview body text
  • og:image — https://app.element.io/themes/element/img/logos/opengraph.png
  • 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 title set

atl30309.com

Preview quality · LinkedIn B · 80/100
  • og:title — falling back from <title>
  • og:description — Add og:description to give the preview body text
  • og:image — https://app.element.io/themes/element/img/logos/opengraph.png

atl30309.com

No title set

No description

Preview quality · Slack B · 80/100
  • og:title — falling back from <title>
  • og:description — Add og:description to give the preview body text
  • og:image — https://app.element.io/themes/element/img/logos/opengraph.png

Social preview quality

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

D · 58/100
FieldTwitter/XFacebookLinkedInSlack
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

Partial brand coverage — a few channels are missing brand signals.

D

42/100

Site name appears as

Page titleElement
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

8/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
  • og:title missing
  • twitter:card missing
  • No Organization schema — Google can't render your logo in the knowledge panel
  • No discoverable contact info — trust signal is weak, legal risk is higher in regulated regions

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

C
Structured Data
Action
No structured data (JSON-LD) found.
REVIEW
No structured data (JSON-LD) found.
Info::
No structured data (JSON-LD) found
Adding structured data helps search engines understand your content and can enable rich results.

Adding structured data helps search engines understand your content and can enable rich results.

Why this matters

Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.

Learn more ▾

Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.

Source: Google Search Central / schema.org

No structured data found

Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.

Common types include:

  • WebSite — your site identity and search box
  • Organization — your company information
  • Article — blog posts and news articles
  • Product — e-commerce product pages
  • BreadcrumbList — navigation paths
Learn more at schema.org
C
Rich Results Eligibility
Action
No JSON-LD found -- no rich-result eligibility
REVIEW
No JSON-LD found -- no rich-result eligibility
Info::
No JSON-LD structured data on the page
No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.
B
Image Optimization
1 issues found across 6 images
REVIEW
1 issues found across 6 images
Warning::
6 images missing alt text
Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
A+
Mixed Content
No mixed content detected — all resources use HTTPS.
PASS
No mixed content detected — all resources use HTTPS.
Info::
No mixed content detected — all resources use HTTPS
A+
Open Graph / Twitter Card Depth
OG image dimensions and Twitter card configuration look healthy
PASS
OG image dimensions and Twitter card configuration look healthy
Info::
OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid
A+
Autoplay Media
No autoplay media on the page
PASS
No autoplay media on the page
Info::
No autoplay media on the page
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback