Skip to content

AI visibility

Why my pages contradict each other about pricing

Answer engines build one entity from every page they have and resolve disagreement by hedging, or by preferring a source that does not contradict itself. A model asked what you cost will say “pricing varies” rather than quote a number it cannot corroborate. Whichever value is current, state it identically everywhere — the fix is copy, not markup.

What 13x checks

This is rule aeo.entity-consistency in the public registry: The site states the same facts everywhere. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.

Surface
AI visibility
Score weight
6 of the readiness score
Scope
Reported as skipped when the page renders only with JavaScript
Applies
To every site

Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.

The fix

The same text the audit hands you when this check fails on your own site.

Your pages disagree with each other about what you are or what you cost.

An answer engine does not read one page. It assembles a single entity from every page it has, and when two of them conflict it resolves the conflict by hedging — "pricing varies", "the product appears to be" — or by preferring a competitor whose pages corroborate each other. Neither outcome quotes your number.

Fix the source, not each page. Put the facts in one module and import them everywhere they are rendered:

ts code
// lib/facts.ts — the single place any price or name is written
export const PRODUCT = {
  name: "example.com",
  startingPrice: { amount: 19, currency: "EUR", period: "month" },
} as const;

Then state the same value in your structured data, so the claim is machine-readable rather than inferred from prose:

json code
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "example.com",
  "offers": {
    "@type": "Offer",
    "price": "19.00",
    "priceCurrency": "EUR"
  }
}

Two cases worth checking before you change anything:

- A homepage showing the *annual* monthly-equivalent price while the pricing page shows the *monthly* price is not a bug, but it does read as a contradiction to a machine. Label the billing period next to every figure. - A brand name that differs between og:site_name and your JSON-LD name splits you into two entities. Pick one spelling and use it in both.

Does your site have this problem?

13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.

No signup. Results in 30 seconds.

More ai visibility checks