Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
D
45/100
Site name appears as
| Page title | Find your potential spouse anonymously · Connection & Destiny | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
12/15covers apple-touch-icon + SVG
Social share image
14/20og:image set; twitter:image missing
Meta completeness
14/20Organization schema
0/15Contact info discoverable
0/10no 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
- Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
- 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.
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
The og:url tag specifies the canonical URL for the shared content.
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:site_name tag displays the website name in social previews.
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.
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

potentialspouse.com
PotentialSpouse — Find your potential spouse anonymously
Search for someone serious about marriage without your family, friends, or coworkers seeing you look. No photos. Codename only. You decide what to share, when.
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from og:title
- twitter:description — falling back from og:description
- twitter:image — falling back from og:image
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">

POTENTIALSPOUSE.COM
PotentialSpouse — Find your potential spouse anonymously
Search for someone serious about marriage without your family, friends, or coworkers seeing you look. No photos. Codename only. You decide what to share, when.
Description will be truncated (159 chars / 155 max)
- og:title — PotentialSpouse — Find your potential spouse anonymously
- og:description — Search for someone serious about marriage without your family, friends, or coworkers seeing you look. No photos. Code...
- og:image — https://potentialspouse.com/images/og-image-c1f0af57f015018b6cf440d2f6bf5113.png?vsn=d
- og:type — website
- 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
Description will be truncated on Facebook (159 chars, max 155)
→ Tighten og:description to ≤155 characters

PotentialSpouse — Find your potential spouse anonymously
potentialspouse.com
Description will be truncated (159 chars / 150 max)
- og:title — PotentialSpouse — Find your potential spouse anonymously
- og:description — Search for someone serious about marriage without your family, friends, or coworkers seeing you look. No photos. Code...
- og:image — https://potentialspouse.com/images/og-image-c1f0af57f015018b6cf440d2f6bf5113.png?vsn=d
Description will be truncated on LinkedIn (159 chars, max 150)
→ Tighten og:description to ≤150 characters
potentialspouse.com
PotentialSpouse — Find your potential spouse anonymously
Search for someone serious about marriage without your family, friends, or coworkers seeing you look. No photos. Codename only. You decide what to share, when.

- og:title — PotentialSpouse — Find your potential spouse anonymously
- og:description — Search for someone serious about marriage without your family, friends, or coworkers seeing you look. No photos. Code...
- og:image — https://potentialspouse.com/images/og-image-c1f0af57f015018b6cf440d2f6bf5113.png?vsn=d
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 | ⚠ | — | — | — |
CStructured DataActionNo structured data (JSON-LD) found.REVIEW
Adding structured data helps search engines understand your content and can enable rich results.
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