Comparison editorial standard

Every page under /compare follows the same five rules. They are checked at the schema level, which means a page that breaks one of them will not build, let alone publish.

1. We name what the competitor does better. At least one of the three scenario answers on each page recommends the competitor over PresentSphere. The other two may recommend PresentSphere; one must not. If we cannot find a single situation where the competitor is the right answer, we should not be publishing a comparison.
2. We compare with sentences, not checkmarks. The differences strip on each page is prose, not a feature checklist. Two products described by one generous sentence each, side by side, tells the reader more than a row of green ticks ever has.
3. We weight both columns equally. The competitor column is never visually de-emphasised: same type ramp, same width, same color, same length. The trust this page earns depends on the reader feeling the competitor was described fairly.
4. We disclose at the bottom. Every comparison page carries the trademark owner of the competitor we discuss, plus the explicit line that PresentSphere is not affiliated with, endorsed by, or sponsored by that competitor.
5. We stamp the page with a fact-check date. The date you see under the title of each comparison is the last time we re-verified the claims about the competitor on that page. If the date is more than 90 days old, treat specific feature or pricing claims as indicative rather than current.

We re-check every comparison page once per quarter. The process is short:

• Open the competitor’s public pages and confirm the pricing, plan structure, and feature claims we made.
• Read each scenario answer with a stranger’s eye and confirm we still believe it.
• Update the page’s lastFactCheckedAt date if the page is unchanged, or both that date and updatedAt if any claim moved.

If a competitor materially changes their product between quarterly cycles (a new privacy model, a new pricing tier, a feature that invalidates one of our claims), we re-check the affected page within two weeks of noticing. We would rather take a page down than leave a stale claim up.

Each comparison page carries a per-page footer that names the trademark owner of the competitor it discusses. The canonical list lives here so the same string appears on every page and on this page, in one place that is easy to audit.

• Elfster is a trademark of Elfster, Inc.
• Giftster is a trademark of Giftster, Inc.
• Amazon, Amazon Wish List, and related marks are trademarks of Amazon.com, Inc. or its affiliates.

PresentSphere is not affiliated with, endorsed by, or sponsored by any of the companies listed above. If we have misidentified a trademark owner here, please reach out and we will correct the page within one business day.

The following claims are not allowed on a comparison page:

• That PresentSphere is “better” than the competitor as a generic statement. Better is situational; the page must describe the situation.
• That the competitor has a flaw we have not personally verified. Reader complaints, public bug threads, and third-party reviews are not enough; we must reproduce the claim ourselves before publishing it.
• Pricing claims that are older than the last fact-check date stamped on the page.
• Any implication that the competitor endorses, partners with, or sponsors PresentSphere.
• Side-by-side imagery that distorts the competitor’s product (cropped screenshots, dated UI, dark-mode screenshots paired with our light-mode hero, and similar visual tilts).

If a claim on a comparison page is wrong, we want to know about it before our readers do. The fastest way to flag a correction is the contact link in our FAQ. We will respond within two business days and, if the correction is valid, update the page with both a new updatedAt date and a brief change note.

If you represent a competitor named on one of these pages and you would prefer we not write about your product, get in touch through the same channel. We will discuss; we may not always agree, but we will read carefully.