ReviewProof ⚖

How do you explain a seasonal spike in your reviews?

By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Run the free review audit See pricing · See a sample provenance report

Short answer

Explain it with contemporaneous evidence, filed before anyone asks: the season's trading records (bookings, orders, occupancy, footfall) beside that month's import and evidence pack; review rows that are predominantly transaction-linked; a rating spread that includes the season's complaints; and wording as varied as the season's customers. A spike so documented reads as weather. A spike that worries an auditor has the opposite file — a quiet trading period, UNLINKED rows, uniform praise, and no seasonal evidence — because it was never seasonal; it was scheduled by a vendor.

What is a seasonal review spike?

A seasonal review spike is a concentration of reviews aligned to a business's genuine trading peak: a resort's August, a retailer's December, a tax adviser's April, a gym's January. Its legitimacy rests on proportionality (reviews rose because transactions rose, roughly in step) and traceability (the rows link back to the season's transactions). Seasonality is therefore an evidential claim about your calendar, which your records either support or do not — not a mood, and not a defence available to a spike in a month your till was quiet.

File the season while it is happening

The distinguishing habit costs nothing and cannot be backdated: during the peak, keep the month's pack together with the season's own artefacts — the booking summary, the event programme, the roster showing extra staff, the local coverage clipping. Future readers (a platform analyst, a buyer's diligence team, your own manager next year) will reconstruct the spike from whatever you filed, and a spike reconstructed from trading records closes in minutes. Proportionality is the check they will run first: if transactions doubled and reviews doubled, the file agrees with itself. If transactions rose 20% and reviews rose 400%, seasonality is not the explanation and the honest audit says so internally, in the same month's notes, while the cause can still be found.

Keep the negative reviews. That instruction surprises people mid-crisis, but suppression is itself a violation under the FTC rule, and a profile scrubbed clean during an attack reads as manipulation to anyone who later examines it. ReviewProof has no silent-delete path: moderation decisions are kept, published or flagged internally, each one is logged in the chain of custody, and the evidence export counts the negatives you kept. The strongest response to a suspicious review is a boring, complete record — the row, the dates, the signals, the decision, all preserved while you dispute through the platform's own process.

Reading a spike like an auditor, once a year

Take the year's biggest spike and interrogate it as an exercise, before anyone else does. What share of the spike rows are transaction-linked? (For a genuine peak served through your own channels, the linked share should resemble the year's norm, not collapse.) What is the rating spread? (A real peak strains service, so the spike should contain the season's share of complaints — a spike of pure praise during your most chaotic month is the least seasonal object in the file.) Does the spike's wording vary at human scale? Then file the answers as the month's audit note. A business that has audited its own spike has nothing to fear from the exercise being repeated by a sceptic with less goodwill.

ReviewProof's import is forgiving about format and strict about meaning. Column names are matched flexibly — body, review or text for the review itself; rating or stars; reviewer, author or name; a verified flag and a transaction reference when you hold them. Rows are capped per import by plan (500 on Free, 5,000 on Pro, 50,000 on Agency), which is generous for a single location's history. What the importer will not do is upgrade a review's status: a row that arrives without a transaction link is analysed fully and still labelled UNLINKED, because the label is the product.

Mistakes that undo the work

Backfilling a seasonal narrative in the dispute month — assembling 'evidence' after the question arrives — inverts the timing that gives the file its force. Explaining every spike as seasonal by reflex teaches the team to stop looking; exactly one of them, some year, will be a vendor. And smoothing solicitation across the season to flatten the chart is engineering the record; import the season as it happened.

Triage starts from your own data, not from the public profile. Import the reviews, look at which rows carry which signals, and separate three questions that are often mashed together: is this review about a real transaction, was it solicited in a way the FTC rule prohibits, and what record do we hold if anyone asks? ReviewProof answers the first two from the imported rows — transaction link present or UNLINKED, gating or incentive language present or absent — and answers the third with the provenance chain. What it will not do is declare a review fake: signals are heuristics for human review, and acting as if they were verdicts creates a new problem while solving none.

Worked example: a Christmas spike and a quiet-month anomaly

A fictional worked example, written to show the numbers and the decisions in practice.

A garden centre's year contained two spikes. December: 138 reviews, 41% of its annual total, 79% transaction-linked from its own till system, ratings spread from one star (queue complaints, kept and answered with the extra-till policy) to five, filed with the December trading summary showing transactions up 3.1×. The audit note called it seasonal and closed it in a paragraph. The other spike was the finding: 26 reviews across three days in a flat February, 4 linked, uniform praise, two duplicate texts — traced to a listings company 'seasonal boost' the centre had not known it was still paying for. Cancelled, flagged, disputed with the pack. The contrast is the lesson: seasonality is a claim only evidence can make, and the same business held one spike that could and one that could not.

Your five-action checklist

  1. Import peak months separately so spikes stay visible and datable
  2. File trading evidence (bookings, occupancy, event records) with the peak pack
  3. Check proportionality: transactions versus reviews for the peak
  4. Read the spike's linked share and rating spread as an auditor would
  5. Note the seasonal conclusion — or the anomaly — in that month's audit record

Frequently asked questions

Will a seasonal burst hurt our risk score?

A detected burst adds 15 points for that import's score. The score is a triage number, not a penalty — the filed evidence and linked rows are the answer, and the next imports return to baseline.

How much of a spike should be transaction-linked?

Roughly your normal linked share. A collapse in linked share during a spike is the anomaly — genuine seasonal customers link at the usual rate; bought rows link at none.

What if our season is someone else's campaign season too?

Then both effects can coexist: document the seasonal layer with trading evidence, and let cluster analysis separate any vendor rows riding the peak.

Can we cite seasonality to a platform?

Yes — as a documented claim: the pack plus trading records for the period. Platforms test proportionality and links, so send the numbers, not the adjectives.

Keep reading

Related guides from the ReviewProof library:

Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.