AI SEO audit

An AI SEO audit that runs itself and shows what changed

A one-off AI SEO audit goes stale the week after it is run. WriteWorks crawls your site on a schedule, up to 10,000 pages on Enterprise, and keeps every audit. Compare any two to see which issues were fixed, which are new and which are still open, follow the trend crawl by crawl, get a weekly summary by email, and hand each page's fix to a developer as a ready brief.

Free Trial See the platform

7-day trial · Cancel anytime

A live crawl in progress: the progress bar, the four crawl steps from robots.txt to scoring, and each page appearing as it is checked with its status, JavaScript share, schema and bot access (sample data).A live crawl in progress: the progress bar, the four crawl steps from robots.txt to scoring, and each page appearing as it is checked with its status, JavaScript share, schema and bot access (sample data).

Connects to the tools your team already uses

The platform

See WriteWorks in Action

This is the working product, not a mockup: the same visibility scores, briefs and published content your team would be looking at. Start a free trial and point it at your own domain, or take the tour of what sits behind the screen.

Get started
Surge45
Home
Ask AI
Opportunities128
Research
Create
Measure
AI visibility
AI discoverabilityNew
AI crawlers
Reports
Context
Support
Settings
Sign out
SCSam Cartersam@example.com
WRITEWORKS
Measure/AI discoverability
Search brands, prompts, competitors…⌘K
New
1.2M (62%) leftAsk AI
AI discoverability
Measure
Overview
Issues
Pages
Bots
Settings
AI discoverability
How well your indexable pages can be accessed, understood and cited by AI search tools. Click any card for the detail behind it.
The challenge

Why one-off AI SEO audits fall short

Snapshots go stale, and two exports aren't a comparison.

Audits are snapshots

An AI SEO checker you run once tells you about one day. A template change next month can undo the fixes, and nobody notices until traffic from AI answers dips.

Two reports don't make a comparison

Putting last quarter's export beside this one by hand, URL by URL, is slow, and it can't tell a fixed issue from a page that simply disappeared.

Findings don't reach the people who fix them

A developer needs the evidence, the steps and how to check, not a screenshot of a dashboard. Writing that ticket for every page is a job in itself.

Large sites get sampled

Audits that stop at a few hundred URLs miss the templates where problems actually repeat.

The solution

How the AI SEO audit runs

Crawl on a schedule, compare audits, follow the trend, brief the fix.

Add your website and the first crawl runs automatically within a day. After that WriteWorks crawls weekly by default, or monthly, or only when you press New crawl. Scheduled crawls use no AI tokens; manual crawls use plan tokens for JavaScript rendering.

◆How the AI SEO audit runsLIVE
WriteWorks AI discoverability score. Close-up: Crawl picker, coverage line, PDF report and New crawl (sample data).WriteWorks AI discoverability score. Close-up: Crawl picker, coverage line, PDF report and New crawl (sample data).
Success story

What real brands fixed with WriteWorks

What each brand fixed, measured before and after with the same audit, in their own words.

Homepage entity markup 0% → 100%

“Nobody had spotted that our market homepages carried no structured data at all. Now 100% of them tell AI exactly who GraftPal is, and every FAQ page in the audit carries a modified date.”

GP
GraftPal teamRead the GraftPal success story
Capabilities

An AI search audit you keep running

Everything that turns one crawl into a history.

Scheduled crawls

Weekly by default, monthly or manual, with the first crawl automatic.

Compare audits

Resolved, new and persisting issues, with the reason for each.

Lost from results

On any issue, the pages that dropped out since the earlier crawl, and why.

Trend charts

Score, pillars, issues and pages, from daily to yearly.

Weekly summary email

Score and change, what went well and where to focus next.

Developer fix briefs

Copy for developer or download as Markdown, built from the crawl's evidence.

CSV export

Affected URLs for any issue, and the full Pages list.

Crawl scope controls

Set a lower page maximum, and include or exclude paths.

Time savings

What changes

From a quarterly snapshot to a weekly, provable record.

TaskBeforeWith WriteWorksTime saved
Re-run the audit every weekRemember to do itScheduled, first crawl automaticThe calendar slot
Show what a sprint fixedDiff two exports by handCompare audits: resolved, new, persistingHalf a day
Brief a developerWrite the ticket from scratchCopy the page's fix briefPer page
Keep stakeholders updatedA monthly status emailWeekly summary after each crawlThe write-up
Included

What's included

Scheduling, limits, comparisons, trends and handoff.

First crawl within a day of adding your website
Weekly, monthly or manual-only schedule
Scheduled crawls use no AI tokens
Starter 1,000, Growth 5,000 and Enterprise 10,000 pages per crawl
Client organisations get up to 5,000 pages each
Homepage and highest-traffic pages crawled first
Include and exclude paths, or set a lower page maximum
Compare the previous crawl, about 7, 30 or 90 days ago, or any two
Resolved, new and persisting issues with the reason for each
Score and pillar changes between any two audits
Trend charts grouped daily, weekly, monthly, quarterly or yearly
Weekly summary email after each scheduled crawl, with one-click unsubscribe
Fix brief per page: copy for developer or download .md
CSV export of affected URLs and pages
Turn individual checks off and re-score without re-crawling
Built for

Who uses it

The people who run, fix and report on the site.

SEO leads

An AI search audit that keeps running, with proof of what each sprint fixed.

Developers

Fix briefs with the evidence, the target and how to verify.

Agencies

The same audit for every client organisation, each with its own history.

Content and web teams

A weekly read on whether the site is getting easier for AI to read.

Featured story

“Honestly, the jobs board looked fine in a browser, so we never questioned it. The audit showed that only 5% of our job pages gave crawlers real content. We moved the listings into the server HTML, and the re-audit came back at 100%. The typical job page now carries 73% of its content before any JavaScript runs, and we're working through the rest.”

GoTeachingJobs team

Read the full story
5% → 100%
Job pages AI crawlers can read
18% → 100%
Median share of page content in the HTML crawlers get
45% → 99%
Pages passing the answer-first check
FAQ

Frequently asked questions

Everything teams typically ask before getting started.

What is an AI SEO audit?+
An AI SEO audit checks whether AI search tools can fetch, read and cite your pages: which AI bots robots.txt lets in, how much of each page is readable without JavaScript, whether structured data is present and valid, how fast the server answers and how fresh the signals are. WriteWorks runs it as a crawl of your own site, on a schedule, and keeps every result so you can see change over time.
How is it different from a one-off AI SEO checker?+
A one-off checker gives you a snapshot. WriteWorks keeps crawling, weekly by default, and stores each audit. That is what makes Compare audits, the trend charts and the weekly email possible, and it is how you catch a regression the week it ships.
How does comparing two audits work?+
WriteWorks matches every issue on every URL between the two crawls. Issues that are gone are resolved, marked fixed or page gone if the URL is no longer crawled. Issues that appeared are new, marked regressed on an existing page or new page for a new URL. The rest are persisting. URLs are normalised first, so http and https or a trailing slash don't count as a change.
How many pages does the audit crawl?+
Up to 1,000 pages per crawl on Starter, 5,000 on Growth and 10,000 on Enterprise. Client organisations in an agency or enterprise account get up to 5,000 each. The homepage and the pages that earn the most search traffic are crawled first.
What is in the weekly email?+
After each scheduled weekly crawl, a summary of the AI readiness score and its change, indexable pages and pages with issues, then what went well and where to focus next, with links into the audit. It can be turned off in notification settings or from the email itself.
Does running the audit use AI tokens?+
Scheduled crawls don't. A manual crawl uses plan AI tokens for JavaScript rendering. Fix briefs are built from the crawl's evidence and use none; the schema generator does use tokens.
Is this the same as an AI visibility audit?+
No. An AI visibility audit measures what AI engines say about your brand for the prompts your buyers ask. The AI SEO audit checks your own website: whether those engines can reach and read it. Most teams run both.
Compare audits

Every issue, matched between two crawls

Pick any two audits. Each issue on each URL lands in one bucket, with the reason.

Resolved

Gone since the earlier crawl. Marked fixed if the page is still there, or page gone if it isn't.

New

Appeared since the earlier crawl. Marked regressed on an existing page, or new page for a new URL.

Persisting

On the same URL in both crawls: the real backlog.

Explore more

Keep exploring

Related solutions, adjacent use cases, and platform features.

Hub

Inside the audit

Related

Put your AI SEO audit on a schedule

A crawl of your whole site every week, every audit kept, and a clear view of what was fixed, what is new and what is still open.

Start free trial See the platform