← jwatte.com

Website & AI Search Readiness Audit

Mega Analyzer · By · Updated · v2026.10.20ar · Methodology · Changelog

Paste a URL. Get one report on how ready that page is for search engines and AI answer engines: SEO, schema, E-E-A-T, mobile parity, performance, accessibility, AI crawler access and agent-readiness signals, plus a ranked fix plan and a ready-to-paste fix prompt for Claude or ChatGPT. Free, no signup, no paywall. Built it because the paid tools charge a subscription for output you could do in one pass. See a sample report.

Analyze everything in one pass

Paste a URL. The Mega Analyzer fetches it twice (desktop and mobile UAs), the aux files (robots.txt, sitemap.xml, llms.txt), validates crawlability (Disallow conflicts, sitemap XML validity, URL-in-sitemap, dead-end detection, noindex + X-Robots-Tag overrides), then runs every check we can run against a single URL and scores six buckets: SEO, Schema, E-E-A-T, Voice, Mobile Parity, Performance + AI. Scan time varies by page.

How to use this
  1. Enter your page address, such as https://example.com, then select Run mega analysis.
  2. Open Full Summary to review what to fix, worst first.
  3. Open Mega AI Prompt, copy it and paste it into your AI assistant or give it to your web developer.

Allow a few minutes for a scan. Some pages take longer. Nothing is changed on your site.

The level and prompt framing choices are optional. Leave these as they are if unsure.

Optional checks
Paste rendered HTML instead (for SPA shells like Squarespace / Wix / Popmenu / Pixieset, or sites that bot-block the audit proxy)

When the static fetch can't see your real content, paste the post-hydration HTML here. The Mega Analyzer scores the pasted HTML against every dimension (SEO / schema / E-E-A-T / voice / mobile / performance + AI / crawlability). If you also paste a URL above, sibling resources (robots.txt, sitemap.xml, llms.txt, well-known files) are still fetched normally — those rarely depend on JavaScript. New to DevTools? Step-by-step walkthrough for Chrome / Firefox / Safari / iPhone / Android.

Tip: in paste mode, the URL field is optional. If provided, sibling resources are fetched from it. CrUX field data is not measured; otherwise those checks read as "Not applicable in paste mode".

Need a deep audit of your whole site, every page and every image? That is possible. Contact us first so we can confirm you own or manage the site and get your approval before a full scan runs.

Level: Standard report with mega AI prompt

Context and background

Read the story behind this tool: One URL, Every Audit in One Pass — The Mega Analyzer →

Paste a URL above

The Mega Analyzer gives you everything the other tools do in one report.

Frequently asked questions

Can you audit my whole site and every image?

Need a deep audit of your whole site, every page and every image? That is possible. Contact us first so we can confirm you own or manage the site and get your approval before a full scan runs.

What does Mega Analyzer check?

Ten buckets in one pass: SEO, Schema, E-E-A-T, Voice, Mobile parity, Performance + AI signals, Accessibility (WCAG 2.2 AA), Indexing hygiene, Retrieval (AEO) readiness, and an AI fix prompt assembled from every finding. See the methodology page for the per-bucket check list.

Does Mega Analyzer execute JavaScript?

No. The tool fetches the raw HTML response twice — once with a desktop user agent and once with a mobile user agent. JavaScript-rendered content that requires a headless browser is not scored. This matches how most AI crawlers actually fetch your site.

Do I need to sign up or pay?

No signup and no paywall. Tool pages count runs without cookies; Google Analytics and Microsoft Clarity set cookies only if you accept. The tool runs in your browser against a server-side fetch proxy with origin allowlisting and per-IP rate limits.

How is the score calculated?

Each check returns pass / warn / fail / info. Warns count as 0.5 of a pass. Bucket score is the weighted average across that bucket's checks. The overall grade is the unweighted average of bucket scores, mapped to A–F. The full rubric and per-check weights are published at /methodology/.

How does this compare to isitagentready.com?

Cloudflare's isitagentready.com groups its checks into five categories. Mega Analyzer looks at the same kinds of agent signals and also covers SEO, schema, accessibility and publishing. It does not stop at "the file exists". It reads each agent file it finds (API catalog, MCP server card, Agent Skills index, A2A agent card, llms.txt and others), checks that the required fields are there and valid, and then asks the addresses those files list whether they actually answer. If your site runs an MCP server, it also does a read-only handshake: it asks the server to introduce itself and list its tools, and it never calls a tool. For an A2A agent, it checks whether the endpoint answers without sending an agent message. These extra lookups are read-only and capped, 12 per normal scan and more with Run all checks, so a scan stays quick. Anything we could not reach or did not get to is marked "not checked", never pass or fail. The Agent Readiness score beside these rows keeps our existing isitagentready comparison model. Its inputs are shown beside the result; the other site's checks can change over time.

How often is Mega Analyzer updated?

Optional checks, nearby scan progress and mobile report layout were updated on October 20, 2026. Completed all-checks runs offer a full fix prompt. The check set is versioned. See /methodology/changelog/ for the dated probe history. The 2026-10-20 agent verification update reads published agent files, checks their links, and keeps the read-only MCP and A2A handshake. Normal scans allow 12 extra lookups; Run all checks allows more. The comparison score remains separate. The 2026-10-20 update removes optional adoption and editorial scoring, consolidates legacy checks, and ranks remaining scored defects using their actual weights. Voice and Mobile comparisons stay visible and unscored. Incomplete evidence stays unknown. Certificate lifetime uses TLS evidence; optional transport tests say Not tested until enabled. Article update dates appear once, with warnings for missing or inconsistent dates and no scoring on other pages. Source reviews cover crawler roles, redacted content and credential cues, conditional resources, forms, phone links and declared feeds/keys. Localized article dates use machine dates. IndexNow files allow a leading BOM and trailing whitespace. Access cards now cover the audited host only. Missing DNS records and certificate errors do not count as blocks; proxy platform errors do not count as recovered pages.