SUKI SONG Guides
Get found — by Google, and by AI.
Field notes on making a website discoverable: indexed by Google and cited by ChatGPT, Claude, and Perplexity. No hype, no invented numbers — the stack I actually ship, explained. If you would rather have it done, that is Get Found.
-
Why is my business email going to spam?
Domain moved and now email goes to spam?
A platform migration quietly drops SPF, DKIM, and DMARC. How to read one bounced header, confirm which record is missing, and restore all three in the account that actually serves your DNS.
Read the guide →
-
Who controls my domain and DNS?
Who actually serves your DNS records?
Registrar, DNS host, site host, and email provider are often four different accounts. How to find which one serves your records in two commands, why a record added in the wrong place does nothing, and the register to write down once.
Read the guide →
-
What does AI see on my website?
What AI actually sees when it looks at your site
Most AI crawlers do not run JavaScript. This is what they receive instead, measured across real sites, plus the one command that shows you what yours sends.
Read the guide →
-
How do I get my website cited by ChatGPT?
How this site is built to get cited by ChatGPT, Claude & Perplexity
A file-by-file teardown of the stack that makes this site citable by AI: llms.txt, Markdown twins, a Schema.org @id graph, and an AI-crawler allowlist.
Read the guide →
-
What is llms.txt?
What is llms.txt — and does your site need one?
A practitioner’s explainer on llms.txt: what it is, what goes in it, when it helps and when it doesn’t, how to write a good one, and a real example.
Read the guide →
-
Why doesn’t my website show up on Google?
Why your website doesn’t show up on Google
A step-by-step self-diagnosis for a site that isn’t showing up on Google: indexing, robots/noindex, canonicals, thin content, schema, and speed.
Read the guide →