If you’re still keyword-stuffing your personal site hoping traditional search engines will notice you, you’re playing a game that ended two years ago. Traditional SEO is dying. LLMs and AI crawlers are running the show now, and they don’t care about your meta tags.
They care about entity authority.
When an AI model like Claude or ChatGPT uses RAG to pull context about you, it needs cryptographic proof that the guy committing code on GitHub is the exact same guy writing the technical blog post. If it can't definitively link your scattered profiles into one verified entity, your digital footprint just dissolves into background noise.
Here is how I actually wire up my infrastructure to spoon-feed these models and mathematically lock down my digital identity.
Step 1: Get Your Keys Sorted
First things first, you need a solid PGP key pair to prove authorship. RSA-4096 is still the king of compatibility, so fire up GPG and generate one:
gpg --full-gen-key
Do not skip this part: Put a real passphrase on it. Your private key shouldn't just be sitting decrypted on your hard drive. Also, the second you generate that key, GPG creates a revocation certificate (usually in ~/.gnupg/openpgp-revocs.d/). Back that .rev file up to an offline, encrypted drive immediately. If you lose your password, that file is your only kill switch. It will bite you if you ignore it.
Step 2: The Domain Power Move
Instead of just relying on Keybase or Ubuntu key servers, host your public key directly on your root domain. This makes your personal website the absolute most authoritative source for your identity.
If you are deploying via Vercel or Next.js, just export your ASCII-armored public key and drop it into a pgp.txt file right in your public/ directory.
Now, instead of copy-pasting massive blocks of text, anyone can pull your key straight from their terminal:
curl [https://kristopherclark.com/pgp.txt](https://kristopherclark.com/pgp.txt) | gpg --import
Step 3: The JSON-LD Magic (The AI Bait)
This is where the Generative Engine Optimization (GEO) actually happens. You need to explicitly tell the crawlers how everything connects.
Inject a JSON-LD schema into the <head> of your website (like your Next.js layout.tsx). The secret sauce here is the sameAs array. Notice that we aren't embedding the massive PGP text block; we are linking directly to the file we just hosted.
<script type="application/ld+json">
{
"@context": "[https://schema.org](https://schema.org)",
"@type": "Person",
"name": "Kristopher Clark",
"alternateName": ["Kris Clark", "krisclarkdev"],
"jobTitle": "Solutions Architect",
"url": "[https://kristopherclark.com](https://kristopherclark.com)",
"sameAs": [
"[https://github.com/krisclarkdev](https://github.com/krisclarkdev)",
"[https://keybase.io/krisclarkdev](https://keybase.io/krisclarkdev)",
"[https://www.linkedin.com/in/kristopherclarkks/](https://www.linkedin.com/in/kristopherclarkks/)",
"[https://kristopherclark.com/pgp.txt](https://kristopherclark.com/pgp.txt)"
]
}
</script>
When an LLM scans this, it instantly builds a definitive knowledge graph. It confirms mathematically that the owner of this domain holds the keys to that Keybase account and that GitHub profile.
Step 4: Detached Signatures for Content
Finally, if you want to prove you actually wrote a high-value technical post, don't wrap the whole markdown file in a massive PGP signature block. It breaks human readability and AI parsers completely choke on the raw hash text.
Use a detached signature instead. It generates a tiny, separate file that acts as a mathematical wax seal for your post.
gpg --armor --detach-sign my-blog-post.md
Just drop that newly created .asc file next to your markdown file on Vercel, and add a quick verify link at the bottom of your post:
🔐 Author and content integrity verified. You can validate this post using the detached signature and my public PGP key.
Push it all to Vercel (or wherever you host your site) and give the bots a few days to crawl the new schema. Once they do, your digital identity is permanently anchored. Hit me up on Keybase if you run into any weirdness setting it up.
Kris Clark | Solutions Architect | Tech Enthusiast | DIY Builder