Case · Audit · Confidential

Premium Fruit, Invisible Online

A paid, pre-contract audit for a Japan-based food exporter, before any redesign or retainer began.

Japan

Severity breakdown of the 38 findings in the delivered audit

01EvidenceReidify, rendered from the delivered severity register

  • 5 critical
  • 4 high
  • 1 medium-high
  • 14 medium
  • 1 low-medium
  • 12 low
  • 1 opportunity

93

products

checked individually against a standard, not sampled

38

findings

graded by severity, not a flat checklist

7

forms flagged

an AI shopping agent could not read or fill in

A pre-contract audit sits under a real incentive to lean one way or the other. This one did neither.

The situation

A retainer, but only after proof

The client was preparing to expand from its home market into Taiwan, Hong Kong, Malaysia, and Singapore, and wanted to know whether the site could carry that expansion before committing to an ongoing SEO retainer. Rather than start the retainer on faith, they asked for a standalone technical review first: what is actually wrong, what is actually fine, and what has to happen before spending real budget on four new markets at once. That is a harder brief than it sounds, because a pre-contract audit sits under a real incentive to lean one way or the other. Pad it and the bigger contract looks more necessary. Soften it and the relationship stays comfortable a little longer. Neither is honest, and neither was the brief here.

Four questions

01

Search visibility

Crawlability, indexation, metadata, catalog integrity, and whether the domain itself was working for or against the business.

02

International readiness

What infrastructure existed for selling into four new markets, and what did not exist at all.

03

AEO

Whether an answer engine or a shopping agent could read the site, extract its facts, and have any reason to recommend it.

04

Visual design

Assessed against the storefront's own configuration data and against how competitors already selling into those markets present themselves.

The method

Built to resist both failure modes

Every one of the 93 products was checked against a standard, not sampled. The site's console and network activity were inspected in a real browser session, not just its source code, which is how a tag-management tool that was installed and never finished being wired up was caught at all. A public search for the site and the company name stood in for Search Console access, reported as a signal rather than a certainty. AEO was evaluated as its own category rather than folded into SEO, including a live Lighthouse "Agentic Browsing" test. And when the client independently ran a Google PageSpeed test mid-engagement and shared it, that data was credited as client-supplied and cross-checked against the audit's own findings, rather than quietly absorbed as if it were Reidify's own measurement.

Spread

Twenty-five categories, not eight

A template audit finds the same short list on every site. This one landed across twenty-five distinct categories, most of them carrying a single finding.

  • Metadata6
  • Structured data3
  • Site architecture2
  • Heading structure2
  • Content2
  • Indexability2
  • Performance2
  • Visual design2

17 further categories carried exactly one finding each, from security headers to competitor benchmarking. 25 distinct categories in total.

What the audit found

Precise, not padded

The site was still running on Shopify's own placeholder subdomain, eighteen months into selling produce internationally, the kind of detail that reads as a real signal to an international buyer paying up front for perishable fruit from an unfamiliar overseas supplier. Twenty of the 93 products, all sharing one naming pattern, carried an identical copy-pasted line declining to describe the product at all, not thin content in the abstract but the same sentence twenty times, traceable to one batch. A separate pair of listings turned out to be the same product at two live web addresses, each quietly working against the other's ranking. A public search for the site and the company name returned nothing, the finding that makes every other finding conditional, since a site that is not indexed has nothing else worth sequencing until that is confirmed. And the one test built for what comes after search, a live Lighthouse Agentic Browsing run, found seven forms an AI shopping agent could not read or fill in, on a platform whose own robots.txt had just started shipping agent-facing directives by default. The infrastructure for being useful to an agent had arrived. Nothing on the site was written to use it.

The sequence

An order to fix them in

The deliverable was not the list. It was knowing what has to be true before the next thing is worth paying for.

01

Immediate

Before any ongoing SEO work begins

  • Confirm the real indexation status in Search Console
  • Fix the duplicate product page
  • Install analytics that actually records
  • Publish a refund policy and terms of service
  • Repair the misconfigured tag manager
  • Write the missing homepage and product metadata
  • Start on mobile page speed, because it takes time
02

Next

Early implementation

  • Decide on a custom domain, and begin moving if so
  • Correct the mislabelled collections
  • Add the missing category descriptions
  • Fix the broken redirect
  • Restore missing page headings, add breadcrumbs
  • Fix mobile contrast and tap target sizing
  • Begin the visual design pass
03

Ongoing

Inside a monthly engagement

  • Configure the site properly for all four target markets
  • Write product and category content for real search intent
  • Build the FAQ and the AEO layer described above
  • Grow trust content, and reviews over time

What this case study is not

No results section, on purpose

Implementation has not happened, so there is no post-fix number to report, and no quote exists to run. Both would have to be invented to include, and this page does not do that. What is provable is the audit itself, so the audit itself is the whole case study: a site that had never been indexed, mapped precisely enough that the next twelve months of work has a sequence instead of a guess.

Where it stands

The audit closed out as a complete, paid, standalone engagement. What comes next, implementation and an ongoing retainer, is a separate scope this record does not claim or describe.

EngagementPre-contract SEO, technical & AEO audit
ClientConfidential, by request
BasedJapan, expanding into four Asian markets
ScopeDiagnosis only
StatusComplete and paid

Project by

Reidify

More audits