Content
· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FImage OptimizationAction5 issues found across 5 imagesFIX
CLinksAction28 links checked, 23 healthy, 5 brokenREVIEW
Broken Links (5)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://fonts.googleapis.com | <link> | Not Found |
| 404 | https://fonts.gstatic.com | <link> | Not Found |
| ERR | https://lemutechnologies.com/ | <link> | Get "https://lemutechnologies.com/": res... |
| 404 | https://calendly.com/lemutechnologies | <a> | Not Found |
| ERR | https://lemutechnologies.com/images/home-social-ca... | <meta> | Get "https://lemutechnologies.com/images... |
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://lemutechnologies.com/images/home-social-card.pngThe 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: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

www.lemutechnologies.com
LEMU Technologies — Custom Software, Data & Agentic AI
Custom software engineering, modern data platforms, and governed agentic AI — delivered by a principal architect with 14+ years of enterprise experience.
- 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">

WWW.LEMUTECHNOLOGIES.COM
LEMU Technologies — Custom Software, Data & Agentic AI
Custom software engineering, modern data platforms, and governed agentic AI — delivered by a principal architect with 14+ years of enterprise experience.
- og:title — LEMU Technologies — Custom Software, Data & Agentic AI
- og:description — Custom software engineering, modern data platforms, and governed agentic AI — delivered by a principal architect with...
- og:image — https://lemutechnologies.com/images/home-social-card.png
- og:type — website
- og:url — https://lemutechnologies.com/
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

LEMU Technologies — Custom Software, Data & Agentic AI
www.lemutechnologies.com
Description will be truncated (155 chars / 150 max)
- og:title — LEMU Technologies — Custom Software, Data & Agentic AI
- og:description — Custom software engineering, modern data platforms, and governed agentic AI — delivered by a principal architect with...
- og:image — https://lemutechnologies.com/images/home-social-card.png
Description will be truncated on LinkedIn (155 chars, max 150)
→ Tighten og:description to ≤150 characters
www.lemutechnologies.com
LEMU Technologies — Custom Software, Data & Agentic AI
Custom software engineering, modern data platforms, and governed agentic AI — delivered by a principal architect with 14+ years of enterprise experience.

- og:title — LEMU Technologies — Custom Software, Data & Agentic AI
- og:description — Custom software engineering, modern data platforms, and governed agentic AI — delivered by a principal architect with...
- og:image — https://lemutechnologies.com/images/home-social-card.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 DataAction1 JSON-LD block(s) found — some improvements recommended.REVIEW
JSON parse error: "Syntax error at index 1: invalid char\n\n\t<!--!-->{\"@context\":\"https://sch\n\t.^..............................\n"
JSON-LD block fails to parse — Google ignores the entire block, so structured data effectively isn't there.
Learn more ▾ ▴
Common causes: trailing comma, single quotes instead of double, unescaped quote in a string value. Validate at https://validator.schema.org/ or Search Console's Rich Results Test.
Source: schema.org / Google Search Central
JSON-LD Blocks
<!--!-->{"@context":"https://schema.org","@type":"Organization","name":"LEMU Technologies","url":"https://lemutechnologies.com/","logo":"https://lemutechnologies.com/images/LemuTechnologies.png","slogan":"Governed agentic AI, custom software engineering, and modern data platforms \u2014 delivered by experienced team members.","foundingDate":"2026","address":{"@type":"PostalAddress","addressLocality":"Coimbatore","addressRegion":"Tamil Nadu","addressCountry":"IN"},"sameAs":["https://linkedin.com/company/lemutechnologies"],"contactPoint":{"@type":"ContactPoint","contactType":"sales","email":"info@lemutechnologies.com","telephone":"\u002B91-877-826-6272","availableLanguage":["English"]}}CBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
C
62/100
Site name appears as
| Page title | Custom Software, Data & Agentic AI | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
14/20og:image set; twitter:image missing
Meta completeness
14/20Organization schema
4/15Organization schema present but missing all recommended fields
Contact 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
- twitter:card missing
- Organization schema missing logo — add a logo property pointing to a square PNG
- Organization schema missing url — point it at the canonical homepage
- Consider adding contactPoint — helps appear in "contact us" rich results
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.