Factual contradictions between pages — different numbers for the same metric, pricing on the home page that doesn't match the pricing page, the product name spelled two different ways — damage credibility more than any individual error. The visitor who navigated from the home page to the pricing page and found different numbers now doesn't know which one is true, and the doubt that creates extends beyond the specific contradiction to the entire site. AI-built sites are particularly prone to cross-page inconsistency because each page was generated in a separate session: the home page might say "100+ audits" and the pricing page, generated three weeks later, says "50+ audits available." Neither is deliberately wrong — the information simply drifted.
Low because cross-page factual contradictions undermine credibility at the comparison stage — visitors who found the inconsistency lose trust in the accuracy of all the site's claims.
Search the codebase for your key claims and product name across all page files to find instances that could contradict each other:
# Find all instances of your product name, feature counts, and pricing
grep -r '100+\|50+\|2,400\|2400' src/ app/ --include='*.tsx' --include='*.mdx'
grep -r 'FlowMetrics\|Flow Metrics' src/ app/ --include='*.tsx' # substitute your product name
grep -r '\$9\|\$29\|\$79' src/ app/ --include='*.tsx' # substitute your pricing
For any metric, statistic, or pricing figure that appears in multiple places, extract it to a shared constants file and reference it everywhere:
// lib/constants.ts — single source of truth for marketing facts
export const MARKETING_FACTS = {
auditCount: '116+',
customerCount: '2,400+',
pricingMonthly: '$9/mo',
pricingYearly: '$79/yr',
productName: 'AuditBuffet', // canonical spelling and capitalization
} as const
Import MARKETING_FACTS in every page component that references these values. Future updates require changing one file.
ID: marketing-content-quality.readability-quality.cross-page-consistency
Severity: low
What to look for: Count all relevant instances and enumerate each. Compare key facts stated on different pages. Specifically check: (1) product name — is it spelled and capitalized the same way on every page? (2) statistics and counts — if the home page says "100+ audits" and the pricing page says "50+ audits", that is a contradiction; (3) pricing — does any price mentioned on the home page match what the pricing page shows? (4) product description — does the one-line description of what the product does match between pages? AI-built sites frequently have inconsistencies between pages because different prompting sessions generated different copy.
Pass criteria: No factual contradictions found between pages. Key statistics, product name, pricing, and product descriptions are consistent across all marketing pages examined.
Fail criteria: At least one factual contradiction found between pages — different numbers for the same metric, different pricing, contradictory descriptions of what the product does, or inconsistent product name spelling/capitalization.
Skip (N/A) when: Only one public-facing page exists (no cross-page comparison possible). Signal: single-route project.
Detail on fail: Quote the contradiction with page locations. Example: "Home page says '100+ audits' but pricing page says '50+ audits available.'" or "Home page spells product as 'FlowMetrics' but footer says 'Flow Metrics' (two words)." Keep under 200 chars.
Remediation: Contradictions between pages signal carelessness or stale copy. For AI-built projects, this is especially common because each page may have been generated in a separate session.
Search your codebase for key numbers and product name to find all instances. Update them to match. Consider extracting shared constants (product name, feature counts, pricing) into a single file that all pages reference, preventing future drift.
Review the configuration in src/ or app/ directory for implementation patterns.