How we rank fixes

Reachable pages first

First, can a crawler reach the right country’s page? We check access rules, redirects, country links and canonical URLs. A page that cannot be read needs attention before new copy.

Accurate facts next

Then we check product titles, prices, availability and page facts. We compare server HTML with a browser render when one is available. Missing access or a failed fetch is a gap in the audit, not proof that the store is broken.

Rank the remaining work

1. Estimate the customer impact and the markets affected.
2. Check the evidence and its limits.
3. Compare effort and risk. Prefer a small, reversible fix.

Search Console queries in positions 4 to 20 can point to useful opportunities by country. These are average positions, not promises of a page-one result.

Approve. Verify. Undo.

Each proposal shows the current state, the proposed change and how to check it. You approve before anything changes. App-supported fixes use the app’s write and undo flow. Theme-owned changes need a reviewed patch and rollback plan.

Freshness and buyer-intent gaps are findings for review. A page older than 90 days may still be accurate. A missing comparison page is not a reason to publish a weak one.

What the check can tell you

The free check samples public pages and reports what it read. The audit adds connected Search Console data and deeper market review. Neither measures every page or proves that an AI system will cite you.

Training-bot rules and answer-search rules serve different purposes. We report both. A merchant must approve any change to crawler access.