Consulting packages
OGKit finds problems the free tool cannot always fix for you: crawler SSR, image pipelines, China share surfaces, and safe unfurl infrastructure. These are fixed scopes, not a vague hire-us form.
Choose the package that matches your situation, then email the package name, URLs, and stack. The email template fills in the useful prompts.
Full-site OG audit
When it fits
You are shipping or rebranding a site, keep finding broken share cards, or bots and browsers receive different HTML.
Email about this packageWhat you get
- Prioritized findings across the agreed URL set
- Multi-platform preview matrix
- Crawler-access and UA-divergence notes
- Fix list mapped to OGKit rule ids
- Written report ready for your issue tracker
SPA / SSR prerender retrofit
When it fits
Share tags appear only after client hydration, so curl and social crawlers see an empty shell.
Email about this packageWhat you get
- SSR or prerendered OG and Twitter tags in the first HTML response
- A stack-appropriate approach without a default full rewrite
- Static-fetch and official-debugger verification
- A short runbook for future routes
Dynamic OG images and brand templates
When it fits
You need per-page share images, safer dimensions and byte sizes, or a consistent brand frame without manual exports.
Email about this packageWhat you get
- An edge-friendly image generation pipeline
- One or two branded templates with safe zones
- Platform-specific size and format budgets
- Documentation for templates and cache regeneration
Self-hosted unfurl service
When it fits
Your product needs in-app link previews without sending every URL to a third-party API, with SSRF-safe fetching on your infrastructure.
Email about this packageWhat you get
- Fetch, parse, and normalize service for OG, Twitter, and JSON-LD
- SSRF protection and redirect limits
- Bounded cache and invalidation strategy
- Deployment notes and a small integration example
How to contact
Email is the primary channel. Write to consulting@akr.moe.
A useful first message includes:
- Which package (or “not sure”)
- The public URLs or product surface in scope
- Framework, hosting, and relevant infrastructure
- Your deadline, if any
- Optionally include OGKit rule ids or a report link so we can skip re-diagnosis.
Free-tool questions and bugs belong on GitHub Issues. Consulting is for changes to your site or infrastructure.