temu.com

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.

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.

Headings (H1, H2, H3…) are the page’s outline. Yours skip levels, repeat H1s, or use styled text instead of real heading tags, so the outline machines extract is scrambled.

Agents use the heading tree to navigate long pages and to decide which section answers a question. A broken tree means quotes get attributed to the wrong section, or sections are missed entirely.

1. Exactly one H1 per page: the page’s actual title.
2. Nest without skipping: H2 for sections, H3 for subsections. Never jump H1 to H4 for visual size.
3. If a heading looks right but is a styled <div>, make it a real <h2> and adjust CSS. Machines only see tags.

• Re-scan: "Heading hierarchy" flips to PASS.

• Don’t pick heading levels for their font size; style with CSS and keep levels semantic.

The thing you want people to do on this page (add to cart, book, subscribe) has to be a real element in the page code: a link with an address, or a button. On your page the words are there, but they are painted on. They live inside an image, or on a plain box styled to look like a button.

An agent working your page does not look at pixels. It reads the list of things it can click. A call to action drawn into an image is not on that list, so the agent scrolls past the exact thing you wanted it to press. In a controlled test, a button baked into an image was clicked zero times out of ten by every model tried, while the same button as a real element was clicked seven times out of ten.

1. Find the main call to action on this page and look at how it is built. In your browser, right-click it and choose Inspect.
2. If you see <img> or a <div> with a background image, replace it with a real <a href="..."> or <button> and put the words in as text.
3. If the design needs an image, keep the image inside the link or button and give the link an aria-label with the words: <a href="/cart" aria-label="Add to cart">.
4. An <a> tag with no href is not a link. Give it a real destination, or make it a <button>.

• View the page source (Ctrl+U) and search for the words of your call to action. They should appear as text, not only as an image filename.
• Try the page with a keyboard: press Tab. If focus never lands on your main action, an agent cannot reach it either.
• Re-scan: "Primary action is clickable" flips to PASS.

• Do not rely on alt text to make an image clickable. Alt text describes an image, it does not create a link, and in testing it did nothing for interaction.
• Do not add invented attributes like data-llm-description or data-ai-action. Those were tested and had no effect at all; use real HTML elements instead.
• Do not add a hidden duplicate link only agents can see. That is cloaking, it fails our coherence checks, and it is the pattern assistants are getting better at spotting.