.recipes Domain
Share Your Culinary Creations with the World
Register your .recipes domain from just £75.99/yr. Free DNS management, email forwarding, and 10GB mailbox included with every domain.
What is a .recipes domain?
The .recipes domain is ideal for food bloggers, home cooks, and culinary enthusiasts who want a dedicated space for their dishes. It tells a visitor there is cooking to be found here.
Who should register .recipes?
Food bloggers, recipe developers, cooking enthusiasts, and culinary content creators.
Why choose .recipes?
- Clearly signals cooking content
- Ideal for food blogging
- Encourages bookmarking and sharing
- Builds a niche audience naturally
Who runs .recipes, and since when
Registry data from the .recipes delegation record held by IANA, which maintains the internet's root zone. Eligibility comes from the registry's own policy, and the prices are ours.
- Extension type
- Generic (gTLD)
- Registry operator
- Binky Moon, LLC
- The organisation that runs the extension
- In the root zone since
- 2013
- Delegated 12 December 2013
- Who can register
- Open to anyone worldwide, with no publishing or food credential needed
- Checked against the registry's own policy
- Our price
- £75.99 a year
- Ex VAT. Renews at the same price
Why .recipes does nothing for recipe rich results
The most common reason people want this extension is the one it cannot deliver. Recipe rich results, the ones with the photograph, the star rating and the cooking time, come from structured data on the page. Google's documentation is explicit about what it needs: a Recipe type carrying at least an image of the finished dish and a name, and for the recipe carousel an ItemList plus a summary page that lists every recipe in the collection. The domain is not among the inputs, and never has been.
Then there is the price. This is the dearest extension in our food group by a clear margin, on a category of site that is usually funded by display advertising or by nothing at all. Ten years of it against a hobby project is a sum worth doing on paper before you fall in love with the name.
The word is also plural, which narrows what reads well in front of it. A subject, a place, a cuisine or a family name finishes the phrase properly. A company name that is already plural or possessive fights it. Say the whole address out loud before you commit, because the plural is the part people get wrong when they retype it.
Delegated in December 2013 and run by Binky Moon, part of Identity Digital, a .recipes domain has no eligibility conditions at all. Where we would use it: as a memorable address that redirects to a recipe section on a site you already own, or for a project that is a collection rather than a business.
Is .recipes the right choice for you?
We would rather sell you the right extension once than the wrong one twice.
.recipes works well if
- You run a food brand or a cookery school and want a memorable address that redirects to the recipe section of your main site.
- The project is a collection rather than a company: a regional cuisine archive, a family record, a single-ingredient site.
- The subject in front of the dot completes the phrase, so the address reads as a title rather than as a business name.
- You want a readable name that is still free, which longer and more specific extensions tend to have when short ones do not.
Look elsewhere if
- The price. This is the dearest extension in the food group and a recipe site rarely earns enough to notice a bill that size, every year.
- It has no effect on recipe rich results. Those need Recipe structured data on the page, which you would have to build whatever the domain said.
- Building the recipes on a second domain splits your site, so the links and shares the recipes attract do nothing at all for the main brand.
Already have a site? Publish the recipes at yoursite.co.uk/recipes/ so the traffic and the links feed one domain. See .co.uk pricing.
.recipes vs .com: which should you register?
Neither of these does anything for how a recipe appears in search, which is the useful thing to establish first. The difference is entirely in how the address reads and what it costs.
.com reads as an organisation. It is the default guess, it never needs explaining, and it is far cheaper to hold for twenty years. The catch is that a readable food .com has been gone since the early 2000s, so what is available is padded with an extra word or a hyphen. .recipes reads as a collection. The plural does the describing for you, so the name in front can be a subject rather than a brand.
If the site is a business with a recipe section, take the .com or the .co.uk and put the recipes in a folder. If it is a collection in its own right and the name is the whole point, the extension has an argument, provided the annual figure does not bother you.
| .recipes | .com | |
|---|---|---|
| Annual cost | The dearest in this food group | Low |
| Reads as | A collection | An organisation |
| Readable names left | Many | Few without hyphens or filler |
| Effect on recipe rich results | None | None |
| Location signal | None | None |
.recipes domain questions, answered
What people ask us before registering a .recipes domain.
Can't find what you're looking for?
Ask us directlyNo. Google's documented requirements for recipe rich results are structured data on the page: a Recipe type with at least an image of the completed dish and a name. To appear in a recipe carousel you also need ItemList markup and a summary page listing every recipe in the collection. Nothing in those requirements refers to the domain. A recipe on a .co.uk with correct markup is eligible; the same recipe on a .recipes without it is not.
The registry sets the wholesale price and this extension sits at the top end of the food group. There is nothing technical behind it: the DNS, the DNSSEC support and the record types are identical to any other extension, so you are paying for the word rather than for anything the domain does. The figure recurs annually, and short or obvious names can be classed as premium under Identity Digital's reserved names policy and priced above the standard rate again.
It narrows what reads well and it invites a typing error. A subject, a cuisine, a region or a family name in front of the dot finishes the phrase naturally. A brand that is already plural or possessive collides with it and sounds awkward spoken. The typing risk is that people drop the s, so if the singular is also available it is worth registering and redirecting. Read the full address aloud to someone and watch them type it before you buy.
It depends on whether you are naming a person or a collection. A blogger building a personal brand, with an eye on a book, a column or sponsorship, wants an address that carries their name and travels beyond recipes, which points at .com or .co.uk. A site that is purely a recipe archive, where the subject is the identity, is what this extension was made for. If you already have a site, publish the recipes in a folder on it and use the .recipes as a redirect.
Included with Your .recipes Domain
DNS Management
Full DNS zone editor to manage A, CNAME, MX, TXT, and all record types.
Email Forwarding
Set up professional email addresses and forward to any inbox.
Auto-Renewal
Never lose your domain with automatic renewal protection.
Free 10GB Mailbox
One 10GB mailbox (POP3/IMAP) included with every domain, on any TLD.
Other Food & Drink Domains Extensions
Register your .recipes domain today
Secure your .recipes domain from just £75.99/yr. Free DNS management, email forwarding, and 10GB mailbox included.
