How to Run an AI-Powered Page Review
Set one up, read what comes back, and turn it into work — without a page changing until you say so.
A review is a full pass over a page by the AI specialists — design, copy, SEO, accessibility and bugs — across desktop, tablet and mobile. It reports what it finds and changes nothing. What you do about it is a separate decision, and this article covers both.
What you can review
| Source | Available |
|---|---|
| A live or staging page, added by URL | Yes — this is how reviews run today. |
| A WordPress page through the Atarim plugin canvas | Yes |
| The Chrome extension | Yes |
| The injectable script | Yes |
| An uploaded mockup or screenshot | Coming soon |
Setting one up
The sentence describing what you want looked at shapes the whole review, and matters more than which preset you pick.
Instructions:
Brand guidelines
Under AI Settings you can set the guidelines the review judges against, at two levels:
Switch on Use Global Settings to inherit the global set. Project settings take precedence where both exist. The toggle is a paid-plan feature — on lower plans it shows an upgrade prompt rather than switching.
The four stages
Once started, a review runs in the background through four stages.
| Stage | What happens |
|---|---|
| 1. Strategic Overview | Claro reads the page and reports back before anyone else starts. Only Claro is active here. |
| 2. Team handoff | The brief passes to the specialists you enabled. |
| 3. On-page comments | Findings appear pinned to the elements they relate to. |
| 4. Summary and next steps | A consolidated report of what was found and what to do. |
What the specialists actually read
Two specialists also get a pass of their own, where that data was captured with the page: Glitch reviews what the browser logged, and Index reviews the page’s metadata. Each counts as its own pass within the review. Index’s keyword and competitor research sits outside a review — ask him for that in chat or on a task.
Reading what comes back
Findings appear as tasks pinned to the elements they relate to, colour-coded by priority.
| Priority | Covers | When |
|---|---|---|
| Critical | Breaks core functionality, blocks a journey, or causes a severe clarity or accessibility failure. | First. |
| High | Major impact on experience, conversion, accessibility, discoverability or trust. | Next. |
| Medium | Clearly relevant, but not blocking anything. | After those. |
| Low | Polish — line breaks, minor typography. | When there’s time. |
The summary report
Alongside the pinned findings you get one consolidated report:
Where the report lives afterwards
The report is not just something you read once in the review. Every completed review saves one, and they collect in a card called Artifacts that sits on your Projects screen alongside your projects. Open it and you are in the same Collaborate view you use everywhere else, with the report in place of a page.
Each report is also listed under Artifacts in a project’s Assets tab, so the ones belonging to a particular site are findable from that site rather than only from the shared card. If a report is not showing against the project you expect, use Assign projects on the Artifacts card to attach it.
Turning findings into work
A finding arrives pinned to the element it’s about, and nothing on the page has changed. Findings are internal — nothing appears to a client because a check ran.
Instructions:
Getting the work done
Reviews change nothing. When you’re ready, ask Atarim to work through the findings, and scope it — “just the critical ones”, “only the mobile problems”.
Running it again
Run another review the same way you ran the first one. Each cycle looks at the page as it is now, so re-running after a round of fixes shows what’s left rather than repeating what you’ve done.
Credits
Reviews use credits from one pool shared across everyone in the workspace. Availability is checked before a review starts, so you’re told up front rather than partway through.
Frequently asked questions
Does a review change my site?
No. A review reports and changes nothing. Making changes is a separate request, and anything needing sign-off waits for your approval.
Can I review a page that isn’t added by URL?
Yes. Reviews run on a page added by URL, through the Atarim WordPress plugin canvas, through the Chrome extension, or via the injectable script. Uploaded mockups and screenshots are still coming soon.
Do I have to pick the specialists?
No — presets enable the relevant ones. Use Custom when you want a particular lens on something.
How long does a review take?
The screen sizes are worked in parallel, but a check is a background job rather than an instant one — findings populate as each pass finishes. You don’t need to keep the tab open.
Can I stop one partway through?
Yes. Stop Review halts it — anything already found stays, and nothing further is generated.
Who can see the findings?
Your team. AI activity is hidden from clients and guests by default, so nothing a review produces is visible to them unless you choose to share the task.
What if I apply something and change my mind?
An Undo control appears on the comment after a change has been applied, and puts the original back. Going further than one element means rolling the page back or restoring from a backup.
Will it suggest the same thing twice?
Only if it was left unresolved. Anything you’ve already applied or dealt with won’t come back.
Does it judge the page on its own?
No. The homepage is provided as a reference when you add a project, so internal pages are assessed against the rest of the site for consistency and brand alignment.
How much does a review cost?
It uses credits from one pool shared across the workspace. Each screen size is a separate pass, and the console and metadata passes count separately again, so a full review costs more than a narrow one.
Common issues
- Review This Page isn't available — the source isn't supported yet. Uploaded mockups and screenshots can't be reviewed. Use a page added by URL, the Atarim WordPress plugin canvas, the Chrome extension or the injectable script.
- A specialist you wanted didn't take part — the preset didn't include them. Use Custom and toggle them on.
- Results feel generic — add a description before starting, and fill in brand guidelines under Advance Settings.
- The review won't start — the workspace may be out of credits. Check availability in your workspace AI settings.
- More findings than expected — detection reaches into nested layouts. Work by priority, not down the page.
- A client asked about a finding — they shouldn't have seen it. AI activity is hidden from clients and guests by default; check whether the task was shared deliberately.
- The same suggestion came back — it was left unresolved. Apply it or deal with it and it won't come back.
- You applied something and want it back — use the Undo control on that comment. Going further than one element means rolling the page back or restoring from a backup.
- Nothing changed after the review — expected. Reviews never change anything; ask for the work separately.
Conclusion
A review gives you five perspectives on a page in the time it takes to make a coffee, and none of them touch the site. The two things that most affect what you get back are a sentence of context before you start and brand guidelines filled in beforehand.
Read first, fix second. Work the priority order rather than the page order, then ask for the work — and send the report rather than the finding list. Explore Getting The Most Out Of The InnerCircle.
Tips & best practices
- Write a description every time; it changes results more than any setting.
- Fill in brand guidelines, globally once and per project where it matters.
- Run reviews once the page is basically finished.
- Hover the device marker before hunting for a problem — it tells you which screen size it was spotted at.
- Work by priority order, not down the page.
- Read the whole review before applying anything.
- Use Show me to see a change before you keep it.
- Send the summary report to clients, not the raw findings.
- Start a new cycle after a round of fixes to see what's left.
- Check credits before a large multi-page sweep.