By the iSuggest.ai Team · Updated for 2026
The "Publish to AI Directory" button looks like one click. Underneath it, several separate checks and one live re-fetch of your page happen before anything becomes public. None of it is mysterious, and understanding the order of operations explains two things people often ask us: why a page that scored well yesterday can be refused today, and why you're never charged for a submission that fails partway through.
Two gates have to pass before anything runs
The first gate is ownership. Only the account that ran the audit — or, for an audit taken while signed out, the exact browser session that ran it — can publish it. A link to someone else's report is not enough, and this holds for administrators too; nobody gets a back door into publishing on your behalf.
The second gate is the score. iSuggest.ai will only publish a page whose audit scored 90 or higher. That bar isn't cosmetic — it's checked independently in four places in the code so it can't drift: the button on the report page (which simply disables itself and explains why below 90), the publish request itself, the API endpoint a personal key would use, and the storage layer that actually writes the snapshot. If your audit is unscored, it doesn't clear the bar either — we don't estimate a score to let something through.
A credit check, before anything is spent
Before any work happens, we check your balance against the cost of publishing to that specific provider (Gemini, ChatGPT, or Claude — pricing per directory is shown on your account page). If you don't have enough credits, you're stopped here, before a single credit moves. That ordering matters for what comes next.
The capture: a fresh look at your page, not a reused report
Here's the part people usually assume is just a copy-paste of the existing audit. It isn't. Once the gates clear, the system re-fetches and re-analyzes your live page in a fresh request — the same audit engine, run again, right before publishing. This capture step exists so the snapshot reflects what your page actually looks like at the moment you publish it, not a report that might be hours or days old. If that live re-fetch happens to fail for some reason, publishing doesn't hang — it falls back to the audit you already had on file rather than blocking you outright.
Freezing the snapshot
Once a fresh (or fallback) report is in hand, it gets frozen into a permanent record. The system computes a deterministic ID from your report and the chosen provider, so publishing the same page to the same directory twice always lands on the same snapshot — there's no way to accidentally create duplicates by clicking twice. The frozen copy strips anything that shouldn't travel with a public page, like your account email, and gets written with a create-only save: once that file exists, nothing in the normal flow can edit or delete it. That's the technical backbone of a promise we take seriously — snapshots are immutable by design, because an AI system that cites your page should be able to trust that the page it cited hasn't quietly changed underneath it.
Only now does a credit actually move
Credits are spent only after the snapshot is successfully written — not before, and not as a pre-authorization. If anything upstream fails — the score check, the capture, the write — nothing is deducted from your balance. This is the same logic covered in more depth in our post on the credit system: you pay for outcomes, not attempts.
What shows up live
The last step is simply routing you to the new page: /ai-directory/{provider}/{id}, alongside JSON and Markdown versions of the same snapshot for machines that would rather parse structured data than an HTML page. Who submitted a given snapshot stays private — visible only to the account that published it — even though the snapshot itself is public.
If you haven't run an audit yet, our workflow walkthrough covers the steps before this one, from your first audit through to a publishable score. And if you want to see what a finished snapshot actually looks like once it's live, browse the Claude directory or check how it works end to end.