AI Readiness Assessment¶
This workflow shows how to use Content Chimera to assess a client’s website for AI readiness — how well the site’s content is structured for consumption by search engines, chatbots, and large language models. It is useful during business development, initial discovery, or ongoing optimization engagements.
Step 1: Run the AI Readiness Pipeline¶
The fastest way to get started is to run the automated AI Readiness pipeline, which crawls the site, extracts the five readiness dimensions, scores E-E-A-T with AI, and generates a report.
MCP
Ask your AI assistant to run the AI Readiness pipeline:
“Run an AI Readiness assessment for https://client-site.com”
You will be asked to confirm before the run starts (due to LLM cost). Once confirmed, the pipeline handles everything end-to-end. Ask “What’s the status?” to track progress.
Tool reference
Tool: run-long-pipeline with pipeline: "ai-readiness"
For details on what the pipeline measures, see AI Readiness Reports.
Step 2: Review the Automated Report¶
When the pipeline completes, a report appears in the Reports section of your extent. Start by reading through the generated analysis to get a sense of the overall picture:
Which dimensions score well and which need attention?
Are there entire sections of the site that lack structured data?
Do E-E-A-T scores vary significantly across content areas?
The report gives you a solid baseline. From here, you can dig deeper into specific areas.
Step 3: Dig Deeper into Specific Dimensions¶
The automated report provides a summary, but you will often want to explore specific dimensions in more detail. Use charts and queries to investigate.
Example explorations:
E-E-A-T by folder — Chart E-E-A-T scores broken down by top-level folder to see which sections of the site have the strongest or weakest content quality signals.
Pages missing Schema.org — Filter for pages with no JSON-LD markup to build a prioritized list for your developers.
Heading structure issues — Identify pages with broken heading hierarchy so content editors know where to focus.
FAQ opportunities — Find high-traffic pages that lack FAQ sections — these represent quick wins for AI visibility.
Chimera Chat
Ask questions to explore specific angles:
“Show me E-E-A-T Expertise scores by folder as a bar chart”
“Which pages have no Schema.org markup?”
“What’s the average Trustworthiness score for the /blog section?”
MCP
Ask your AI assistant to explore specific dimensions:
“Which pages have no JSON-LD markup?”
“Show me E-E-A-T Expertise scores by folder as a bar chart”
“What’s the distribution of semantic HTML usage across the site?”
Your AI assistant can answer data questions and create charts from the AI Readiness results.
Tool reference
Tools: chimera-query for data questions, chart for visualizations
Step 4: Present Findings to the Client¶
Once you have reviewed and refined the analysis, assemble your deliverable:
Edit the automated report — Remove sections that are not relevant, add your own commentary, and include any additional charts you created during exploration.
Use presentation mode — Content Chimera reports can be presented section by section, similar to a slide deck. Click the screen icon in the upper right of a report to enter presentation mode.
Print to PDF — If the client needs a static document, print the report from your browser. It will break at section boundaries for clean pagination.
Tip
Focus your presentation on the dimensions where the client has the most room to improve. A site with strong E-E-A-T scores but no structured data has a very different action plan than a site with good Schema.org but weak heading structure.
Tips for AI Readiness Engagements¶
Run the assessment early. Even in a business development context, an AI Readiness report demonstrates your analytical capability and gives the client concrete data about their site.
Benchmark against expectations. Not every site needs a perfect score on every dimension. Help the client understand which dimensions matter most for their industry and audience.
Make it actionable. For each gap, suggest a specific fix — “Add FAQ schema to your top 20 product pages” is more useful than “Improve structured data.”
Revisit over time. Re-run the pipeline after the client has made changes to show progress and justify ongoing investment.