robots.txt
# See https://www.robotstxt.org/robotstxt.html for documentation on how to use the robots.txt file
# Hand-maintained: bin/build-site removes and recopies its own generated paths
# (blog, help, _astro, pagefind, sitemap*.xml) and never touches this file.
# The sitemap itself IS generated, by @astrojs/sitemap — the reason /blog and
# /help are subpaths rather than a subdomain was SEO, and an unannounced
# sitemap gives that up for one line.
Sitemap: https://emailfig.com/sitemap-index.xml
User-agent: *
# The signed-in app. None of it is a page a search result should lead to, and
# none of it answers to an anonymous crawler anyway: most redirect to /auth,
# /api/ wants a key, /good_job, /impersonate and /staff want a staff session. So these rules
# buy crawl budget rather than protect anything.
Disallow: /api/
Disallow: /auth
Disallow: /automations
Disallow: /campaigns
Disallow: /contacts
Disallow: /custom_fields
Disallow: /dashboard
Disallow: /forms
Disallow: /good_job
Disallow: /grow
Disallow: /impersonate
Disallow: /imports
Disallow: /lists
Disallow: /segments
Disallow: /sending_domains
Disallow: /settings
Disallow: /signup
Disallow: /staff
Disallow: /suppressions
Disallow: /tags
Disallow: /template_images
Disallow: /templates
Disallow: /up
# The token-gated recipient paths (/u/, /c/, /p/, /w/, /invites/) stay
# crawlable on purpose. Their controllers send X-Robots-Tag: noindex, and a
# crawler has to fetch a page to read that header. Disallowing them would hide
# it and leave an externally linked token URL eligible for URL-only indexing,
# which is the opposite of the intent. test/architecture/static_site_test.rb
# pins it.
# Hosted signup pages (/f/:id) stay crawlable: each carries its own SEO title,
# description and OG image (docs/features/FORMS.md), so it is meant to rank.
# Only its two non-page endpoints are blocked.
Disallow: /f/*/challenge
Disallow: /f/*/config
llms.txt
# EmailFig
> Email marketing that gets out of your way: campaigns, automations, signup forms and segments on every plan.
## Pricing
- [Pricing](https://emailfig.com/pricing): Every tier's price by subscriber count, free plan through 500,000 contacts, managed sending and bring-your-own-SES.
## Comparisons
- [Mailchimp alternative](https://emailfig.com/compare/mailchimp-alternative): The Mailchimp alternative that costs a fifth as much
- [Brevo alternative](https://emailfig.com/compare/brevo-alternative): The affordable Brevo alternative
- [MailerLite alternative](https://emailfig.com/compare/mailerlite-alternative): The MailerLite alternative that stayed affordable
- [EmailOctopus alternative](https://emailfig.com/compare/emailoctopus-alternative): EmailFig vs EmailOctopus: the budget tools, compared honestly
- [Moosend alternative](https://emailfig.com/compare/moosend-alternative): The Moosend alternative with a real free plan
- [Kit alternative](https://emailfig.com/compare/kit-alternative): The affordable Kit (formerly ConvertKit) alternative
- [beehiiv alternative](https://emailfig.com/compare/beehiiv-alternative): EmailFig vs beehiiv: email tool or media platform?
- [BigMailer alternative](https://emailfig.com/compare/bigmailer-alternative): The BigMailer alternative with no surprise price floor
- [MailBluster alternative](https://emailfig.com/compare/mailbluster-alternative): The MailBluster alternative for people who send often
## Integrations
- [Integrations](https://emailfig.com/integrations): EmailFig's integrations, and how to build your own on the API.
- [Zapier](https://emailfig.com/integrations/zapier): start Zaps from what happens in your list, and add or tag contacts from any app Zapier connects.
- [Make](https://emailfig.com/integrations/make): run scenarios on contact, form and campaign events, and keep contacts up to date from any scenario.
- [n8n](https://emailfig.com/integrations/n8n): an EmailFig node and a trigger node, for n8n Cloud or your own server.
- [Pabbly Connect](https://emailfig.com/integrations/pabbly-connect): start workflows when contacts sign up or unsubscribe, and add or unsubscribe them from any workflow.
- [Pipedream](https://emailfig.com/integrations/pipedream): a source for every EmailFig event, and actions for contacts, lists and tags.
- [WordPress](https://emailfig.com/integrations/wordpress): your forms and popups on your site, and a subscribe checkbox on comments and registration.
- [Contact Form 7](https://emailfig.com/integrations/contact-form-7): a subscribe checkbox on any form, with tags and extra answers.
- [WPForms](https://emailfig.com/integrations/wpforms): add a checkbox field, and everyone who ticks it joins your list.
- [Gravity Forms](https://emailfig.com/integrations/gravity-forms): add a feed to any form, and everyone who fills it in joins your list.
- [Lnk.Bio](https://emailfig.com/integrations/lnk-bio): newsletter leads from your Lnk.Bio page land in your EmailFig lists as they arrive.
- [Advanced Form Integration](https://emailfig.com/integrations/advanced-form-integration): send submissions from almost any WordPress form plugin to your EmailFig lists.
- [Integrately](https://emailfig.com/integrations/integrately): ready-made automations between EmailFig and the apps you use, built by Integrately.
- [Move from Mailchimp](https://emailfig.com/integrations/mailchimp): bring your audience over once, then Zapier sends new Mailchimp subscribers to EmailFig.
- [Move from MailerLite](https://emailfig.com/integrations/mailerlite): import your subscribers, then Zapier sends new MailerLite signups across while you move your forms.
- [Move from Brevo](https://emailfig.com/integrations/brevo): import your contacts, then Zapier sends new Brevo signups to EmailFig.
## Documentation
- [Help center](https://emailfig.com/help): guides on getting started, contacts and segments, campaigns, templates, forms, automations, reports, deliverability, account and team, billing, the API and integrations, and bring-your-own-SES.
- [API reference](https://emailfig.com/docs): the EmailFig REST API - contacts, lists, tags, custom fields, campaign results.
- [Blog](https://emailfig.com/blog): posts on email marketing practice and product changes.
## Optional
- [Terms of Service](https://emailfig.com/terms)
- [Privacy Policy](https://emailfig.com/privacy)
