www.target.com
Finalizing the report
Preparing the stored Is Agentic score
www.target.com
Preparing the stored Is Agentic score
www.target.com
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.
Needs work
Weighted across 17 applicable checks
Blocked
Weighted across 7 applicable checks
Blocked
Weighted across 3 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. Inner pages need their main text in the raw HTML too, not only after JavaScript runs.
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.
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.
Checks are grouped by relevance for Commerce sites.
Homepage: 2680 chars with H1, but 1.9% content ratio is below the 5% target. No inner pages checked: the 5 sampled pages were skipped (forms, login pages, bot challenges, error pages, non-HTML pages and pages over 1 MB are skipped).
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. Inner pages need their main text in the raw HTML too, not only after JavaScript runs.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh or JavaScript-redirect stubs across 14 checked pages
All 5 sampled pages are publicly readable (0 with substantive content)
Homepage https://target.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "accept-encoding")
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://target.com/__ora-404-probe-9r3il9je 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.
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://www.target.com/sitemap_keywords-index.xml.gz with multiple sitemaps entries
JSON-LD found (1 block) but no identity type - use SoftwareApplication, Product, Organization, Person, or Article so agents can tell what this site is
How to pass
Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.
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.
3/4 metadata signals present - missing: og:image
How to pass
Add all four signals to your homepage: <link rel="canonical"> pointing to the page on your own site, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
No Organization type found in JSON-LD
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.
About, Privacy pages verified - missing: Contact
How to pass
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
All 6 measured pages fit an agent context budget (largest ~1K tokens)
In a search for your API docs, your docs came up at #8 (https://plus.target.com/docs/spec/seller)
target.com ranks #2 for "Target" (searched your brand name alone: no main product term from your homepage qualified)
Wikipedia "Target Corporation" and Wikidata Q1046951 both verified - domain confirmed on both sources
Found the llms.txt at https://developer.target.com/llms.txt.
The llms.txt is well-formatted: 64 lines with markdown links, 6,158 characters in total.
Documentation site found at https://developer.target.com
Schema types found (BreadcrumbList), but none matches a link, name, question or rating shown on the homepage. Lists on the homepage with no schema type: a list of 3 links starting with /c/kids-clothing-deals/-/N-ywh7o, a list of 6 links starting with /pl/8675-4452059982180142, a list of 4 links starting with /b/dairy-boy-by-hanes/-/N-q643le4qtbi
How to pass
Mark up what your homepage shows: an ItemList for a list of pages, posts or products, with each item pointing to its page, or FAQPage for questions the page answers.
All 5 probed llms.txt links resolve to real content
Code fences balanced across 1 markdown document
Developer portal found at https://developer.target.com
Documentation site found at https://developer.target.com but API content unclear. Best-of-protocols score: 3/7.
How to pass
Expose a public REST or GraphQL API. AI agents need programmatic access - not just a web UI - to integrate with your product.
OAuth mentioned on homepage but no standard endpoints found
How to pass
Implement OAuth 2.0 for API authentication. Publish your authorization server metadata at /.well-known/oauth-authorization-server.
Onboarding signals described but not verified live: self-serve key generation, sandbox/test environment
How to pass
Offer a free tier or trial, self-serve API key generation, and a sandbox environment. Agents can't fill out 'contact sales' forms.
Runtime-verified: 1 tool captured in a real browser session
Server HTML is a well-structured document (main=true, landmarks=3/4, h1=1, maxHeadingSkip=1).
112 native controls, 0 non-native div-soup affordances (100% native).
109/110 interactive elements have a computable accessible name (99%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does www.target.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.target.com do and who is it for? Explain it back to me.
5 steps1 reasoning step1 search
The agent assembled a reasonably complete overview of Target's business, pricing, and audience from its homepage and corporate About page, but had to supplement membership pricing via web search because the Circle pages lacked specific fee data. The site exposed basic positioning but left gaps in competitive context and membership terms that required external lookup.