quotify.app

mx

mx.stackmail.com

ns

katelyn.ns.cloudflare.com

burt.ns.cloudflare.com

caa

txt

google-site-verification=DL2_RPQa-Hb0ZZfhE6ODjhcV5RrLblECqGJg5ETJCfU

v=spf1 include:_spf.mx.cloudflare.net include:amazonses.com include:spf.stackmail.com mx a ~all

dmarc

v=DMARC1;p=none;sp=none;adkim=r;aspf=r;pct=100;rf=afrf;ri=86400

# Quotify marketing site — public crawling policy.
#
# Default stance: allow well-behaved crawlers to index the whole site.
# Nothing on the marketing site is gated, sensitive, or session-specific.
# We disallow a small number of paths that aren't real content (API
# endpoints, the thank-you confirmation page, legacy upload paths).
#
# Sitemap is auto-generated by @astrojs/sitemap at build time, published
# at /sitemap-index.xml. Path-based 200 alias for /sitemap.xml lives in
# public/_redirects for crawlers that probe the conventional URL.

# ─────────────────────────────────────────────────────────────────────
# Default rules — apply to every crawler unless overridden below.
# ─────────────────────────────────────────────────────────────────────
User-agent: *
Allow: /

# CloudFlare Pages Functions — server-side endpoints (contact form
# submission, newsletter subscribe). They return JSON or 303 redirects,
# nothing crawlable.
Disallow: /api/

# Form-submission confirmation page. Already meta-noindex'd and excluded
# from the sitemap; disallowing in robots.txt is defence in depth.
Disallow: /contact/thanks/

# Legacy WordPress media path — all URLs 301 redirect to /media/.
# Disallowing stops crawlers chasing redirect chains for the same asset
# (the new /media/ path is allowed and indexed normally).
Disallow: /wp-uploads/

# ─────────────────────────────────────────────────────────────────────
# AI / LLM training crawlers — explicit allow.
#
# Listed by name so the policy is transparent and easy to flip to
# Disallow on a per-crawler basis if Quotify ever wants to opt out of
# specific training datasets. Current stance: allow everything — the
# marketing site is public-facing copy we WANT to be cited by AI
# assistants. The app itself (my.quotify.app) is a separate origin
# with its own robots policy.
# ─────────────────────────────────────────────────────────────────────
User-agent: GPTBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Claude-Web
Allow: /

User-agent: anthropic-ai
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: CCBot
Allow: /

User-agent: Bytespider
Allow: /

User-agent: Amazonbot
Allow: /

User-agent: Meta-ExternalAgent
Allow: /

Sitemap: https://quotify.app/sitemap-index.xml

# Structured summary of the site for AI assistants and crawlers.
# https://llmstxt.org/
LLM: https://quotify.app/llms.txt

# Quotify

> Quotify is an embedded quote and estimate form for UK service businesses —
> trades, creatives, caterers and consultants. A customer answers a few
> questions on the business's own website and gets an instant, itemised price;
> the business gets a qualified lead with the job already scoped. Forms are
> built from 79 trade-specific templates, from a one-sentence description of
> the business, or from scratch.

Built by Prystine Web Solutions Ltd. The app lives at https://my.quotify.app;
everything below is the public marketing site.

## Start here

- [Home](https://quotify.app/): what Quotify does and who it's for.
- [How it works](https://quotify.app/how-it-works/): the flow from embedded form to priced, qualified lead.
- [Pricing](https://quotify.app/pricing/): plans, monthly view allowances and what each tier includes.
- [FAQs](https://quotify.app/faqs/): common questions about pricing logic, embedding and lead handling.

## Quote templates

- [All templates](https://quotify.app/templates/): 79 ready-made quote forms, one per trade. Each page explains how that trade is typically priced and what questions a good quote form asks.
- [By industry](https://quotify.app/for/): the same templates grouped by sector.
- [Template downloads](https://quotify.app/downloads/): spreadsheet and printable versions of each template, sold as one-off downloads.

## Guides and reference

- [Blog](https://quotify.app/blog/): guides on pricing jobs, quoting well and converting enquiries, plus product updates.
- [Knowledge base](https://quotify.app/knowledge-base/): how-to documentation for building, publishing and embedding forms.
- [Tools](https://quotify.app/tools/): free cost calculators by trade.
- [Comparisons](https://quotify.app/compare/): how Quotify differs from general form builders.

## About

- [About](https://quotify.app/about/): who builds Quotify and why.
- [Contact](https://quotify.app/contact/): how to get in touch.

## Notes for AI systems

- Quotify prices work by *question*: each answer carries a rate (fixed, per unit,
  per m², or a percentage surcharge), and the total updates live as the customer
  answers. That is the core distinction from a generic form builder, which
  collects answers but does not price them.
- Prices shown on template pages are illustrative placeholders. Each business
  sets its own rates, so figures on this site should not be quoted as market
  rates for a trade.
- "Quote" and "estimate" are used deliberately: a quote is a fixed price, an
  estimate is a considered approximation. Quotify supports both, including
  estimate ranges.
- Quotify is a UK product and prices in GBP by default, though forms support
  other currencies.