For software vendors and product makers · free · no account

Get listed, or put your prices on a weekly read

If you make software or a product in a category we cover, you can tell us which product is yours and which page states its price. You say it on your own domain, in a small file or in a badge, and our crawler reads the price off your page once a week. There is no form, no account and no fee, and nothing on this page can be bought.

9,0926,945 products and 2,147 software listings on record today, each written from public pages and none paid for
7 daysbetween reads of a pricing page a vendor has claimed; an ordinary listing is re-read within 30 or flagged stale
$0for a listing, a claim or a correction. No rank or score is for sale

The four steps

  1. Say which product is yours, on your own domain: a file or a badge. Either one is enough and they count the same.
  2. Make the prices readable. A product's page in a shop usually already is, through its schema.org data. A software pricing page usually needs its prices marked.
  3. Send us the domain, once: one email to [email protected] whose subject line is exactly Claim: example.com, with your domain in place of example.com. A program reads the subject line and nothing else, so the email may be empty and may come from any address: the proof is on the domain, not in the email. Nobody writes back; the answer is your status page.
  4. Read your status page. It appears at https://frontdeskreview.com/get-listed/status/your-domain/, usually within a few hours of the email, and every weekly check writes it again. It says what was read and, where something was not, why.

Way one: a file on your domain

Serve this at https://your-domain/.well-known/frontdeskreview.json. It holds no prices, only where they are.

{
  "version": 1,
  "products": [
    {
      "name": "Example CRM",
      "category": "crm-software",
      "pricing": [
        {
          "country": "US",
          "currency": "USD",
          "url": "https://example.com/pricing"
        },
        {
          "country": "DE",
          "currency": "EUR",
          "tax_included": true,
          "url": "https://example.com/de/preise"
        }
      ]
    },
    {
      "name": "Example Air 300",
      "category": "air-purifiers",
      "brand": "Example",
      "pricing": [
        {
          "country": "US",
          "currency": "USD",
          "url": "https://example.com/products/air-300"
        }
      ],
      "specs": {
        "cadr_smoke_cfm": 200,
        "coverage_sqft": 310,
        "hepa": true
      },
      "confirm": [
        "https://tester.example/reviews/example-air-300"
      ]
    }
  ]
}
MemberWhat it is
versionThe number 1.
productsOne to 20 products.
nameThe product's name: Latin letters, digits, spaces and . & + ' ( ) / -, up to 60 characters.
categoryOne of our category names: a software comparison such as crm-software, or a product category such as air-purifiers. The category decides whether the entry is read as software or as a product.
listingOptional. The address of the page we already hold for this product, copied from your browser: https://frontdeskreview.com/product/…/…/ for a product, https://frontdeskreview.com/software/…/…/ for software. Leave it out when we hold none.
pricingOne to 6 pages that state the price, one per market you sell in: the pricing page for software, the product's own page for a product.
brandOptional, products only. The brand, by the same rule as a name. Left out, it is the first word of the name.
specsOptional, products only. Up to 40 figures, each a number or true/false under one of the keys its category compares. See what a figure has to pass.
confirmOptional, products only. Up to 3 addresses of pages on the sites of testers our pages cite that name the product and state the same figures.
countryThe market's two-letter country code, for example US or DE.
currencyThe currency that page states its prices in, as a three-letter code.
tax_includedOptional. true when the page's prices include VAT or sales tax, false when they do not.
urlThe pricing page: https, on your own domain or a subdomain of it, with no port, user name or fragment.

Any other member is ignored. A file over 64 KB is not read, and one check reads at most 40 pricing pages on a domain.

Way two: a badge on your front page

A link to this site, placed in the HTML of https://your-domain/, that carries the same statement in its attributes. One badge states one product and one pricing page; for more products or more markets, use the file.

<a href="https://frontdeskreview.com/get-listed/status/example.com/"
   data-fdr-name="Example CRM"
   data-fdr-category="crm-software"
   data-fdr-pricing="https://example.com/pricing"
   data-fdr-currency="USD"
   data-fdr-country="US">Prices read weekly by The Front Desk Review</a>

For a product we already hold a page for, the badge can link that page, and then names it as the product's listing:

<a href="https://frontdeskreview.com/product/air-purifiers/example-air-300/"
   data-fdr-name="Example Air 300"
   data-fdr-category="air-purifiers"
   data-fdr-pricing="https://example.com/products/air-300">Example Air 300 on The Front Desk Review</a>
  • The link may point at any page of this site. Your status page is where a visitor of yours can see what we read and when; the product's own page here is the other natural choice.
  • data-fdr-currency and data-fdr-country may be left out; they are then USD and US.
  • The wording inside the link is yours, and so is how it looks.
  • Where a domain has both a file and a badge, the file is the claim.

A badge is a link to us, and we would rather say that than leave it unsaid. We do not require it, it earns nothing that the file does not, and you may mark it rel="nofollow": the check reads the attributes either way.

Make the prices readable

A product's page

Most shop pages need nothing. Where a product's page has no marked element, we read its schema.org Product in JSON-LD: the one the page names as your claim names the product, or the only one on the page. Shopify, WooCommerce and most shop platforms publish it already.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Air 300",
  "offers": {
    "@type": "Offer",
    "price": "149.99",
    "priceCurrency": "USD"
  }
}

Failing that, we read the page's OpenGraph price tags, when it states both the amount and the currency:

<meta property="product:price:amount" content="149.99">
<meta property="product:price:currency" content="USD">
  • The price is read in the currency your claim states for that page; an offer in another currency is passed over.
  • Where a product has several prices on its page (sizes, colours, bundles), the lowest is recorded and your status page says how many there are.
  • Where a page prices several products and names none of them as your claim names yours, no price is recorded: use the name the page uses, or mark the price.
  • To choose the figure yourself, mark it. A marked element on a product's page is read as a one-time price per unit:
<span data-fdr-price="price">$149.99</span>

A software pricing page

On each pricing page your claim names, mark the element whose text is the price. The value of data-fdr-price is a short id for the plan, in lower-case letters, digits and hyphens.

<span data-fdr-price="pro" data-fdr-name="Pro" data-fdr-per="user" data-fdr-period="month">$29</span>
<span data-fdr-price="team" data-fdr-name="Team" data-fdr-period="year">$990</span>
<span data-fdr-price="starter" data-fdr-name="Starter">Free</span>
AttributeValuesWhen left out
data-fdr-priceThe plan's id, up to 32 charactersThe element is not read
data-fdr-nameThe plan's name, by the same rule as a product's nameThe id is the name
data-fdr-peruser, flat or unitflat for software, unit for a product
data-fdr-periodmonth, year or oncemonth for software, once for a product

Where a software pricing page has no marked element, we read the Offer entries in its JSON-LD that carry a price and a priceCurrency equal to the currency your claim states for that page. An offer does not say how a plan is billed, so each is recorded as a flat monthly price. If that is wrong for your plans, mark the elements instead.

On either kind of page

  • The price must be in the HTML your server sends. We do not run a page's scripts, so a price a script writes in afterwards is not seen.
  • One figure per marked element. $29, $1,299.00, 29,00 €, GBP 15 and Free are read. "From $29 to $49" is two figures and is not; nor is a price beside a discount percentage. Mark the innermost element that holds the price alone.
  • Mark the price a visitor sees. The text of the element is what we record, so it has to be the figure your page shows.
  • Up to 12 plans are read per page. Where one id is marked twice, the first stands.

A product we do not hold: the makers' lane

A product whose claim names no page of ours is listed on its maker's statement: a page of its own under https://frontdeskreview.com/stated/ and a line on its category's page, both marked as the maker's word. It is listed when all of this holds:

  • A US dollar price was read from a page the claim gives for the United States (country US, currency USD).
  • It has been on sale six months. We count 183 days from the first day the product's page is known to have been public: the day the Internet Archive first captured it, or the day we first read it, whichever is earlier. Until then the status page gives the date.
  • Our catalogue does not hold a product of that name in the category already. If it does, name its page as listing.

What a figure has to pass

  • Its key is one the category compares. The keys of every category are published; a figure under any other key is left out.
  • The product's own page states it. A number in specs is taken only if the same number stands in the visible text of a page the claim gives for the product. It is then a statement made to your customers, not a number told to us.
  • It is not better than the best on record. A figure that would be the best its category has is shown as you state it and held back: it is not counted until a tester states it too.
  • A tester can confirm it. A page named in confirm is read when it is on the site of a tester whose reviews our pages already cite for at least 5 products. If it names the product and states the figure, the figure is marked confirmed. A shop's page confirms nothing: it repeats the maker's sheet.

What the lane is, and is not

  • The product is scored, and holds no place. Its figures are scored by the same formula as the category's products, and its page says where that score would stand beside them. It is not in the ranking, in no pick, award or "best", and not in our open data.
  • It moves nobody. The category's scores and places are computed without it, so no statement can raise or lower another product.
  • The first three places take confirmation. Where stated figures alone would stand among the first three, the page gives the score and no place.
  • It is the maker's page to lose. Withdraw the claim and the page goes with the next check.

A product we already hold: figures beside ours

Where a claim names our page for the product as its listing, each figure in specs is set beside the one our record holds, on your status page. Nothing in our record changes.

  • Within 10% it agrees. Past that it differs, and both figures are shown.
  • A dispute is a difference that flatters the product: more than 10% better than our figure, on a spec where the ranking counts higher or lower as better.
  • A tester settles it for you. If a page named in confirm states your figure, it is no dispute; it is marked as borne out against our record.
  • Left standing for 30 days, a dispute closes the domain. Its claims are not read for 365 days, everything it stated comes down, and its status page says why. Correct the figure, withdraw it or have it confirmed, and the dispute ends with the next check.
  • If our figure is the wrong one, email [email protected]: corrections are free and logged.

Currencies, countries and tax

Each pricing page in a claim is one market: a country, a currency, and optionally whether its prices include tax. A price is recorded in the currency its page states and is shown that way on your status page; we do not convert it. A bare $ is read as the currency the claim states for that page, since a dozen currencies share the sign. A marked price in another currency than the claim's is not recorded.

The comparison pages themselves list US dollar prices today.

The currencies we read: AED AUD BRL CAD CHF CZK DKK EUR GBP HKD ILS INR JPY KRW MXN NOK NZD PLN SEK SGD TRY USD ZAR

What a claim can say, and what it cannot

  • It can say a short list of things: a product's name, its category, where its prices are and which page of ours is about it; and for a product, its brand, its figures as numbers or yes/no, and testers' pages that state them. There is no description, no tagline, no logo and no field for free text.
  • Naming a listing changes nothing in it. Your status page then links our page for the product and says whether our record already cites your domain as a source. That is a fact about our record, not a judgement of yours.
  • A name that breaks the rule is refused, not cleaned. The same goes for every other value: what does not pass is left out, and your status page names it.
  • It cannot move a rank or a score. Those are computed from the data by published rules, and nobody can pay or ask to change them.
  • It cannot change or remove a listing of ours. Listing needs no vendor's consent, and a product a claim lists stands in the makers' lane, apart from the catalogue. If a figure of ours is wrong, email [email protected]: corrections are free and logged.
  • It speaks only for its own domain. Every address in a claim must be on the domain the claim was found on, so nobody can state a claim for a product whose site they do not control.

How we read your pages

  • Our crawler names itself as FrontDeskReviewBot on every request; its policy is public. It asks your robots.txt first. A page your robots.txt closes to it is not requested, and your status page says so.
  • The claim check requests your robots.txt, the claim file, your front page and the pricing pages your claim names, when your email arrives and then once a week, and nothing else.
  • A page may redirect up to three times, and only within your domain; a redirect that leaves it ends the read.
  • It reads up to 6 MB of a page and waits 15 seconds for it.
  • What it reads is treated as data. Nothing from your page is run, and only the checked values above are kept.
  • If your site answers it with a refusal, it stops there. A refused page is not read some other way.

What a status page says

StatusMeaning
Claim found, prices readWe found your claim on your domain and read at least one price from a page it names.
Claim found, no price readThe claim is there, and no pricing page gave us a price. The page lists why.
No claim foundThe domain answered, and neither the file nor a badge was on it.
Could not read the domainThe domain did not answer, or closed the claim file or the front page to our crawler, so we cannot say whether a claim is there. The page lists why.
Closed to claimsA dispute was left standing for 30 days. The domain's claims are not read until the date shown.

No status is our word for a vendor, a product or a price. It says that a claim stands on a domain and that a figure was read off its pages on the day shown.

Every message a status page can show

Each is our own sentence about what the check met. Nothing a vendor's page says is repeated in one.

CodeWhat it means
not-foundNothing answered at that address.
not-jsonWhat answered at the claim file's address is not valid JSON.
file-too-largeThe claim file is over 64 KB.
not-an-objectThis part of the claim is not an object.
version-must-be-1The claim must say "version": 1.
no-productsThe claim lists no product.
too-many-productsThe claim lists more products than a claim may hold; only the first ones, up to the limit, were read.
page-limit-reachedThe claim names more pricing pages than one check reads; this one was not read.
listing-not-a-page-of-ourslisting must be the address of a product's or a vendor's own page on this site.
listing-in-another-categoryThe page named as listing is in another category than the claim states for the product.
listing-not-foundWe hold no record at the address named as listing.
several-products-on-page-none-named-as-claimedThe page prices several products and names none of them as the claim names this one. Use the name the page uses, or mark the price.
brand-not-allowedbrand follows the same rule as a name.
specs-not-allowedspecs must be an object of figures.
spec-value-not-allowedA figure is a number or true/false under one of its category's keys; a product states at most 40.
confirm-not-allowedconfirm lists up to three https addresses on sites other than your own.
confirm-not-a-tester-we-citeA page named in confirm is not on the site of a tester our pages already cite, so it was not read.
unknown-specA figure's key is not one of the keys its category compares; it was left out.
spec-not-on-your-pageA figure in the claim does not stand on the product's own page; it was left out.
name-makes-no-addressThe product's name yields no page address.
already-in-the-catalogueOur catalogue already holds a product of this name in the category. Name its page as listing instead.
no-us-dollar-price-readNo US dollar price was read from a page the claim gives for the United States (country US, currency USD).
no-first-day-on-recordWe have no first day on record for the product's page yet.
on-sale-less-than-six-monthsThe product's page has been public for less than six months, as far as the web archive and our own reads show.
disputed-figure-left-standingA figure the domain stated flattered a product we hold, no tester we cite bore it out, and it stood for thirty days.
name-not-allowedA name may hold Latin letters, digits, spaces and . & + ' ( ) / - only, up to 60 characters.
unknown-categoryThe category is not one of ours. Use the last part of a comparison's address, for example crm-software or air-purifiers.
duplicate-nameTwo products in the claim have the same name.
no-pricing-pageThe product names no pricing page that passed the checks.
url-not-on-your-domainAn address must be an https page on your own domain, with no port, user name or fragment.
unknown-currencyThe currency is not a three-letter code we read.
country-must-be-two-lettersThe country is a two-letter code, for example US or DE.
tax-included-must-be-true-or-falsetax_included is true or false.
duplicate-pageThe same pricing page is listed twice for one product.
robots-txt-disallows-our-crawlerYour robots.txt closes this page to our crawler, or could not be read, so we did not request the page.
a-host-we-do-not-readThis is a host our crawler never reads.
your-site-refuses-our-crawlerYour site answered our crawler with a refusal (401, 403, 429 or 451).
redirects-off-your-domainThe page redirects to another domain; we did not follow it.
too-many-redirectsThe page redirected more than three times.
bad-redirectThe page redirected to an address we could not read.
not-a-public-addressThe address does not resolve to a public server.
could-not-connectWe could not connect, or the page did not answer within 15 seconds.
page-did-not-answerThe page answered with an error.
page-too-large-or-cut-offThe page is over 6 MB and no price stands in the part we read, or the connection was cut.
no-price-found-on-pageThe page has no element marked data-fdr-price and no schema.org Offer or product price tag in this page's currency.
plan-id-not-allowedA plan id (the value of data-fdr-price) is lower-case letters, digits and hyphens.
period-or-unit-not-alloweddata-fdr-period is month, year or once; data-fdr-per is user, flat or unit.
no-single-price-in-marked-elementThe marked element does not hold exactly one price. Mark the element whose text is the price itself.
currency-differs-from-claimThe marked price is in another currency than the claim states for this page.
not-a-domainThis is not a domain name.

Changing or withdrawing a claim

Edit the file or the badge and the next weekly check reads the new statement. Take both away and the next check records that no claim was found, and the prices it had read are no longer shown. A domain on which no claim is found for two weeks is taken off the list by itself, its status page goes with it, and we stop asking; the same email puts it back. A domain we could not read is not counted as having no claim: it stays on the list for eight weeks before it is taken off. To have a domain taken off sooner, email [email protected].

Category names

The 786 values category accepts. Each is the last part of a comparison's address.

Products: all 515
Software: all 271

Claims we have checked · Our crawler · How we make money · About