www.mecca.com/en-au
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
www.mecca.com/en-au
Preparing the stored Is Agentic score
www.mecca.com/en-au
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Ready with gaps
Weighted across 14 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Keep the correct HTTP 404 status. The remaining requirement is a Markdown error body when agents request Accept: text/markdown. Include at least 20 characters explaining the error and a link to your docs, sitemap, or llms.txt. Verify with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/some-path-that-does-not-exist. Check both the final 404 status and the Markdown body with Content-Type: text/markdown. Checking the status alone does not verify the missing requirement.
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
Put price data in each product page's JSON-LD or microdata. Use a schema.org/Product whose offers is a schema.org/Offer with price, priceCurrency, and availability, or AggregateOffer for a variant price range, so agents can read prices without scraping a marketing page.
Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases and how an agent should call you. Be specific about the jobs you are right for - generic marketing copy does not read as guidance.
Checks are grouped by relevance for Commerce sites.
1783 chars with H1, but heading hierarchy skips H1 to H4
How to pass
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Site accessible to 6 AI agent user-agents
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 6 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
Homepage https://mecca.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "accept-encoding, origin")
How to pass
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
The nonexistent path https://mecca.com/__ora-404-probe-lp6j8r0p correctly returns HTTP 404. Partial credit: no Markdown error body was detected.
How to pass
Keep the correct HTTP 404 status. The remaining requirement is a Markdown error body when agents request Accept: text/markdown. Include at least 20 characters explaining the error and a link to your docs, sitemap, or llms.txt. Verify with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/some-path-that-does-not-exist. Check both the final 404 status and the Markdown body with Content-Type: text/markdown. Checking the status alone does not verify the missing requirement.
mecca.com ranks #1 for "MECCA Brands fragrance shop"
Valid sitemap found at https://www.mecca.com/sitemap.xml with multiple sitemaps entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (2 blocks)
No pricing page or pricing data found
How to pass
Put price data in each product page's JSON-LD or microdata. Use a schema.org/Product whose offers is a schema.org/Offer with price, priceCurrency, and availability, or AggregateOffer for a variant price range, so agents can read prices without scraping a marketing page.
No agent instruction file with when-to-use guidance found
How to pass
Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases and how an agent should call you. Be specific about the jobs you are right for - generic marketing copy does not read as guidance.
2/4 metadata signals present - missing: og:image, og:type
How to pass
Add all four signals to your homepage: <link rel="canonical">, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
Organization schema found but missing: address
How to pass
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
All trust anchor pages verified: About, Contact, Privacy
All 6 measured pages fit an agent context budget (largest ~1K tokens)
Agent mode view found at ?mode=agent (3 signals: api, agent, sdk)
How to pass
Add a ?mode=agent query parameter to your homepage that returns a structured, machine-readable view with API endpoints, authentication info, and key capabilities instead of marketing HTML.
Strong entity linking via sameAs: linkedin.com, wikipedia.org
NLWeb /ask endpoint exists but requires authentication (HTTP 403, via POST)
564 native controls, 57 non-native div-soup affordances (91% native).
494/564 interactive elements have a computable accessible name (88%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does www.mecca.com do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does www.mecca.com do and who is it for? Explain it back to me.
13 steps6 reasoning steps3 searches
The agent successfully assembled a comprehensive explanation of MECCA by combining direct site fetches with web search results. The homepage (step 1) and customer care page (step 4) provided basic positioning and logistics, while the Beauty Loop page (step 9) revealed the loyalty program structure. However, the agent had to rely heavily on external sources (ShopBack comparisons, Wikipedia, Business of Fashion) to answer the core questions about pricing, differentiation, and competitive positioning—information that MECCA's own site does not clearly surface in a single, machine-readable format.