Mini lesson · English

How to add email subscriptions to your website

Connect a provider-hosted subscription form and test joining, email confirmation and leaving with your own address.

Start the interactive lessonRead the lesson below

Who is this for?

People who want visitors to receive new posts or lessons. You can use a provider form and a coding assistant; no HTML editing knowledge is required.

Before you start

Your own email-marketing account and a test inbox. A ready website starter is supplied. The worked route uses a Mailchimp-hosted public form with double opt-in; actual account options and terms may vary. Worked answers are illustrative examples, not completed tests on your account. Replace their sample observations with your own results, or identify the step that is still blocked.

Estimated time: 26–39 min

Estimates for the supplied starter files with prerequisite accounts and tools ready. Setup, deployment queues and delivery/DNS waits take additional time. Planning estimates with accounts ready. Sender setup, plan restrictions and delivery delays may add time; check your provider’s current terms.

What you will learn

  • Create a clear subscription entry point.
  • Verify confirmation before treating a person as subscribed.
  • Check repeat signup and unsubscribe without changing real readers.

Workshop files

Step 1

Explain what people are signing up for

Ask for ongoing updates clearly.

Choose one honest promise, such as new project notes or lessons. Use the supplied page and ask your assistant for a short heading, explanation and button that reflect that promise.

An address sent through a contact form is not permission for ongoing updates. Keep the two purposes distinct.

A concrete example

The supplied page says New writing and lessons and explains the email purpose. Keep the promise specific enough that the visitor can decide whether those future messages are useful.

Use the supplied website starter and my provider’s public signup URL. Help connect a clear updates button without adding another email backend. Guide me through double opt-in and a test using only my own address. Keep requested, confirmed and unsubscribed states distinct. Do not send to an existing audience or automatically re-subscribe anyone.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Let readers ask for your next post

The result is a confirmed subscriber who can leave again—not just an email address saved somewhere.

A newsletter sign-up asks for ongoing email updates. A contact form sends one message to a site owner. The two forms may both contain an email field, but their purposes are different.

For this lesson, the visitor asks for new writing and lessons. We will describe that clearly, ask the person to confirm their address, and test the unsubscribe path.

Our work on emrevarol.com showed why confirmation feedback and delivered email matter. This workshop teaches the same distinction using a provider-hosted form, rather than rebuilding the site’s custom code-verification service.

Worked example: what the visitor is agreeing to

“Get an email when a new article or lesson is published” describes the update. “Send” beside an unexplained email box does not tell the visitor what happens next.

Our example is a small practice newsletter. Use your own mailbox during testing; do not add other people just because you know their addresses.

Extra implementation exercise

A visitor enters an address to ask you one question through a contact form. Does that action, by itself, show that they asked to receive your future posts?

Show a worked solution

No. The visitor asked to send a message, not to receive future posts. Offer a separate sign-up action that describes the updates.

Explain what updates the sign-up is for before asking the visitor to submit their address.

  • Distinguishes a one-off contact request from a request for future updates.
  • Proposes a clear, separate sign-up action instead of silently adding the address.

Step 2

Plan the confirmation messages

The page should explain the next action truthfully.

Prepare text for the stage after address entry and for the stage after confirmation. Ask the assistant to show a pending message until the email confirmation is complete.

Keep requested, confirmed and unsubscribed separate. A visitor closing the browser does not complete confirmation.

A concrete example

Address entered → “Check your inbox to confirm.” Confirmation completed → “Your subscription is confirmed.” The first message gives the next action instead of pretending the second has happened.

Mailchimp: double opt-in

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Understand the confirmation journey

Submitting an address starts the request. Confirming it is a separate action.

Double opt-in means the visitor first submits a sign-up form, then follows a confirmation message sent to that address. In this worked route, only after confirmation should the contact be subscribed to marketing updates.

Think in terms of three learning states: requested, confirmed, and unsubscribed. Your provider’s interface may use more detailed labels; check the actual contact status instead of inferring it from a website message.

A verification email can be delayed or land in spam. The page after form submission should explain the next action without claiming that the address is already confirmed.

In this double opt-in flow, the address remains unconfirmed after submission, even if the visitor closes the browser. The next required action is to open the confirmation email and use its confirmation link. Inspect the resulting provider contact status before calling it subscribed.

Worked example: confirmation is still pending

A visitor submits the form and closes the browser without opening the confirmation email. Their intention may be genuine, but this double opt-in journey has not been completed.

A suitable page message is: “Check your inbox to confirm your subscription.” After the confirmation action, a success page can say that the subscription is confirmed.

Mailchimp: double opt-in

Extra implementation exercise

Your sign-up page says “You’re subscribed!” immediately after address entry. The confirmation email has not been opened. What message would you use at this point, and why?

Show a worked solution

Use “Check your inbox to confirm your subscription.” It names the action still required.

Reserve a confirmed-success message for the completed confirmation step, and verify the provider’s contact status.

  • Uses a pending-confirmation message with an explicit inbox action.
  • Does not count the submitted address as a confirmed subscriber.

Step 3

Prepare a practice audience

Work in your own provider account before connecting the website.

Create or select a separate practice audience and enable double opt-in where supported. Review its public form and sender setup. Use the current provider guide if labels differ.

Record the audience name beside the form URL. Check the actual account settings rather than assuming confirmation is enabled by default.

A concrete example

Keep the audience name and its public form URL together. If a form belongs to another audience, confirmations and contact states can appear somewhere different from where you are looking.

Mailchimp: double opt-in · Mailchimp: subscribed and other contact statuses

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Set up a practice audience and double opt-in

Configure the actual flow before putting a sign-up link on the website.

In your own Mailchimp account, create or choose a practice audience. An audience is the provider’s collection of contacts and related settings; use a practice one so this exercise does not change an established mailing list.

Find that audience’s email opt-in settings and enable double opt-in. Do not assume it is on by default: account and audience settings can differ. Use the current help page linked below if the dashboard wording has changed.

Review the hosted form’s sender identity and visitor-facing copy. Complete any sender setup required by your account. This lesson does not assume a free plan or that every account exposes identical options.

Open the form-sharing controls from the intended audience itself, and record that audience name next to the public form URL before copying it to the website. If you cannot establish which audience owns an old URL, obtain the public link again from the intended audience rather than guessing from the URL text.

Worked example: avoid testing the wrong audience

Suppose the audience used by the public form still has single opt-in, while another audience has double opt-in. Your test cannot verify confirmation for the public form simply because the setting exists elsewhere.

Record which audience the form uses and check its setting directly.

Mailchimp: double opt-in · Mailchimp: subscribed and other contact statuses

Extra implementation exercise

You enabled double opt-in for a practice audience, but your website link opens a form for a different audience. Which part should you correct before testing?

Show a worked solution

Confirm which audience the public form belongs to. Use the intended audience’s form URL and verify double opt-in for that same audience.

A setting on one audience does not prove how a form attached to another audience behaves.

  • Checks which audience owns the public form URL.
  • Makes the chosen form and its audience’s opt-in setting agree before interpreting test results.

Step 4

Get a visitor-facing link

A subscriber should not need your account login.

Copy the public hosted form URL from the intended audience’s sharing controls. Open it in a private browser window before asking the assistant to connect it.

The page should show the signup form, not the provider’s account dashboard. Replace the supplied placeholder only with the real URL you tested.

A concrete example

A dashboard address may open perfectly in your signed-in browser while leaving visitors at a login screen. A private-window visit checks the actual visitor route.

Mailchimp: share a public sign-up form

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Get the public form URL

Visitors need a public sign-up page, not a link to your account dashboard.

Use the provider’s form-sharing controls to obtain the hosted public sign-up URL. A hosted form lives on the provider’s service; your website can link to it without embedding account credentials.

Open that URL in a private browser window. You should see a visitor-facing sign-up form without being asked to access your account dashboard.

The starter contains YOUR_PUBLIC_SIGNUP_URL as a deliberate placeholder. Replace it with the real HTTPS form address from your own account before publishing. An example URL in a lesson cannot subscribe people to your personal audience.

Worked example: public link versus private control panel

A visitor-facing form asks for the information needed to sign up. A dashboard page asks you to manage contacts or log in as the site owner. Only the first belongs behind the website’s subscription link.

Use the sharing control rather than copying whichever address happens to be in the browser while you are logged in.

Mailchimp: share a public sign-up form

Extra implementation exercise

The Subscribe button works while you are logged in, but your friend sees an account login page. What is the likely mistake, and how will you verify the replacement?

Show a worked solution

You may have linked to the account dashboard instead of the public form. Get the form’s shareable URL and open it in a private window.

Do not solve this by giving visitors your account credentials.

  • Identifies a private dashboard link or otherwise incorrect public URL.
  • Obtains the provider’s shareable form URL and tests it in a private browser window.

Step 5

Connect the supplied website

Let the assistant make the small website edit.

Give your coding assistant the tested public URL and the supplied starter. Ask it to replace the placeholder and keep the subscription promise clear, then publish the practice page when ready.

Try the website button on a narrow screen and with the keyboard. It should open the same public form you already checked.

A concrete example

The website edit can be small: replace its placeholder link with the tested public form URL. Keep the update promise visible next to it, then try the button as a visitor.

Mailchimp: share a public sign-up form

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Connect your website with one clear link

Give the visitor a clear reason to subscribe and a working path to the hosted form.

Open starter/index.html. Replace the placeholder in the link with the public form URL you just tested. Keep the copy about new writing and lessons, or adapt it to what you will actually send.

This route uses a normal link. It does not require an email-service API key, a custom backend, or a second email field that merely forwards an address between pages.

Publish the changed page on your own site and try the link from a small phone-sized window. Make sure the button is readable, keyboard-accessible and clearly labelled.

Worked example: the site’s entry point

The placeholder below is an instruction to the site owner. Replace it before testing the live journey. The workshop’s full file also includes page structure and styling.

<h1>New writing and lessons</h1>
<p>Get an email when a new article or lesson is published.</p>
<a href="YOUR_PUBLIC_SIGNUP_URL">Subscribe by email</a>
<p>You can unsubscribe using the link in each newsletter.</p>

Mailchimp: share a public sign-up form

Extra implementation exercise

You have the correct public URL. Which exact attribute will you change in the starter, and what two visitor actions will you test after publishing?

Show a worked solution

Replace the href value in starter/index.html. From the published website, activate the link and complete a test sign-up using your own address.

Also try the link on a narrow screen or with the keyboard, so the feature is usable as well as connected.

  • Replaces the anchor’s href placeholder with the actual public HTTPS form URL.
  • Tests reaching the public form and starting a sign-up from the published website, including a small-screen or keyboard check.

Step 6

Confirm one address end to end

Check the email and provider status, not just the page text.

Start from your practice website and submit your own address. Read the pending message, find the confirmation email, use its link and inspect the resulting contact status in the intended audience.

Record the state before and after confirmation. If the email is missing, check address, spam and provider delivery information before repeating submissions.

A concrete example

Use the same controlled address throughout: website entry → pending instruction → received confirmation email → subscribed status. A success-looking page cannot substitute for a missing confirmation step.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Follow one address through confirmation

Test the whole journey with an inbox you control.

Start at your published website, open the public form, and submit your own test address. Record what the page says before touching the email.

Find the confirmation message, check which list or updates it describes, and follow its confirmation action. Then inspect the contact’s status in the intended audience.

If a confirmation message is missing, investigate the destination address, spam folder, audience opt-in setting and provider delivery information. Repeating submissions without looking for the failed step can make the result harder to understand.

Worked example: a test record that tells a story

A useful record names the last completed action. It does not compress every stage into a single “works” checkbox.

Started from published website: yes / no
Public form opened without owner login: yes / no
After address entry, page asks me to confirm: yes / no
Confirmation email received: yes / no
Confirmation action completed: yes / no
Provider status after confirmation: __________
Time tested: __________

Extra implementation exercise

The confirmation email arrives, but you have not clicked its confirmation action. Your test record says “confirmed”. Which observation is missing?

Show a worked solution

Receiving a confirmation email is evidence of delivery, not evidence that its confirmation action was completed. Follow that action and inspect the resulting contact status.

If the status remains unresolved, keep the result marked unresolved.

  • Requires completing the confirmation action.
  • Checks the resulting contact status, rather than equating email delivery with confirmation.

Step 7

Test leaving and repeat signup

Respect the person’s choice throughout the journey.

Try the same controlled address again and note the provider’s actual response. To test leaving, keep the practice audience limited to your own test contact. If your account permits a practice update targeted only to that address, review its one-recipient list before sending, then use the unsubscribe link in the message actually received.

Verify the resulting contact state. If you cannot safely send to only that controlled address, leave the received-message unsubscribe check unrun. A manual dashboard unsubscribe or preview is a different check; do not send to an existing audience to finish the exercise.

A concrete example

For the leave test, the message must actually reach your controlled address. Inspect the recipient list before sending: one test contact, no existing audience. Use the link in that received update, then inspect the resulting contact state.

Mailchimp: subscribed and other contact statuses

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Check repeat sign-up and unsubscribe

A usable subscription has a clear way out, and repeated attempts should not confuse the reader.

Submit the same test address again and observe the provider’s actual response. It may explain that the address is already subscribed or guide the person through an allowed next step. Do not invent a new confirmed subscriber for every click.

When you have a confirmed test contact, inspect an appropriate provider-generated marketing email or preview and find the unsubscribe route. Test it with your own contact and verify the updated contact status. Sending a test message alone may not exercise a real unsubscribe link; follow the provider’s current testing guidance.

If you want to test signing up again, do it through the public form and observe any confirmation step the provider requires. Do not silently restore someone’s subscription from the account dashboard.

For a genuine unsubscribe-link test, a provider preview or account-side manual unsubscribe is not automatically equivalent to the received-message journey. Where your account permits it, prepare a marketing send targeted only to the single test address you control, check the recipient count is exactly one, then use that received message’s unsubscribe link and verify its state change. If you cannot do that safely, mark the end-to-end link test not performed; manual account changes verify a different operation. This lesson does not ask you to send to an existing real audience.

Worked example: unsubscribed means the result changed

A person clicks unsubscribe. An “Unsubscribed” page is useful feedback, but the stronger check is the contact’s resulting status and exclusion from the next intended marketing send.

Use only your own test contact. This lesson does not ask you to send a campaign to a real audience.

Mailchimp: subscribed and other contact statuses

Extra implementation exercise

Your own test contact unsubscribes. A developer proposes changing its status back to subscribed automatically the next time the person opens the website. Would that preserve the visitor’s choice?

Show a worked solution

No. Opening a website is not a new request for updates. Keep the unsubscribed state until the visitor explicitly signs up again through an appropriate flow.

Verify the status change using your own test contact before inviting others.

  • Rejects automatically undoing an unsubscribe just because the website is opened.
  • Requires a new explicit sign-up action and the applicable confirmation flow.

Step 8

Finish the small subscription journey

Hand over clear messages and observed states.

Connect your update promise and public form, then repeat the join–confirm–leave flow with your own address. Save the page and a short test record.

Keep pending and confirmed messages accurate and record any provider limitation. A custom signup backend is optional further work, not this lesson’s requirement.

A concrete example

A concise completion record can use four rows: requested, confirmed, repeated and unsubscribed. If your account prevented a one-address update, leave the received-message unsubscribe row marked not run instead of inventing a result.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Your assignment: make a small sign-up journey understandable

Adapt the copy for your own site and prove that the visitor can join and leave.

Choose a genuine update you can describe, such as new project notes or new lessons. Write a heading, one explanatory sentence, a button label, a pending-confirmation message and a confirmed-success message.

Connect the public form to your site and test the journey using your own address. Record the observed states before confirmation, after confirmation and after unsubscribe.

Our site needed custom code-based verification for its own design. A custom backend is a separate project: first show that you understand the states and the evidence using this managed route.

Worked example: words for three different moments

Entry: “Get new project notes by email.” Pending: “Check your inbox to confirm.” Confirmed: “Your subscription is confirmed.”

Those messages describe different moments. The provider’s actual contact status remains the final check for each change.

The complete reference walkthrough is available in reference/assignment-walkthrough.txt. Compare its steps with your own result; fill the test record from observations in your own project.

Extra implementation exercise

Build your own site’s sign-up entry point and complete a join–confirm–unsubscribe test. Show how each message matches the state at that moment.

  1. Replace the public-form placeholder and adapt the entry copy.
  2. Use only your own address for the live test.
  3. Record the contact state before confirmation, after confirmation and after unsubscribe; include a repeated-sign-up observation.
Show a worked solution

Entry copy: 'New project notes by email'. Explanation: 'Get an email when a new project note is published.' Button: 'Subscribe by email'. Pending: 'Check your inbox to confirm.' Confirmed: 'Your subscription is confirmed.' Adapt this copy to the updates you will actually send.

Connect the intended audience's public form URL, verify double opt-in for that audience and open the website link signed out. Submit only your own address. Before clicking confirmation, record the pending/unconfirmed status; after clicking it, inspect the actual subscribed status.

Observe repeat sign-up without creating fictitious new subscribers. Use the provider's supported unsubscribe test path and verify the resulting unsubscribed state. An unclear response is unresolved: inspect the contact status and the provider's current audience/unsubscribe guide rather than silently changing the account status back.

  • Entry copy describes the actual updates and the public link opens without owner login.
  • Pending feedback asks for confirmation; confirmed feedback follows actual confirmation.
  • A verified contact state and a tested unsubscribe route support the completion claim.

Was this lesson useful?

Leave a like, or share it with someone who could use it.

Continue learning

Explore the other lessons