Based on what buyers actually ask
Auto-generated tagsFeatureAI-powered
AI discoverability
A GEO audit that shows whether AI search can read your site
WriteWorks runs a GEO audit on your own website. It crawls every indexable page, checks what AI search bots are allowed to fetch, how much of the page they can read without JavaScript, whether the schema is there and valid, and how fresh the signals are. The result is an audit you can act on: a 0 to 100 AI readiness score, every issue ranked by the share of pages it affects, and a fix brief for each page.
7-day trial · Cancel anytime
Google Search Console
Google Analytics 4
Google Ads
Ahrefs
Semrush
DataForSEO
Firecrawl
Tavily
Exa
Parallel
G2
WordPress
Webflow
Contentful
Sanity
Payload
BaseHub
Framer
Notion
Gamma
v0
Slack
Linear
Atlassian
Monday.com
Granola
Klaviyo
Customer.io
OpenAI Ads
Claude and MCP clients 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.
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
New1.2M (62%) leftAsk AI
AI discoverability
Measure
Overview
Issues
Pages
Bots
Settings
The challenge
Why sites drop out of AI answers
The access, rendering and structure problems a traffic report never shows.
AI search can't cite what it can't fetch
A single robots.txt rule, a firewall that refuses AI user agents, or a page that only renders in the browser can take a site out of AI answers. Nothing in a traffic report tells you it happened.
Classic SEO audits stop at Googlebot
A standard site audit checks what a search engine sees. AI search bots fetch differently, often without running JavaScript, and follow their own robots.txt groups.
Issues arrive as a list, not a plan
Hundreds of warnings with no sense of how many pages each one touches, or which pages earn the traffic, leave the team guessing where to start.
No way to prove the fixes landed
After a sprint of fixes, there is rarely a clean before and after showing which issues were resolved, which are new and which are still there.
The solution
How the GEO audit works
Crawl, score, rank the issues, then fix them page by page.
WriteWorks reads your robots.txt, then finds pages from the homepage, your XML sitemap and Search Console. Each page is fetched as raw HTML, timed with an AI user agent, and rendered to measure how much of the main content needs JavaScript.
Bot access (35%), machine readability (30%), freshness signals (15%) and AI search performance (20%) roll up into one 0 to 100 score. Pages that earn more search clicks count for more, so the score reflects the pages that matter.
Issues are sorted by pages affected multiplied by points lost. Each one shows the percentage of pages it touches, the affected URLs you can export, and how it changed since the last crawl.
Each page has a "How to fix this page" brief: what is wrong, the steps, what to aim for and how to check. Copy it for a developer or download it as Markdown. Schema can be generated from the page's own content, and any page can be opened in the content editor to rewrite.
Success story
What real brands fixed with WriteWorks
What each brand fixed, measured before and after with the same audit, in their own words.
“Our job pages used to reach AI crawlers as a "Loading jobs..." placeholder. One rendering fix later, the share AI crawlers can read has gone from 5% to 100%, and every job page now names itself with a proper heading.”
GT
Capabilities
What the AI search audit checks
Four pillars, from bot access to AI search performance.
Bot access checks
robots.txt evaluated per AI bot, server refusals of AI user agents, page size and server response time.
JavaScript visibility
The share of each page's main content present in the server HTML, before any script runs.
Structured data
Schema expected for each page type, and validation of the schema that is there.
Answer-first structure
One H1, a clean heading order and an opening paragraph that answers the page's question.
Freshness signals
dateModified, sitemap lastmod accuracy and IndexNow submission for changed pages.
AI search performance
Visibility in tracked AI answers, AI referrals and AI bot hits, against your own recent best.
Issues, Pages and Bots views
Filter every page by type, score, status, schema or issue, and see each AI bot's access across the site.
Reports and a weekly email
Ready-made AI discoverability report templates with PDF export, plus a weekly summary after each scheduled crawl.
Time savings
What changes
From a list of warnings to a ranked, provable fix plan.
TaskBeforeWith WriteWorksTime saved
Find out whether AI bots can reach the siteRead robots.txt by hand, bot by botPer-bot access across every pageThe guesswork
Decide which issue to fix firstA flat list of warningsRanked by pages affected and points lostTriage time
Hand a fix to a developerWrite the ticket yourselfCopy the fix brief for the pagePer page
Show the fixes workedScreenshots of two auditsCompare audits: resolved, new, persistingThe report
Included
Everything in AI discoverability
The crawl, the score, the views and the fixes.
0 to 100 AI readiness score across four weighted pillars
Pages weighted by search clicks, so busy pages count for more
robots.txt evaluated per AI bot, following the RFC 9309 rules
Server response time measured with an AI user agent
JavaScript visibility ratio for each page's main content
Schema coverage by page type, plus schema validation
Answer-first structure checks on headings and opening paragraphs
dateModified, sitemap lastmod and IndexNow freshness checks
Issues sorted by pages affected, with % of pages and exportable URLs
Compare any two audits: resolved, new and persisting issues
Fix briefs per page, copy for developer or download as Markdown
Schema generator grounded in the page's own content
Weekly or monthly scheduled crawls, with a weekly summary email
Turn checks off and re-score without re-crawling
Built for
Who uses it
The people who own whether a site can be read.
SEO and technical SEO leads
A GEO audit that covers what classic crawlers miss: AI bot rules, JavaScript dependence and answer-first structure.
Content teams
See which pages need schema, a date or a clearer opening, and fix them in the editor.
Developers
Fix briefs with the evidence, the target and how to verify, ready to paste into a ticket.
Agencies
Run the same GEO audit across every client organisation, each with its own score and report.
Featured story
Fhresh
“We're a booking marketplace, so listings are everything. Since the fixes, pages fully readable without JavaScript went from 84% to 98%, our sitemap dates finally mean something, and our full llms.txt file is real. Over a third of our audited category pages now list their businesses as structured data, with the remaining markets up next.”
Fhresh team
Read the full story72% → 98%
Pages answering crawlers in under 0.8 s
84% → 98%
Pages fully readable without JavaScript
29% → 58%
Key pages with the schema AI expects
FAQ
Frequently asked questions
Everything teams typically ask before getting started.
What is a GEO audit?+
GEO stands for generative engine optimisation. A GEO audit looks at a site through the eyes of the generative engines that answer questions with citations. In WriteWorks the GEO audit and the AI SEO audit are the same crawl: one AI readiness score, the issues behind it and the fix for each page. It checks what a classic SEO audit checks for Googlebot, then adds the AI-specific parts: which AI bots your robots.txt lets in, how much of each page is readable without JavaScript, whether structured data is present and valid, and how fresh the signals are.
How is this different from an AI visibility audit?+
They answer different questions. The AI visibility audit measures what AI engines say about your brand: whether they mention and cite you for the prompts your buyers ask. AI discoverability audits your own website: whether those engines can reach and read it in the first place. Most teams run both, because a site that can't be read rarely gets cited.
How is the AI readiness score calculated?+
Every indexable page is scored on four pillars: bot access (35%), machine readability (30%), freshness signals (15%) and AI search performance (20%). Each page starts at 100 per pillar and loses points for each issue. Pages are weighted by their search clicks, and a pillar with nothing to measure yet is left out rather than counted as zero. If more than half the indexable pages are blocked from every AI search bot, the score is capped at 40.
Which issues does the audit check?+
Bot access: pages blocked for some or all AI search bots, servers that refuse AI user agents, slow server responses, oversized pages and content that needs JavaScript. Machine readability: missing or invalid Product, Article, FAQPage, ItemList and Organization schema, and pages without an answer-first structure. Freshness: missing or stale dateModified, sitemap lastmod mismatches and changed pages not sent to IndexNow. AI search performance: pages that earn search traffic but are never cited by AI.
Can I compare two audits?+
Yes. Compare audits matches every issue on every URL between two crawls and sorts them into resolved, new and persisting, with the reason (fixed, page gone, regressed or new page). Pick the previous crawl, one from about 7, 30 or 90 days ago, or any two crawls, and see the score and pillar changes alongside.
How often does it crawl, and does it use AI tokens?+
By default the site is crawled weekly, and you can switch to monthly or manual only. The first crawl runs automatically within a day of adding your website. Scheduled crawls use no AI tokens. A manual crawl uses plan AI tokens for JavaScript rendering, and WriteWorks shows the estimate before you start it.
How many pages does it 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. You can set a lower maximum, and include or exclude paths.
Does it tell me how to fix each issue?+
Yes. Every page has a fix brief listing each issue, what is wrong, the steps to fix it, what to aim for and how to check. Briefs are built from the crawl evidence, so they use no AI tokens. For missing schema, the schema generator writes JSON-LD from the page's own text and leaves out anything it can't see rather than inventing it.
Can I run it on any site?+
It runs on the website of each brand or client organisation in your workspace, using that site's robots.txt, sitemap and, if connected, Search Console data. It is built for auditing sites you manage, not for spot-checking a competitor's.
Compare audits
Compare audits to prove the fixes worked
Pick any two crawls. WriteWorks matches every issue on every URL and sorts the difference into three buckets, with the score and pillar changes alongside.
Resolved
Issues that were on a page before and are gone now, marked fixed, or page gone if the URL no longer exists.
New
Issues that appeared since the earlier crawl, marked regressed on an existing page or new page for a URL that wasn't there before.
Persisting
Issues still present on the same URL, so the backlog shows what is genuinely outstanding.
Two audits, two questions
AI discoverability or AI visibility?
AI discoverability: can AI read your site?
This page. A crawl of your own website, scored for bot access, machine readability, freshness and AI search performance.
AI visibility audit: what does AI say about you?
Your brand across 10+ AI platforms: mentions, citations and the competitors engines recommend instead.
See the AI visibility auditAI crawler tracking: which bots actually visit?
The bots that really fetch your pages, from your own traffic, with full request logs.
See AI crawler tracking Go deeper
Inside the GEO audit
GEO score
How the 0 to 100 AI readiness score is weighted, banded and capped.
How the GEO score worksSchema markup checker
Schema coverage by page type, validation, and JSON-LD generated from the page.
Check your schemaJavaScript SEO
How much of each page AI bots can read before any script runs.
Audit JavaScript renderingAI bot access
Your robots.txt, read the way each AI bot reads it, page by page.
Audit robots.txt for AISchema markup generator
JSON-LD for up to 10 flagged pages at a time, written from each page's own content.
Generate schemaAnswer-first content
One H1, headings in order and an opening that answers the title's question.
Check content structureAI crawler speed test
Server response time with an AI user agent, and the 2 MB page size limit.
Test response timeSitemap checker
Whether sitemap lastmod and dateModified match real content changes.
Check your sitemap dates Explore more
Keep exploring
Related solutions, adjacent use cases, and platform features.
Run your first GEO audit this week
Add your website and WriteWorks crawls it within a day: an AI readiness score, every issue ranked by reach, and the fix for each page.