Independent technical audit

docs.aspose.com

Overall AI readiness score

A combined result across all audit signals.

Excellent

AI readiness audit: 9/2/2026Public technical data

Overall AI readiness assessment

How ready docs.aspose.com is for AI systems

83/100

Aspose.Words Documentation (docs.aspose.com) received an AI-readiness score of 83/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was accessible, and ai.txt was not found. The robots.txt analysis found 0 explicitly allowed and 0 blocked AI crawlers, with 1 declared sitemap. Homepage markup completeness was 60%; no Schema.org types were detected and 6 OpenGraph tags were detected. Results reflect the public site response observed on 2026-09-02T00:55:56.157Z.

Audit context

llms.txt is accessible and contains 361 tokens. An expanded llms-full.txt is also available with 2,442 tokens, giving agents more direct context. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. No Schema.org type was detected on the homepage. 6 OpenGraph tags were found and markup completeness is 60%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 44/100, Accessibility 91/100, Best Practices 92/100, SEO 100/100, and experimental Agentic Browsing 67/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

Accessible llms.txt
Expanded llms-full.txt
1 sitemap declaration

Priority improvements

1Add JSON-LD for the organisation, website, and core entities.
2Complete OpenGraph and canonical homepage metadata.
3Reduce mobile rendering delay and main-thread work.

llms.txt tokens361

llms-full.txt tokens2,442

ai.txt

sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse

Performance

Accessibility

Best Practices

100

Technical SEO

Agentic Browsing

What these results mean

Mobile performance is 44/100, with the largest visible content block appearing in 8.6 s and the browser main thread blocked for 630 ms. Layout shift was 0.005. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 91/100, Best Practices 92/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 67/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

Improve interface contrast and readability

Increase contrast for text, states, and interactive controls so both people and visual agents can distinguish content from actions and supporting labels.

FCP5.7 s

First content

LCP8.6 s

Main content

CLS0.005

Layout stability

TBT630 ms

Blocking time

SI6.2 s

Visual speed

Metric glossary

FCP · First content: When the first text or image appeared on screen.
LCP · Main content: When the largest visible element in the first viewport rendered.
CLS · Layout stability: How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time: How long the browser main thread could not respond quickly to input.
SI · Visual speed: How quickly the visible viewport filled with content.

9/2/2026Lighthouse 13.4.1Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://docs.aspose.com/words/llms.txt

llms-full.txt

Full version is available

https://docs.aspose.com/words/llms-full.txt

ai.txt

ai.txt file was not found

robots.txt

File found

https://docs.aspose.com/robots.txt

Sitemap in robots.txt1

1 sitemap found

llms.txt in robots.txt

References: llms-txt: https://docs.aspose.com/llms.txt

Schema.org (JSON-LD)

Schema.org markup was not found on the homepage

OpenGraph60%

6 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotNot mentioned

OAI-SearchBotNot mentioned

ChatGPT-UserNot mentioned

Google-ExtendedNot mentioned

ClaudeBotNot mentioned

Claude-SearchBotNot mentioned

Claude-UserNot mentioned

BytespiderNot mentioned

CCBotNot mentioned

PerplexityBotNot mentioned

Perplexity-UserNot mentioned

Sitemaps

Declared discovery routes for crawlers and agents.

https://docs.aspose.com/sitemaps.xml

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 60%

og:titleAspose Documentation

og:descriptionClass Libraries & REST APIs for the developers to manipulate & process Files from Word, Excel, PowerPoint, Visio, PDF, CAD & several other categories in Web, Desktop or Mobile apps. Develop & deploy on Windows, Linux, MacOS & Android platforms.

og:typewebsite

og:urlhttps://docs.aspose.com/

og:imagehttps://docs.aspose.com/images/Aspose-image-for-open-graph.jpg

og:site_nameAspose Documentation

# Aspose.Words Documentation
Central documentation hub for Aspose.Words across all supported platforms.
Easily create, edit, render, print your documents, as well as convert them to almost any format, such as DOC, DOCX, RTF, HTML, Markdown, PDF, XPS, EPUB, and more. All this without additional libraries and applications.

## Platforms
- [.NET Documentation](https://docs.aspose.com/words/net/): Documentation and useful links for the Aspose.Words library for .NET developers
- [Java Documentation](https://docs.aspose.com/words/java/): Guides and useful links for the Aspose.Words library for Java developers
- [C++ Documentation](https://docs.aspose.com/words/cpp/): Documentation and useful links for the Aspose.Words library for C++ developers
- [Python Documentation](https://docs.aspose.com/words/python-net/): Documentation and useful links for the Aspose.Words library for Python developers
- [Node.js Documentation](https://docs.aspose.com/words/nodejs-net/): Documentation and useful links for the Aspose.Words library for Node.js developers
- [Android via Java](https://docs.aspose.com/words/java/android/): Using Aspose.Words on Android

## Additional Resources
- [Release Notes](https://releases.aspose.com/words/): Product updates and version history
- [Product Overview](https://products.aspose.com/words/): Features and supported formats
- [API Reference Hub](https://reference.aspose.com/words/): Links to all API references

Share or continue the analysis

Share this audit

Discuss with AI

Added 9/2/2026