ChatGPT optimization, as an engineering job.
Not tips and tactics — a checklist. Crawler access, rendering, structured facts, entity consistency and a monitor that tells you the hour ChatGPT changes its mind about you.
Audit, fix, verify, monitor.
Two weeks from audit to shipped fixes on most sites.
Six checks, in priority order.
Fixing them out of order wastes weeks.
1. Crawler reachability
robots.txt, CDN and WAF rules for every OpenAI agent. Nothing else matters until this passes.
2. Initial-HTML content
Your core claims published as readable text, verified per template.
3. Published specifics
Prices, limits, timelines and policies in readable HTML rather than PDFs or support tickets.
4. Schema and entities
Organization, Product and FAQPage markup that matches the visible page exactly.
5. Public documentation
The most-cited source type in technical answers, moved outside the login wall.
6. Continuous monitoring
Position and presence tracked weekly, with the displacing competitor named.
What each failure costs you.
Fix top-down; the lower rows cannot pay off until the upper ones pass.
Implementation questions.
It helps considerably, but ChatGPT also draws on widely-cited third-party sources. Allowing it is the simplest lever you control.
Your public content may be used in answers — which is the objective. Genuinely proprietary paths can stay blocked.
No. Publishing the critical copy as readable text is usually a scoped change, not a rewrite.
Presence and position across your tracked prompts, from stored answers you can open and read.
Yes — included on Scale, an add-on on Growth, or we hand your developers a patch-level spec.
Run the GPTBot inspection.
Free on any domain, and it tells you which of the six checks is failing.