Index

Common MX Mistakes - Anti-Patterns to Avoid

· 4 min read

Even well-intentioned implementations can fail if you don’t know the pitfalls.

Here are the most common mistakes we see when organizations adopt Machine Experience.

1. Adding Structure Without Validation

Mistake: Implementing Schema.org markup but never validating it.

Why it fails: Syntax errors, wrong types, or missing required properties make structured data useless. Agents ignore invalid markup.

Fix: Validate every page with:

Test with actual agents - Ask ChatGPT questions about your page.

2. Hidden Structured Data

Mistake: Marking up content that isn’t visible to users.

Example:

<!-- BAD: Price not shown on page -->
<div itemscope itemtype="https://schema.org/Product">
  <meta itemprop="price" content="99.99">
</div>

Why it fails: Search engines and agents penalize hidden content. It’s considered deceptive.

Fix: Only markup content that’s visible to users. If humans can’t see it, don’t mark it up.

3. Using Generic Schema Types

Mistake: Using Thing or CreativeWork when specific types exist.

Example:

{
  "@type": "Thing",  // Too generic
  "name": "Widget"
}

Why it fails: Agents can’t take specific actions on generic types. Thing tells them nothing useful.

Fix: Use the most specific type available:

4. Stale Data

Mistake: Structured data that’s out of sync with page content.

Examples:

Why it fails: Agents confidently share wrong information. Users lose trust.

Fix: Update structured data whenever content changes. Automate from database where possible.

5. Accessibility Theater

Mistake: Adding ARIA attributes without understanding them.

Example:

<!-- BAD: Contradictory attributes -->
<button disabled aria-disabled="false">Submit</button>

Why it fails: Conflicting signals confuse assistive tech and agents.

Fix: Use ARIA correctly or don’t use it. Native HTML is often better:

6. Over-Reliance on Visual Cues

Mistake: Assuming color, position, or icons communicate meaning.

Example:

<!-- BAD: Only visual indication -->
<input type="text" class="required-field" style="border: red">

Why it fails: Agents don’t see visual styling. They need explicit markup.

Fix: Declare in markup:

<input type="text" required aria-required="true">

7. Broken Heading Hierarchy

Mistake: Skipping heading levels or using headings for styling.

Example:

<h1>Page Title</h1>
<h4>Section</h4>  <!-- Skipped h2 and h3 -->
<h2>Subsection</h2>  <!-- Out of order -->

Why it fails: Agents use heading hierarchy to understand content structure. Broken hierarchy breaks understanding.

Fix: Maintain proper order: h1 → h2 → h3 → h4 → h5 → h6. Never skip levels.

8. Ambiguous Link Text

Mistake: Links that don’t describe their destination.

Example:

<a href="/products">Click here</a>
<a href="/about">Learn more</a>
<a href="/contact">Read more</a>

Why it fails: Screen reader users and agents can’t distinguish between links without context.

Fix: Make links self-descriptive:

<a href="/products">Browse our product catalog</a>
<a href="/about">Learn about our company</a>
<a href="/contact">Contact our support team</a>

9. Form Inputs Without Labels

Mistake: Placeholder text instead of labels, or no labels at all.

Example:

<!-- BAD: No label -->
<input type="email" placeholder="Enter email">

Why it fails: Agents filling forms don’t know which field is which.

Fix: Always use explicit labels:

<label for="email">Email Address</label>
<input type="email" id="email" placeholder="name@example.com">

10. Testing Only With Humans

Mistake: Assuming if it works for humans, it works for agents.

Why it fails: Humans compensate for poor design. Agents don’t.

Fix: Test with actual agents:

The Recovery Checklist

If you’ve made these mistakes, here’s how to fix them:

✓ Validate all Schema.org markup (Google Rich Results Test) ✓ Run accessibility audit (axe DevTools, WAVE) ✓ Check heading hierarchy on every page ✓ Verify form labels are explicit and connected ✓ Test with agents - ask questions, try tasks ✓ Review alt text on all images ✓ Check for visual-only cues (color, position, icons) ✓ Validate required fields are marked in markup ✓ Review link text for clarity ✓ Keep structured data current

Start with your highest-traffic pages and most important user journeys.

→ See Success Patterns → Understand the Benefits → Get Professional Audit

Back to Top