⚠Warnings 4
⚠ warningllms-txt/missingllms.txtllms.txt present
No llms.txt found
GET https://www.mozilla.org/llms.txt returned HTTP 404.
FixCreate /llms.txt at the site root: an H1 title, a short blockquote summary, and ## sections linking to your key content.
https://www.mozilla.org/llms.txt → HTTP 404
⚠ warningschema/no-jsonldStructured DataJSON-LD structured data present
No JSON-LD structured data on the page
AI engines use schema.org markup to identify entities, dates, authors and page types. Without it they fall back to unreliable inference.
FixAdd JSON-LD blocks describing the page (Article, Organization, BreadcrumbList, FAQPage as appropriate).
⚠ warningcontent/missing-datesCitabilityVisible publication/modified date
No machine-readable publication or modified date found
Checked <time datetime>, article:* meta tags and JSON-LD datePublished/dateModified — none present.
FixExpose a date via <time datetime="…">, article:published_time meta or JSON-LD datePublished/dateModified.
⚠ warningtechnical/sitemap-missingTechnical FoundationXML sitemap discoverable
No sitemap discoverable
No Sitemap directive in robots.txt and /sitemap.xml does not resolve.
FixPublish an XML sitemap at /sitemap.xml and declare it in robots.txt ("Sitemap: https://…/sitemap.xml").
https://www.mozilla.org/sitemap.xml → HTTP 404
ℹHints 9
ℹ hintllms-txt/llms-full-missingllms.txtllms-full.txt companion file
No llms-full.txt found
GET https://www.mozilla.org/llms-full.txt returned HTTP 404. The optional full-content companion is absent.
FixConsider publishing /llms-full.txt with your key documentation inlined as markdown.
https://www.mozilla.org/llms-full.txt → HTTP 404
ℹ hintllms-txt/ai-manifestllms.txtEmerging AI manifest files (agents.json, ai.txt)
No emerging AI manifest files found
Checked /agents.json, /ai.txt, /.well-known/ai-plugin.json — all absent. These conventions are early and entirely optional.
FixPrioritize /llms.txt; add agents.json or ai.txt only if they fit your AI distribution strategy.
ℹ hintschema/no-faq-schemaStructured DataQuestion headings backed by FAQPage schema
2 question headings present but no FAQPage schema — easy citation win
Q&A content is exactly what answer engines quote. FAQPage markup makes those pairs machine-readable.
FixWrap the Q&A section in FAQPage (or QAPage) JSON-LD with Question/acceptedAnswer pairs.
ℹ hintschema/no-organizationStructured DataOrganization schema present
No Organization schema found
Without entity grounding, engines cannot connect this site to a known organization — weaker trust signals for citation.
FixAdd an Organization JSON-LD block (name, url, logo, sameAs links) at least on the homepage.
ℹ hintschema/no-breadcrumbStructured DataBreadcrumbList schema present
No BreadcrumbList schema found
Breadcrumbs expose site structure to machines; without them a page floats without context.
FixAdd BreadcrumbList JSON-LD matching the visible breadcrumb trail.
ℹ hintcontent/no-data-pointsCitabilityConcrete data points
Few concrete data points found (0 numeric stats)
Percentages, growth figures and quantities give AI engines precise, attributable claims to quote.
FixAdd verifiable numbers — percentages, counts, benchmarks — near the claims they support.
ℹ hintcontent/images-no-altCitabilityImages carry alt text
18 of 24 images have no alt text
Alt text is the primary way AI systems understand what an image shows; missing alt makes visual content uncitable.
FixWrite descriptive alt text for meaningful images (purely decorative ones can keep alt="").
ℹ hintcontent/answer-firstCitabilityPage leads with a direct answer
Lead paragraph after the H1 is thin (~16 words)
A teaser or caption-length opener is hard to quote verbatim; engines prefer a self-contained answer they can lift whole.
FixExpand the opening paragraph into a direct, self-contained answer (roughly 40–80 words) before diving into details.
From trustworthy tech to policies that defend your digital rights, we put you first — always.
ℹ hinttechnical/redirectTechnical FoundationNo unexpected redirect
The URL redirected to a different final URL
Requested https://mozilla.org/, ended at https://www.mozilla.org/en-US/.
FixMake sure redirects are intentional, single-hop and point at the canonical destination.
https://mozilla.org/ → https://www.mozilla.org/en-US/