I'm an AI engineer who works on search and digital marketing — technical SEO, local SEO, content, and the web or product work that often sits next to it for the same clients.
Case studies list SEO work first, then other work from the same engagement when that was part of the job.
The page itself is part of the proof: crawlable HTML, structured data, llms.txt and AI crawler access you can inspect on kumararyan.dev.
Hover or focus a client to preview the case study. Open the full write-up from there.
2026 · freelance · Mobility equipment e-commerce (WooCommerce) · YMYL · United States
Heavy Duty Mobility
heavydutymobility.com is a US mobility equipment e-commerce store on WooCommerce. As a YMYL category, search and shoppers both need clear trust signals for who stands behind the brand.
EEAT/YMYL authority build for the founder: Person JSON-LD schema, sameAs corroboration across profiles
Canonical page architecture
Collection page copy rewritten for scannability and search intent
Blog trust-box module surfacing author credentials
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Example Ledger Studio?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Example Ledger Studio is a fictional practice used only to demonstrate FAQPage JSON-LD."
}
}
]
}
Short takes — not a manifesto. Positions I will defend.
Geotagging GBP photos does not work the way people claim
Google strips EXIF on upload for Business Profile photos. Treat geotagged-photo tricks as folklore unless you have primary-source proof that still holds.
Link volume is not authority
A pile of irrelevant links is not EEAT. Relationship-based placements and clear entity corroboration beat bought volume on YMYL sites.
If AI crawlers cannot render it, AI cannot cite it
Empty shells, blocked GPTBot rules and client-only HTML are silent failure modes. Check robots and rendered responses before arguing about prompts.