The problem
Metadata bugs tend to surface late. A page looks fine in the browser, passes code review, and deploys cleanly — then someone shares it on Slack or LinkedIn and the preview is blank. By that point the fix requires a deployment, a cache purge, and another round of review.
Three failure modes show up repeatedly:
Previews that look fine locally but break in production. Open Graph tags often depend on environment-specific values: the og:image URL might be relative in development, the canonical might point to a staging domain, or the image might be behind authentication. None of these fail a build, and none are visible in the browser's DOM inspector.
Schema that fails validation post-deploy. JSON-LD is easy to write but sensitive to structure. A missing offers field in a Product schema, a wrong @type, or a malformed date string will drop the page from rich-result eligibility. These errors don't throw exceptions — they're silent until you run a validator.
Metadata drift across routes. A site might have consistent og:image on the home page and product pages, but the blog index, author pages, and category pages were added later with different templates. Over time, coverage becomes inconsistent and hard to track without checking each route.
Run the free JSON-LD Validator to catch missing required fields and rich-result issues.
How Linkraft helps
Linkraft fits into the development workflow at the places where metadata problems are easiest to fix — before they reach production.
Validate per page. The Open Graph Checker reads the live page the same way a platform crawler does. It reports what's present, whether the og:image URL is absolute and reachable, and whether any core tags are missing. The JSON-LD Validator parses the structured data block and reports schema errors against the spec — not against what search engines happen to accept today.
Fix with a spec, not a guess. When an issue surfaces, the fix path is specific: the exact tag, the correct format, and the validation step to confirm it's resolved. og:image missing walks through the three most common causes (relative URL, unreachable image, tag absent from <head>) with the correct values for each.
Re-check after deployment. Run the same validators against the production URL after deploy to confirm the fix held. Environment differences — CDN rewrites, SSR vs. static, auth middleware — sometimes swallow a fix that looked correct in staging.
Monitor across routes. Once the key pages are clean, scheduled checks catch regressions before they become support tickets. Template changes, new routes, and dependency updates all get validated against the same baseline.
Recommended workflow
This sequence integrates with a standard deploy process:
- Validate a page before opening a PR. Paste the preview URL (or a staging URL) into the Open Graph Checker and JSON-LD Validator. Confirm tags are present, the image URL is absolute, and the schema parses without errors.
- Fix the issues. For common problems — missing
og:image, invalid JSON-LD, wrong canonical — the issue and guide pages include the exact tag format and correct values. - Re-check after deploy. Repeat the validation against the production URL. Confirm the image loads from the production CDN and the canonical reflects the correct domain.
- Monitor going forward. Add key routes to a scheduled check so regressions from future template changes or dependency updates surface automatically.
For sites with many routes, focus validation on pages that appear in social sharing and search: landing pages, blog posts, product pages, and any page that appears in external links. Internal tooling and account pages can be lower priority.
What you can do today
The validation tools are free and require no account:
- Open Graph Checker — inspect
og:title,og:description,og:image, andog:urlfor any URL. Flags relative paths, missing tags, and images that return non-200 responses. - JSON-LD Validator — parse and validate structured data against the schema.org spec. Reports missing required fields, wrong types, and malformed values.
- What is Open Graph? — the four tags that matter and how each platform reads them.
- og:image missing — the three most common causes and how to fix each.
For teams delivering audits and client reports rather than implementing fixes directly, see Linkraft for SEO agencies.