Help center
Open dashboard

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.

Atarim team Updated 7 Oct 2026 · 16 min read
Atarim AI
Starting an AI page review in Atarim and picking the expert agents
Before you start

Relevant for

  • Anyone checking a page before a client sees it.
  • Anyone taking on a site they didn't build.
  • Anyone running periodic passes on sites they look after.

Required knowledge

  • Familiarity with projects and tasks in Atarim.
  • No specialist background needed — findings explain what's wrong and why it matters.

Tools & resources needed

  • A project in Atarim. Reviews run on a live or staging page added by URL, through the Atarim WordPress plugin canvas, through the Chrome extension, or via the injectable script — and on an uploaded design, by asking Claro in workspace chat (Beta).
  • Credits available in the workspace. They come from one pool shared across everyone.
  • Brand guidelines in your Brand Kit, set globally and overridden per project, if you want the review judged against your standards rather than general ones.

A review is a full pass over a page by the AI specialists — design, copy, SEO, accessibility and bugs. It works down the page one screen-height section at a time and checks each section at 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

SourceAvailable
A live or staging page, added by URLYes — this is how reviews run today.
A WordPress page through the Atarim plugin canvasYes
The Chrome extensionYes
The injectable scriptYes
An uploaded mockup or screenshotYes — ask Claro in workspace chat (Beta); there’s no canvas button yet.
Note
A review needs a page Atarim can load. That means a live or staging page added by URL, a WordPress page through the plugin canvas, the Chrome extension, or the injectable script. Uploaded mockups and screenshots are reviewable too, by asking Claro in workspace chat (Beta) rather than from the canvas.
Note
This is about where a review can be started. It’s separate from the WordPress plugin, which is what lets the AI save changes to a site — that’s available now. Explore the WordPress Plugin.

Setting one up

The sentence describing what you want looked at shapes the whole review, and matters more than which preset you pick. Guests and collaborators can’t start a review.

Instructions:

  1. On Projects, select Open on the project’s card, then open the Review tab in the sidebar. It shows Work with your InnerCircle and the presets. If you see a plain comment box instead, select the switch icon at the top of the tab (its tooltip reads Switch to AI review).
  2. Pick a preset — Perfect my design (Pixel), Find accessibility gaps (Navi), Increase conversion rate (Navi and Lexi), Make this page faster (Index), Improve SEO (Index and Lexi) or Fix what’s broken (Glitch) — or choose Custom to write your own prompt and pick the specialists yourself. A preset fills in the description and replaces anything already typed there. Typing in the box before you pick one counts as Custom. Either way the tab moves on to Let’s invite your InnerCircle.
  3. In the description box, add a sentence of your own about what you want looked at, or edit the preset’s text. This changes the results more than any other setting. You can attach up to five images or documents for context.
  4. Switch specialists on or off under Let’s invite your InnerCircle. A preset switches on the ones it needs; with Custom, switch on the ones you want. Claro’s switch is always on. Leave Ask me before Claro invites the full team on if you want to read Claro’s overview before the specialists start.
  5. Select Review This Page. It stays greyed out until the description has text. With the overview switch on, Claro replies first with a Strategic Overview; select Start Review under Ready to include the InnerCircle? to bring the specialists in.
  6. Follow the review in the tab, which now splits into Chat, where Claro and the specialists report, and Tasks, where the findings arrive section by section. You don’t need to keep the tab open.
Opening the Review tab in the sidebar
Opening the Review tab
Describing what to review
Describing what to review
Let's invite your InnerCircle with every specialist switched on and Claro's switch locked on
Choosing which specialists join
Starting the page review
Starting the page review
Recommendation
Always write the description. “Check this before it goes to the client on Friday” and “we’re trying to get more demo bookings” produce genuinely different reviews of the same page. A review can’t start without a description: picking a preset fills one in, but a line of your own context gets you a far more useful review.

Brand guidelines

You can set the guidelines the review judges against at two levels:

  • Project level — specific to this site. Open Project Brief from the Atarim menu at the left of the bottom bar.
  • Global level — your defaults across everything, in Settings › Agency Brief.
Collaborate bottom bar with the Atarim menu open and Project Brief highlighted
Project Brief in the Atarim menu
Project-level brand guidelines
Project-level brand guidelines
Settings with Agency Brief selected, showing the brief's Business Details
Global-level brand guidelines

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.

Tip
Set the global defaults once for your agency’s own standards, then override per project for client brands. It saves filling the same fields in for every site. Explore Agency Brief: Building Your Brand Kit.
Note
Generating the guidelines needs a website URL. They are built by reading a site, so the URL field at the top of the brief has to be filled in before Generate will run. It is pre-filled from the project’s own address and you can point it somewhere else. Typing the fields in by hand works without one.

The four stages

Once started, a review runs in the background through four stages.

StageWhat happens
1. Strategic OverviewClaro reads the page and reports back before anyone else starts. Only Claro is active here.
2. Team handoffThe brief passes to the specialists you enabled.
3. On-page commentsFindings appear pinned to the elements they relate to.
4. Summary and next stepsA consolidated report of what was found and what to do.
Inbox review task with Claro's Strategic Overview: Core Theme, Strategic Gaps and What Great Looks Like
Stage one: the Strategic Overview
Stage two: the team handoff
Stage two: the team handoff
Stage three: on-page comments
Stage three: on-page comments
Stage four: the summary report
Stage four: the summary report
Note
After the Overview you can Start Review to bring the specialists in, or reply first to narrow the brief — “just the conversion issues”, “ignore the blog”. Ask me before Claro invites the full team is on by default, which is what makes that pause happen. Switch it off to run the whole cycle in one go. Explore Collaborate with AI Inside Strategic Overview.
How you can tell it has actually finished
While the review runs, the Tasks tab lists one row per section of the page. A row keeps its spinner until that section has finished and its findings have loaded, so a tick never appears while results are still arriving. Above them a counter reads something like 3/7 Completed with the elapsed time, and gains 1 Failed in amber if a section does not make it. A section that fails for good shows one notice naming the reason, and its row turns red and hides its findings — that notice appears once the retries behind the scenes are exhausted, not while they are still running, so it is telling you the outcome rather than a hiccup. If the whole review fails, or you stop it yourself, the tab shows This review couldn’t finish with a Start a new review button. When the whole thing ends normally you get a single message, either that the review completed or that it completed with a number of sections failed.

What the specialists actually read

  • The page’s HTML and structure
  • Its CSS, layout and visual hierarchy
  • The copy, calls to action and tone
  • Metadata and SEO structure
  • Screen size, browser and device context

Index also reviews the page’s metadata, which 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.

Tip
Reviews are context-aware. When you add a project, the homepage is provided as a reference point, so internal pages are judged against the rest of the site rather than in isolation — design consistency, brand alignment and how calls to action are treated elsewhere.
Note
A review splits the page into screen-height sections at the width you’re viewing it, and judges each section at desktop, tablet and mobile. The sections are worked in parallel rather than one after another, but a check is a background job rather than an instant one — findings populate as each section finishes. You don’t need to keep the tab open. Select Stop to end a review early: anything already found stays and nothing further is generated.

Reading what comes back

When the review finishes, the Tasks tab lists the page section by section, each section named after what it shows, such as Hero Section or Footer Links, with its findings underneath. Each finding is its own task, pinned to the element it’s about and written by the specialist who raised it: a one-line summary of the problem, then Current (what’s on the page now), Solution (the change to make) and Impact (why it matters). It also carries a priority, colored as in the table below, and a short tag naming the issue.

Inbox showing a review's Hero Section findings and Pixel's finding with Current, Solution and Impact
A finding under its section, with Current, Solution and Impact

The review also shows up in the Inbox as one task with a Review label. Open it to read Claro’s messages from the review, or expand it to see the sections and the findings under each.

Note
Not everything the specialists raise reaches you. Once the passes finish, a validation step goes back over the findings and keeps the ones it can stand behind. The rest are set aside before any task is created. That is why a review comes back tighter than the raw output would be — but nothing on screen shows you what was dropped, so a shorter list than you expected on a page you know has problems is usually this rather than a clean bill of health.
PriorityCoversWhen
CriticalBreaks core functionality, blocks a journey, or causes a severe clarity or accessibility failure.First.
HighMajor impact on experience, conversion, accessibility, discoverability or trust.Next.
MediumClearly relevant, but not blocking anything.After those.
LowPolish — line breaks, minor typography.When there’s time.
Tip
Every finding carries a device marker — hover it and it tells you which screen size the fault was spotted at. Check it before you go looking — a problem flagged on mobile often looks perfectly fine on your desktop screen, and that’s the usual way time gets wasted.
Note
Detection reaches into nested and complex layouts, so you may see more findings than expected. Work down the priority order rather than down the page and it stays manageable.

The summary report

Alongside the pinned findings you get one consolidated report:

  • Overall impression of the page
  • Recurring themes across the specialists
  • Notes and observations from each
  • An effort estimate, adjusted to your selected experience level
  • Top priorities
  • Suggested next steps
Recommendation
The report is the thing to send a client, not the task list. It reads as a considered view of the page; forty individual findings read as a list of complaints.

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 (Beta), 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, attach it yourself.

Instructions:

  1. On the Projects screen, open the ⋮ menu on the Artifacts card and select Assign projects. Inside the card, each report’s own ⋮ menu has the same option.
  2. Under Deliverables on the left, pick the report.
  3. On the right, select each project the report belongs to. The search box finds a project by name.
  4. Select Save Assignments.

A report you never assign stays with the project it came from. Assigning it moves it, or shares it across several projects.

Each report starts as internal
A new report is Internal. To let a client see one, select Share with client on it, and select Make internal to hide it again. Clients only see the reports you have shared. This doesn’t create a public link, so the client opens the report inside Atarim.

The same ⋮ menu on the Artifacts card also has Share, which invites people to the whole card rather than to one report, and Artifact settings, Archive and Delete. Archive and Delete act on the whole card and every report in it, not on a single report. What the menu shows depends on your role. The Artifacts card doesn’t use one of your project slots.

Downloading reports as PDFs

Two kinds of report also come as a PDF you can download, keep on file or forward.

Instructions:

  1. In the Inbox, open the task the review ran in.
  2. Once the review has finished, AI Review Cycle appears under Task Attachments in the task’s details. Select its download button to save the review as a PDF.
  3. When Navi runs an accessibility check, or Index runs a Lighthouse or keywords check, their reply in the task thread carries the result as a PDF: Accessibility Report, Lighthouse Report or Keywords & Trends Report. Select the download button beside it. These replies show in Collaborate as well as the Inbox.
Inbox review task with the AI Review Cycle PDF under Task Attachments and a Keywords & Trends Report in the thread
AI Review Cycle under Task Attachments

Downloading the specialists’ reports needs a paid plan. If yours doesn’t include it, the download button shows Upgrade to download.

Turning findings into work

A finding arrives pinned to the element it’s about, and nothing on the page has changed.

Instructions:

  1. Open the finding on the element it’s pinned to.
  2. Press Show me to see the change applied to the page in front of you. Nothing is committed. The element is put back afterwards, so you can toggle the preview off to compare against the original, or regenerate it if it isn’t what you meant.
  3. Press Do It to apply it for real. Your own click needs no approval: it queues and runs in the background. When it has applied, the task moves to Pending Review and an Undo control appears on that comment.
  4. Work down the priority order rather than down the page.
A finding's proposed change previewed on the page with Show me
Previewing a change with Show me
Applying a change with Do It
Applying a change with Do It
Note
The same buttons appear on the finding’s thread in the Collaborate sidebar. They aren’t shown in the Inbox or on Boards. On a site without the Atarim plugin, the arrow beside Do It opens the platform list — WordPress is the one that applies changes today, with the others marked as coming. If Do It is greyed out, hover it to see why. The message is one of these:
  • Log in to your WordPress to use Do It
  • Your WordPress account can’t edit this page
  • Do It is turned off in the Atarim plugin settings
  • Do It works on individual pages and posts, not on listing pages like the blog or archives
  • Update the Atarim plugin to use Do It
  • Do It isn’t available on this page
Tip
Read the whole review before applying anything. A long list feels like forty jobs until you’ve seen which eight actually matter, and the priority order is there to tell you.

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”.

Warning
AI changes to live pages wait for your approval. When Atarim applies findings for you, a change to a published, private or scheduled page waits until you approve it. A request nobody decides on within 14 days is declined automatically, and nothing runs. Changes to drafts run straight away, and so does a Do It you press yourself. Read approvals properly — these are real changes to a live client site. Explore Getting The Most Out Of The InnerCircle.
Note
Changes can be put back — a single element from the copy saved before it, a page through WordPress’s own version history, and a whole site only from a backup plugin installed on it.

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.

Note
A previous suggestion will only come up again if it was left unresolved. Anything you’ve already applied or dealt with won’t reappear.

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.

Tip
A review is charged per section of the page: 10 credits for each screen-height section, plus 10 for Index’s metadata pass when Index is in the review. A long page costs more than a short one, so check what’s available before a large site sweep. Explore Credits & Usage.

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 reviewable too, by asking Claro in workspace chat (Beta) rather than from the canvas.

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 page’s sections are worked in parallel, but a review is a background job rather than an instant one — findings populate as each section finishes. You don’t need to keep the tab open.

Can I stop one partway through?

Yes. Stop ends it — anything already found stays and nothing further is generated.

Who can see the findings?

Your team. A review’s findings are created as internal tasks, so guests and clients don’t see them. To share one, open the task and select the internal icon at the top to make it visible.

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-height section of the page costs 10 credits, plus 10 for the metadata pass when Index is in the review, so a long page costs more than a short one.

Common issues

  • Review This Page isn't available — the source isn't supported. Use a page added by URL, the Atarim WordPress plugin canvas, the Chrome extension or the injectable script. On a design project the AI control reads InnerCircle coming soon instead.
  • 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 your brand guidelines in the Brand Kit.
  • The review won't start — the workspace may be out of credits. Check Settings › Credits & Usage.
  • There's no way to start a review — guests and collaborators can't start one. Ask someone on your team to run it.
  • The review says This review couldn't finish — something went wrong, so no suggestions were added. Select Start a new review to run it again.
  • More findings than expected — detection reaches into nested layouts. Work by priority, not down the page.
  • 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.

Related articles