The finished page
The browser runs JavaScript and shows the content available after the page finishes loading.
We request your page the way ChatGPT, Claude and Perplexity do, with no JavaScript, and show you exactly what they can read.
JavaScript rendering SEO
A browser runs JavaScript before showing the page. An AI crawler may read only the original HTML response. This difference matters for server-side rendering SEO and technical visibility.
The browser runs JavaScript and shows the content available after the page finishes loading.
The crawler reads the HTML returned before JavaScript runs. Client-only content may be missing.
Evidence in the report
The report separates rendering, content, and access signals so you can see what an AI crawler received.
Count the words and links available in the original HTML response without JavaScript.
See whether robots.txt allows or blocks the named AI crawlers we check, including GPTBot.
Get a diagnosis of server-rendered, partially rendered, or client-only content from the two page fetches.
The checker reviews robots.txt rules for about 16 named AI bots. It shows which bots are allowed or blocked and separates direct crawlers from mediated access.
GPTBot
A bot used to collect web content for model training. The report shows whether robots.txt allows or blocks GPTBot.
Retrieval crawlers
Some bots retrieve pages when an AI system needs current information. The report identifies their access route and permission status.
On-demand crawlers
Some bots fetch a page for a specific user request. The report shows whether the page is available to these crawlers.
One robots.txt view
Rules can differ by bot name. The report checks each named crawler separately so one allow or block rule does not hide the others.
Writesonic tracks where you show up across ChatGPT, Perplexity, Google AI Overviews and seven more engines, and tells you what to fix next.