allegiantair.com
2026-08-21 14:25 UTC スキャン · キャッシュ · 0時間後に更新 · rubric 2026.11.0
未確認の公開スキャン
不合格
AgentSpeed は、自動化エージェントが allegiantair.com をどれだけ容易に発見・理解・操作できるかを検査します。スコアは機械可読性の5カテゴリを重み付けし、弧の目盛りはその背後にある37件の個別チェックです。
測定不完全: ルーブリック重みの50%のみが結果を出しました（5カテゴリ中2）。そのため評価は表示されません。スコアは測定できた範囲のみを反映します。
チェックの技術的な詳細は英語で表示されます。スキャナーの出力をそのまま示しているためです。
優先すべき修正
「emerging」タグの付いたチェックは、まだウェブの大半が採用していない2026年のエージェントプロトコル標準です。早期採用は欠点ではなく強みです。
failReachability+37点実行可能性Terminal HTTP 403.
具体的な手順を見る
これは何を意味するか
Before reading anything, an agent has to reach your page: one request, a clean answer. Yours didn’t answer cleanly. The finding above says exactly what happened: an error status, a connection failure, or a chain of redirects before any content arrived.
なぜ重要か
Agents give up much faster than browsers. A human waits through three redirects and a retry; an agent on a time budget records "unreachable" and answers from other sources. Every other measurement on this page happens only after this one succeeds, so this failure hides everything else your site does right.
やること
- Read the finding above: it names the status code and counts the redirects we followed.
- If it is a redirect chain, collapse it to one hop. The classic chain is http → https → www → final page; configure your host to jump straight from any variant to the final address in a single redirect.
- If it is a 4xx or 5xx status, your server is refusing or failing the page. Fix the route or the error before anything else on this page.
- If the fetch failed outright, check DNS and the TLS certificate; an expired or mismatched certificate turns every agent away at the door.
このレポートを保存
今すぐ受信箱へ。さらにallegiantair.comのスコアが変化したときに通知します。無料、いつでも配信停止できます。
監視はお任せください。Monitorが毎週再スキャンし、変化があればメールでお知らせします（$29/mo）。 監視を始める →
修正する
上記のギャップに対応する、生成済みですぐ使えるファイルです。コピーするか、ダウンロードしてリポジトリに配置してください。
このスキャンは1ページを採点しました。サイトは1ページではありません。
このスキャンで最も弱かったのは実行可能性（0/100）— このページが人に提供している操作を、エージェントは見つけることも完了することも困難です。
採点したのはトップページだけです。価格・ドキュメント・購入ページは別のページにあり、アシスタントが引用するのはまさにそれらのページです。ここで15/100ということは、最も磨いたページですらエージェントが見逃しているということ。Deep Scan（$29）はトップページに加えて、当社が検出した最大10ページを全37チェックで監査し、失敗したチェックとその具体的な修正を、可視性への影響が大きい順にまとめたPDFをメールで送ります。1回限り・数分で納品・サブスクリプションなし。
エージェントが受け取るもの
スコアを掲載
このバッジをサイトに埋め込めます。ライブスキャンにリンクし、再スキャンのたびに更新されます。
<a href="https://agentspeed.com/scan/allegiantair.com"><img src="https://agentspeed.com/badge/allegiantair.com" alt="AgentSpeed agent-readiness score" height="56"></a>このスコアを追跡
このレポートをメールで受け取り、allegiantair.comの対応状況が実際に変化したとき（チェックの悪化や総合スコアの低下）に通知を受け取れます。
メールが送られないケースが2つあります: 当社が新しいルーブリックを公開したことによるスコア変化（測定器が変わっただけで、サイトの変化ではありません）と、実行のたびに揺れる時間依存チェックだけで説明できる変動です。
自分のスケジュールで、メールの代わりにSlackやWebhookで受け取りたい場合は スコアドリフト監視 をどうぞ。すべての有料プランに含まれています。
このスコアはAIエージェントがallegiantair.comを読み取れるかを示します。 AIトラフィック分析 は、実際に来たかどうか、そしてどのページが追い返したかを示します。
完全な内訳
2 pass1 warn8 fail26 skip
発見可能性
fail
robots.txt present
No reachable robots.txt at the site root. Publish one so agents can discover your crawl policy and sitemap.
0/100
pass
robots.txt allows AI agents
All 9 answer-time access agents allowed.
100/100
fail
Content-Signal directivesemerging
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
0/100
pass
llms.txt present
Found /llms.txt but missing H1 header and markdown links. Not scored.
100/100
warn
Sitemap present
sitemap.xml reachable but not referenced from robots.txt, so agents may miss it.
70/100
skip
Link response headers
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Canonical URL
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
MCP server cardemerging
Not measured: the origin answered HTTP 403 for this resource, which says we were refused or could not be served, not that the resource is missing.
—
fail
OAuth authorization metadataemerging
No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.
0/100
fail
OAuth resource metadataemerging
No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.
0/100
fail
API catalog / OpenAPIemerging
No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.
0/100
fail
Web Bot Authemerging
No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.
0/100
可読性
skip
Markdown negotiationemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Text-to-markup ratio
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Content without JavaScript
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Heading hierarchy
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Cookie wall blocks content
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Declared language
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Page title
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Meta description
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
構造化データ
skip
JSON-LD present
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Structured data validates
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Schema type coverage
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
整合性：各チャネルは一致していますか？
skip
JSON-LD price matches the visible priceemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
JSON-LD name appears on the pageemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Declared language matches the contentemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
実行可能性
skip
Paywall / login wall
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Agent Skills manifestemerging
Not measured: the origin answered HTTP 403 for this resource, which says we were refused or could not be served, not that the resource is missing.
—
skip
WebMCP actionsemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
fail
Commerce protocol manifestemerging
No agentic-commerce discovery manifest (x402 at /.well-known/x402.json, UCP at /.well-known/ucp, or ACP at /.well-known/acp.json). Agents that buy pre-flight these before attempting a transaction; publishing the one for your commerce protocol is how they learn you accept agent-initiated purchases.
0/100
skip
Primary action reachable
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
fail
Reachability
Terminal HTTP 403.
0/100
skip
Primary action is clickableemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Filters reachable by URLemerging
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
パフォーマンス
skip
Time to first byte
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Full render time
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
skip
Page weight
Not measured: the origin returned HTTP 403 for this URL, so the document received is an error or challenge response rather than the page. Scoring it would describe that response, not your site.
—
スキャンの先へ
自社のAIエージェントを運用していますか？ AgentSpeedは本番環境の監視も行います。すべての実行、レイテンシ、コスト、失敗を記録し、問題発生時にアラートを送ります。月10,000イベントまで無料、クレジットカード不要。
このようなレポートをすべてのクライアントに:ホワイトレーベルPDFと週次モニタリングを最大15ドメインまで、$149/mo。 代理店向けAgentSpeed →
方法論と制限事項
このスコアは、公開されたルーブリック 2026.11.0 に基づく、自動化エージェント向けの読みやすさの測定値です。AgentSpeed はセキュリティ、事業の正当性、プライバシー、金銭的信頼性を評価しません。