Technical readiness resource

Why scanning 100 pages costs more than scanning one

Understand page-based audit scope, AI review usage, and the difference between reusable technical fixes and additional model requests.

More audited pages mean more retrieval and potentially more AI review work. SiteReadyFor.SI shows the discovered count and asks you to confirm the audit scope before starting.

Check the page count before you start

Five audits of one page and one audit of five pages both involve five page scans. Look at the confirmed scope before starting. A homepage check may be enough to test a shared template, while a larger audit can find differences between routes. React or Next.js does not decide the usage count; the pages included in the audit do.

Distinguish model work from fixed instructions

Technical fix explanations in SiteReadyFor.SI are reusable text and do not require a new AI call per issue. AI writing suggestions come from the content-review request when it succeeds. Provider costs depend on the selected model, token usage, and current rates. We do not infer a dollar estimate from an unknown rate.

Budget using the actual plan and result

Review the pricing page for current allowances before a larger audit. The app blocks an over-quota audit rather than automatically charging an unchecked overage. Admin access removes subscription quotas for debugging, but provider usage still exists and is recorded when available. Repeating a paid model review can incur additional provider usage.

Check your own website next.

Run an on-demand audit across crawler access, content retrieval, JSON-LD, sitemaps, and llms.txt.

Start a scan