target.com

HTTP responses can carry a Link header: the same canonical and alternate-language information your HTML declares, but delivered in the response envelope itself. Agents that only send a HEAD request, or that decide what to do while the page is still streaming, read the header without parsing any HTML. Yours is missing (or carries none of the relations agents use: canonical, alternate, describedby).

An agent triaging fifty URLs doesn’t want to download and parse fifty pages to learn which are duplicates of which. The Link header answers at the cheapest possible layer. Sites that provide it get correctly de-duplicated and correctly language-routed even by the most minimal fetchers.

1. Emit a Link header alongside each page, mirroring what your HTML head already declares. Example: Link: <https://yoursite.com/page>; rel="canonical".
2. Most stacks set this in one place: Next.js headers() config, an nginx add_header line, or a CDN response-header rule.
3. If you serve translations, add rel="alternate" entries with hreflang, matching your HTML.

• Run: curl -sI https://yoursite.com | grep -i "^link:" and confirm the relations appear.
• Hit Re-scan above: "Link response headers" flips to PASS.

• The header must AGREE with the HTML. A Link header pointing one place while the in-page canonical points another gives machines two contradictory answers, which is worse than one missing answer.
• Don’t inject the same site-wide canonical on every page via a blanket CDN rule; each page names its own clean URL, exactly as in the HTML tag.

Of everything your server sends for this page, very little is actual readable text. The rest is code, styling, and markup wrapper. Agents fetched a lot of bytes and found few words.

Agents work with retrieval budgets. A page that is 2% text either gets skimmed (and mis-summarised) or skipped. More signal per byte means more of your actual message survives into the agent’s summary.

1. Confirm your real copy is server-rendered. See the JavaScript check; these two usually fail together.
2. Cut boilerplate wrappers: deeply nested divs, inline SVG logos repeated per section, base64 images inlined into HTML.
3. Move large inline styles and scripts into external files.
4. Check how much of the document is inline script: your report now says. If most of it is, that is your framework serializing state for hydration, often a second copy of text already in the HTML. Send only the props a component cannot recompute, and render statically where a page does not need to hydrate.

• Re-scan: "Text-to-markup ratio" improves, and "Page weight" often improves alongside.

• Don’t pad the page with keyword text to inflate the ratio. The ratio is a proxy for substance, and stuffing is the opposite of substance.

Your page’s actual content (headlines, product info, pricing) only appears after JavaScript runs in a browser. Most AI agents read the raw HTML that arrives FIRST, and for your site, that first delivery is nearly empty.

An agent fetching your page gets the skeleton: navigation links, a footer, loading placeholders. It then summarises your business from a skeleton. Sites in this state get described as "this page contains little information" while the full pitch renders only for humans.

1. Next.js: Render primary content on the server: use Server Components (App Router) or getServerSideProps/SSG (Pages Router). Avoid fetching above-the-fold content in a client useEffect, since agents don’t run it.
2. Server-render the content that matters: hero copy, value proposition, pricing, product details.
3. Next.js: use Server Components or static generation for marketing pages. Don’t fetch above-the-fold content in a client useEffect.
4. Quick self-test: view the page source (Ctrl+U shows the raw HTML, not the inspector) and search for your headline. If it isn’t there, agents don’t see it.

• Your headline and pricing appear in the raw page source.
• Re-scan: "Content without JavaScript" flips, and "Text-to-markup ratio" usually improves with it.
• The "What the agent receives" section below shows exactly what a no-JS agent gets from your page.

• Don’t serve a special pre-rendered version only to detected bots (cloaking). Agents compare notes with real user agents, and a divergence gets you classified as deceptive.
• Don’t paste an HTML copy of the content into a hidden div as a workaround. Duplicated content that drifts from the rendered version fails coherence in the ugliest way.

Your page HAS structured data, but it is malformed: broken JSON syntax, or types and fields that don’t exist in the schema.org vocabulary. Machines can see the block but can’t parse it.

Invalid JSON-LD is worse than it looks. The agent spends its attention budget on the block, fails to parse it, and falls back to guessing from prose anyway. You pay the cost of structured data without getting the benefit.

1. Paste the failing page into validator.schema.org. It names the exact line and field that breaks.
2. The most common breaks: a trailing comma (invalid JSON), a typo’d type name, or a price written as "$79" instead of "79" with a separate priceCurrency.
3. Fix in place, redeploy, revalidate.

• validator.schema.org reports zero errors for the page.
• Re-scan: "Structured data validates" flips to PASS.

• Don’t delete the block to make the error disappear. That trades "invalid" for "absent" and fails the presence check instead; fix it.
• Don’t hand-edit generated JSON-LD in the page. Fix the template or plugin that generates it, or the error returns on the next publish.

Your structured data exists but only covers the basics (say, Organization) while the page is really a product page, an article, or an FAQ. The machine-readable caption is missing the part that describes what this page actually is.

An agent looking for "running shoes under $100" matches against Product markup with offers. A product page carrying only Organization markup is invisible to that query shape: the agent knows who you are but not what this page sells.

1. Identify the page’s real type: Product (with offers), Article, FAQPage, HowTo, LocalBusiness, Event.
2. Add that type’s JSON-LD alongside the Organization block, filled from the page’s actual content.
3. For Product: include name, price, priceCurrency, and availability. Those are the fields agents actually query.

• Re-scan: "Schema type coverage" improves. Keep "Structured data validates" green while you add.
• The coherence checks below compare your declared price and name to the visible page; they should stay (or flip to) PASS.

• Only declare types the page genuinely is. A blog post marked up as a Product to appear in shopping queries is the exact incoherence assistants are getting better at detecting.
• Keep declared values synced with the page. If a sale changes the visible price, the JSON-LD price must change in the same deploy.