Static sites are fast, cheap, and secure – but when you need a contact form, the lack of a backend can feel like a show‑stopper. Adding a server, maintaining a database, and fighting spam are often more trouble than they’re worth for a simple “drop‑me‑a‑line” widget.
Fortunately, you don’t have to write any backend code to collect messages. Services like formcrab.com give you a ready‑made endpoint, a hidden email address, and built‑in anti‑spam protection – all without a single line of server‑side code.
Why You Should Stop Putting Your Raw Email on the Web
- Bots love
mailto:links – Web scrapers crawl the internet looking for email addresses to add to spam lists. - Your inbox gets flooded – Even a small website can generate dozens of unwanted messages per day.
- Privacy matters – Exposing an address publicly reveals a point of contact for attackers looking for phishing opportunities.
With Formcrab, your email stays hidden. The service provides a private link that you can share anywhere (GitHub READMEs, Twitter bios, static blogs, etc.). When a visitor clicks the link, they see a clean landing page with a form. The message is then forwarded directly to your inbox – no extra hosting, no extra code.
What Formcrab Gives You Out of the Box
| Feature | Benefit |
|---|---|
| Receive Messages, Hide Your Email | Keep your address invisible to bots while still getting messages straight to your inbox. |
| No Code Required | Just add a link – Formcrab serves the landing page, the form, and the backend. |
| Anti‑Spam Protection | Built‑in filters stop most automated junk before it reaches you. |
| Zero Hosting Costs | No need to provision a server or pay for a third‑party form service. |
| Customizable Email Form Link | Use GET parameters to pre‑fill fields or control post‑submission redirects. |
Customizing the Form With Simple GET Parameters
Formcrab’s private link can be tweaked with query parameters to tailor the user experience. Replace {custom-link} in the examples with your unique token (you’ll get this when you create a form on Formcrab).
1. Auto‑fill Name
If you already know the visitor’s name, pass it via the name parameter to save them time.
<a href="https://formcrab.com/f/{custom-link}?name=Hugh" target="_blank">Email us</a>
2. Pre‑set Visitor Email
Ideal when you’re sending a personalized outreach and already have the user’s email.
<a href="https://formcrab.com/f/{custom-link}[email protected]" target="_blank">Contact Support</a>
3. Custom Subject
Classify incoming messages by setting a subject that appears in your notification email.
<a href="https://formcrab.com/f/{custom-link}?subject=Urgent+Support+Request" target="_blank">Report an Issue</a>
4. Predefined Message
Provide a starter template to guide the user’s response.
<a href="https://formcrab.com/f/{custom-link}?message=I+would+like+to+request+a+demo" target="_blank">Inquiry</a>
5. Custom Redirect (next)
After a successful submission, Formcrab shows a default “Thank You” page. Override it with your own URL.
<a href="https://formcrab.com/f/{custom-link}?next=https://yoursite.com/success" target="_blank">Send and Return</a>
These parameters work together, so you can combine them to pre‑fill a name, email, subject, and message all in one click.
How to Add Formcrab to a Pure‑HTML Static Site (or a Markdown Blog)
- Create a form on Formcrab – Sign up at formcrab.com, define the email address where you want to receive messages, and copy the generated token.
- Insert the link – In your HTML, Markdown, or README, use any of the anchor examples above. No additional scripts or CSS are required.
- Publish – Deploy your static site as usual (GitHub Pages, Netlify, Vercel, etc.). Visitors clicking the link will see the Formcrab form, submit, and you’ll get the message in your inbox.
Because the form lives on Formcrab’s domain, your site never handles the POST request. This eliminates any security concerns about exposing APIs or managing CORS.
Real‑World Use Cases
| Use Case | How Formcrab Helps |
|---|---|
| GitHub Project README | Add a “Contact the maintainer” link that opens a hidden‑email form. |
| Personal Portfolio | Collect client inquiries without exposing a public email address. |
| Twitter Bio | Share a single short URL that redirects to a form, keeping your DMs private. |
| Documentation Site | Let readers report bugs or request features directly from the docs. |
TL;DR
Static sites don’t need a custom backend to collect messages.
- Stop publishing raw email addresses – they attract spam.
- Use formcrab.com to get a private, anti‑spam‑protected form instantly.
- No HTML to write, no server to host, and you can pre‑fill fields or redirect users with simple query parameters.
Give it a try today, and turn your static pages into interactive touchpoints without writing a single line of backend code. 🚀