Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
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
The og:image tag provides a preview image for social sharing.
No og:image means social shares are imageless — measurably less engaging than image-cards across every major platform.
Learn more ▾ ▴
Twitter, Facebook, and LinkedIn all use og:image (or twitter:image as a fallback) for share-card thumbnails. Without one, the post renders as a text-only card. A 1200x630px image (Twitter's preferred size) covers all platforms.
Source: Open Graph Protocol
10 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: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: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
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
palmplaystore.com
Palm Store
No description
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — Palm Store
- twitter:description — Add twitter:description to give the preview body text
- 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)
PALMPLAYSTORE.COM
Palm Store
No description
- og:title — Palm Store
- og:description — Add og:description to give the preview body text
- 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 — Palm Store
No preview image for Facebook
→ Add og:image (recommended 1200×630)
Palm Store
palmplaystore.com
- og:title — Palm Store
- og:description — Add og:description to give the preview body text
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
palmplaystore.com
Palm Store
No description
- og:title — Palm Store
- og:description — Add og:description to give the preview body text
- 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.
| 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 | — | — | — |
FBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
F
31/100
Site name appears as
| Page title | Palm Store | |
| og:site_name | Palm Store | |
| twitter:site | Palm Store | |
| Organization.name | — |
Consistent
Brand assets
Favicon
8/15covers SVG
Social share image
0/20Meta completeness
8/20Organization schema
0/15Contact info discoverable
0/10no contact info discoverable
Findings
- Missing brand name in: Organization.name
- No social share image — shared links render as bare URLs
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- og:image 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.
ALinks76 links checked, 74 healthy, 2 brokenPASS
Broken Links (2)
| Status | URL | Found in | Error |
|---|---|---|---|
| 429 | https://palmplaystore.com/_nuxt/Footer.DkIHoQSd.cs... | <link> | Too Many Requests |
| ERR | about:blank | <iframe> | Get "about:blank": unsupported protocol ... |
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
Adding "description" can improve how search engines display your content.
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 "potentialAction" can improve how search engines display your content.
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
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Palm Store",
"url": "https://www.palmplaystore.com/"
}