Content
· 9 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
46/100
Site name appears as
| Page title | Benefit Estimator | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
8/15covers SVG
Social share image
14/20og:image set; twitter:image missing
Meta completeness
14/20Organization schema
0/15Contact info discoverable
5/10tel 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
- twitter:card missing
- No Organization schema — Google can't render your logo in the knowledge panel
- Only partial contact info discoverable — consider adding a dedicated contact page or mailto/tel link
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: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
benefit-estimator.netlify.app
Aotearoa New Zealand Benefit Estimator
Free tool to estimate your NZ benefit payments including Accommodation Supplement and income abatement.
- 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">
BENEFIT-ESTIMATOR.NETLIFY.APP
Aotearoa New Zealand Benefit Estimator
Free tool to estimate your NZ benefit payments including Accommodation Supplement and income abatement.
- og:title — Aotearoa New Zealand Benefit Estimator
- og:description — Free tool to estimate your NZ benefit payments including Accommodation Supplement and income abatement.
- og:image — https://benefit-estimator.netlify.app/screenshot.png
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — https://benefit-estimator.netlify.app/
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
Aotearoa New Zealand Benefit Estimator
benefit-estimator.netlify.app
- og:title — Aotearoa New Zealand Benefit Estimator
- og:description — Free tool to estimate your NZ benefit payments including Accommodation Supplement and income abatement.
- og:image — https://benefit-estimator.netlify.app/screenshot.png
benefit-estimator.netlify.app
Aotearoa New Zealand Benefit Estimator
Free tool to estimate your NZ benefit payments including Accommodation Supplement and income abatement.
- og:title — Aotearoa New Zealand Benefit Estimator
- og:description — Free tool to estimate your NZ benefit payments including Accommodation Supplement and income abatement.
- og:image — https://benefit-estimator.netlify.app/screenshot.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 | ⚠ | — | — | — |
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