Content
· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DLinksAction200 links checked, 192 healthy, 8 brokenFIX
Broken Links (8)
| Status | URL | Found in | Error |
|---|---|---|---|
| 429 | https://tnuck.com/a/novel/js/novel-storefront.js?s... | <script> | Too Many Requests |
| 429 | https://tnuck.com/ | <link> | Too Many Requests |
| 404 | https://www.googletagmanager.com | <link> | Not Found |
| 429 | https://shop.app | <link> | Too Many Requests |
| 429 | https://tnuck.com/apps/shop/hscvk | <script> | Too Many Requests |
| 503 | https://monorail-edge.shopifysvc.com | <link> | Service Unavailable |
| 429 | https://tnuck.com/apps/shop/hscvk/eat/core | <script> | Too Many Requests |
| 400 | https://fonts.googleapis.com/css?family=Open Sans:... | <link> | Bad Request |
Redirects (2)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://cdn.gladly.com/chat-sdk/widget.j... | https://cdn.gladly.com/chat-sdk/widget.j... | <script> | 0 |
| https://cdn.gladly.com/assets/chat-sdk-v... | https://cdn.gladly.com/assets/chat-sdk-v... | <script> | 0 |
FOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
https://cdn.shopify.com/s/files/1/0630/4999/0366/files/Tuckernuck_stacked-logo-preview.png?v=1697550112The og:image URL could not be fetched. Social platforms won't be able to display it.
An unreachable og:image URL (404, DNS fail, slow timeout) means social platforms cache the failure and serve no image for hours.
Learn more ▾ ▴
Social platforms (Facebook, Twitter) cache OG metadata aggressively — including failed image fetches. A momentarily-broken og:image can leave your shares imageless for hours. Test og:image URLs in Facebook's Sharing Debugger to force re-cache after fixing.
Source: Open Graph Protocol / Facebook Sharing Debugger
The og:title tag controls the title shown in social sharing previews.
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.
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.
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
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

tnuck.com
No title set
No description
- 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 — falling back from og:image
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">

TNUCK.COM
No title set
No description
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://cdn.shopify.com/s/files/1/0630/4999/0366/files/Tuckernuck_stacked-logo-preview.png?v=1697550112
- 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
og:image is below recommended size (1200×628)
→ Upload an image ≥1200×630 for the large preview card

No title set
tnuck.com
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://cdn.shopify.com/s/files/1/0630/4999/0366/files/Tuckernuck_stacked-logo-preview.png?v=1697550112
tnuck.com
No title set
No description

- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://cdn.shopify.com/s/files/1/0630/4999/0366/files/Tuckernuck_stacked-logo-preview.png?v=1697550112
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 | ⚠ | — | — | — |
FImage OptimizationAction4 issues found across 88 imagesFIX
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 | Women’s Clothing, Dresses, Shoes & Home | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
8/15single size only
Social share image
14/20og:image set; twitter:image missing
Meta completeness
8/20Organization schema
0/15Contact info discoverable
10/10contact page + mailto link
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
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- og:title missing
- twitter:card missing
- 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+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
A+Open Graph / Twitter Card DepthOG image dimensions and Twitter card configuration look healthyPASS
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
JSON-LD Blocks
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Tuckernuck",
"url": "https:\/\/tnuck.com",
"potentialAction": {
"@type": "SearchAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https:\/\/tnuck.com\/collections\/all?q={search_term_string}"
},
"query-input": "required name=search_term_string"
},
"publisher": {
"@type": "Organization",
"name": "Tuckernuck",
"url": "https:\/\/tnuck.com",
"sameAs": [
"",
"",
"",
"",
"",
"",
"",
"",
""
]
}
}