This checklist is for small-business owners whose contact page feeds a real inbox: local-service companies, restaurants, studios, and simple shops where a person has to reply. A good contact page is not just name, email, message. It should help the visitor choose the right path, give the business enough detail to answer once, and prevent the first reply from being “Can you send more details?”
Last reviewed: 2026-04-23. Builder features and pricing change, so verify the form, storage, and notification options on your builder before publishing.
The builder matters less than the contact flow. Whether you use a hosted builder, a Shopify theme, or WordPress, the useful question is not “Does this platform have a form?” It is “Will this page send the right details to the right person on the first try?”
Quick contact page checklist
A contact page should answer three things fast: who should use it, what details are required, and what happens after submission. Use this short checklist before you write the longer copy.
- Say who the form is for: name the requests you accept, such as quotes, bookings, private events, order issues, press, or partnerships.
- Route the inquiry first: make the first field a reason for contact so the message goes to the right person or reply template.
- Require only useful fields: collect details that change the first response, not every detail you might want later.
- Ask for the missing identifier: use an order number, requested date, ZIP code, current URL, or event size when that answer determines the next step.
- Set the response window: tell visitors when to expect a reply and what to do for urgent requests.
- Confirm the submission: show a clear success message, send a notification, and test that the inbox receives it.
- Keep a fallback visible: offer phone or email when the cost of missing a lead is higher than the cost of filtering spam.
- Check the basics before launch: test mobile layout, HTTPS, spam controls, email delivery, and page speed.
Decide who should use the page
The page should make the right visitor feel expected and the wrong visitor choose another path. If the contact page handles every possible request with one blank box, the inbox has to do all the sorting.
Start by naming the jobs your contact page is allowed to handle. A one-person photographer may need only new bookings, press, and print questions. A restaurant may need reservations, catering, lost items, private events, and delivery issues. A store may need product questions, order problems, returns, and wholesale inquiries. If all of those visitors see one blank “Message” box, the first reply will usually ask for details the page could have collected.
Shopify’s contact page documentation says all themes include a built-in contact form that can be applied to pages, and submissions go to the store’s sender email address.[1] That is enough for a simple store, but it means the page copy and fields have to do the sorting. Ask for an order number when the visitor is already a customer. Ask for product, quantity, and deadline when the visitor is asking about wholesale. Do not ask a first-time buyer for a company name unless that answer changes your reply.
Local businesses should also make the contact page match the business facts customers see elsewhere. If your contact page says “call anytime” but your public hours say weekdays only, expect avoidable calls and “Are you open?” messages. If you serve only certain ZIP codes, collect location before asking for a long project description.
- Reason for inquiry: use options such as “new website quote,” “existing customer support,” “order issue,” “private event,” “press,” and “partnership,” so the submission can be triaged without reading a paragraph twice.
- Business or project type: ask whether the visitor is building a restaurant site, portfolio, local-service site, ecommerce store, booking site, or one-page landing page, because each one changes the follow-up questions.
- Current website state: ask for the existing URL if they are replacing an older site or moving away from another builder.
- Timeline: separate “ready to start,” “pricing research,” “broken site,” and “event deadline,” because those need different replies.
- Scope detail: collect the smallest useful version of scope, such as “one-page site,” “five-page service site,” “menu and reservations,” “online store,” or “portfolio with inquiry form.”
- Location or service area: ask for city, ZIP code, or service area when the business travels, delivers, books appointments, or depends on local search.
- Preferred reply channel: let the visitor choose email, phone, or text if the business can truly support those channels.
- Files or links: ask for a logo, menu PDF, existing site URL, Google Drive folder, portfolio, or product sheet only when it changes the next reply.
- Consent and limits: keep marketing opt-in separate from the contact request, and say when the form is not monitored for urgent issues.
The Squarespace form field guide recommends no more than 30 fields to keep a form user-friendly and quick to load, and its file upload field allows up to 5 files with a 10 MB limit per file.[2] Treat those as upper limits, not goals. A first contact page usually works better when it collects the answer that changes the first response, then moves everything else to email, a call, or a booking flow.
Set response expectations
Visitors should know what happens after they submit: whether they will get an email, when to expect a reply, and what to do if the issue is urgent. The business should receive a submission that is easy to identify before anyone opens it.
Webflow’s Forms overview says form success and error messages can be edited.[3] Use that space for useful copy, not a vague “Thanks.” A better success message says, “We received your catering request and usually reply within one business day. For same-day orders, call the restaurant.”
Form storage and notification rules also matter. Squarespace Form Blocks can use a post-submit message or redirect and can send submissions to storage options such as email, Google Drive, Zapier, and Mailchimp.[4] Carrd’s Contact form documentation says Contact forms require Pro Standard or higher and can send messages to the account email or up to five recipient email addresses.[5] Those details matter because “we never saw your message” is usually a setup problem, not a writing problem.
| Inquiry type | What the visitor should see | What the business should receive |
|---|---|---|
| New website quote | “Tell us what you are building, what exists now, and the launch window.” | Name, email, current URL, business type, scope, timeline, and best reply channel. |
| Existing ecommerce order | “Include the order number and the email used at checkout.” | Order number, order email, issue type, and product name before support replies. |
| Restaurant or local-service request | “Use this form for non-urgent requests; call during posted hours for same-day needs.” | Service area, requested date, party or job type, callback window, and phone number. |
| Press or partnership | “Include publication, organization, deadline, and the exact ask.” | Sender identity, outlet or company, deadline, link, and requested next step. |
Keep the form as short as possible, but no shorter
Every required field should change the first useful response. If a field only satisfies curiosity, make it optional or move it to the second conversation.
“Name” and “email” are required because you need to reply. “Phone” is required only if phone follow-up is part of the process. “Budget” is useful for custom services, but it may be a bad fit for a restaurant catering inquiry where date, headcount, menu style, and venue are more important. “Company name” matters for B2B, wholesale, and invoices; it is clutter for a local dog groomer or illustrator taking a first inquiry.
Do not copy every available builder field into the form. Most builders make it easy to add dropdowns, checkboxes, uploads, and hidden fields, but the checklist should match how your team actually handles requests. If nobody checks files before the first reply, do not require uploads. If the owner answers every message personally, use simple routing labels instead of a complex department menu.
Put technical checks in service of the form
Technical checks belong on the checklist only when they help people submit the form or help the business receive the message. Keep them short, testable, and tied to the contact-page goal.
- Email delivery: if the form sends auto-replies or notifications from a custom domain, set up SPF, DKIM, and DMARC before launch. DMARC.org explains that DMARC policies are published as DNS TXT records and tell receivers what to do with mail that fails authentication.[6]
- Page speed: keep maps, chat widgets, review embeds, and booking scripts below the form unless they are needed to complete the request. Google’s web.dev guidance lists good Core Web Vitals thresholds as Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less at the 75th percentile of page loads.[7]
- Search snippet: use a clear page title and opening line, such as “Contact Ridgeway Dental Studio in Austin,” not only “Get in Touch.” Google Search Central says good page titles are unique, clear, concise, and accurate, and snippets can come from visible page content or the meta description.[8]
- Trust checks: confirm the published contact page loads over HTTPS, works on mobile, shows a success or error message, and sends the test submission to the right inbox.
Worked example: reduce a quote request from four replies to one useful submission
The fastest way to improve a contact page is to remove one vague message and replace it with a few routing answers. Use this example as a model, not a benchmark: a solo electrician is replacing an outdated website and wants fewer vague quote requests.
- Before: the form has three fields: name, email, and message. A visitor writes, “Need work done next week.” The owner replies asking for address, job type, photos, timing, and phone number. The visitor answers in pieces across four messages.
- Route first: the revised form starts with “What do you need?” and offers “new installation,” “repair,” “inspection,” “billing,” and “not sure.”
- Ask only what changes dispatch: the form asks for ZIP code, job type, preferred callback window, whether power is currently out, and a photo or link if available.
- Set the urgent path: the copy says the form is for non-urgent requests and gives the phone number for same-day issues during posted hours.
- After: one submission contains six useful answers, so the first reply can be “We serve your ZIP code, this looks like a repair request, and the next step is a call during your selected window.”
The launch rule is simple: publish the page only when a stranger can choose the right path, submit the minimum useful details, understand the response window, and still find a direct fallback if the form fails.
If you are still shaping the site, start at Website Builder, describe the business, and use the AI-built draft as the place to add these contact rules before you publish.
FAQ
What should a contact page include?
A contact page should include who should use the form, the reason for inquiry, the minimum details needed to reply, the expected response time, and a fallback such as phone or email when missing the request would be costly. Add location, order number, project type, requested date, or file upload only when that answer changes the first response.
Which fields should be required on a contact form?
Require only fields that change the first response. If you can answer the first email without a budget range, make budget optional. If you cannot route without service type, order number, requested date, or ZIP code, make that field required.
How should a contact page route different inquiries?
Put the routing choice near the top of the form. Use plain options such as quote request, existing customer support, order issue, private event, press, and partnership. Then show or request the details that fit that path, or at least label the submission clearly in the notification email.
Should a contact page show an email address or phone number, or only a form?
Show a fallback when missing a lead would be expensive. A form gives you structure, but an email address or phone number helps visitors who cannot submit, need accessibility support, or have a request that does not fit your options. If spam is a concern, keep the direct email less prominent than the form and use mail filtering.
Do small businesses need SPF, DKIM, and DMARC for a contact form?
They need them when the business domain sends email, especially auto-replies, booking confirmations, invoices, or form notifications. If the builder only sends notifications from its own system, the setup may be different, but the business should still authenticate its main email domain before using it for customer replies.
Sources
- [1] Shopify Help Center, contact page template: https://help.shopify.com/en/manual/online-store/themes/customizing-themes/common-customizations/add-contact-page
- [2] Squarespace Help Center, form fields explained: https://support.squarespace.com/hc/en-us/articles/205814018-Form-fields-explained
- [3] Webflow Help Center, Forms overview: https://help.webflow.com/hc/en-us/articles/33961347548563-Forms-overview
- [4] Squarespace Help Center, Form Blocks storage and post-submit options: https://support.squarespace.com/hc/en-us/articles/206566737-Form-blocks
- [5] Carrd Docs, setting up a Contact form: https://carrd.co/docs/forms/setting-up-a-contact-form
- [6] DMARC.org, DMARC overview: https://dmarc.org/overview/
- [7] web.dev, Core Web Vitals: https://web.dev/articles/vitals?hl=en
- [8] Google Search Central, SEO Starter Guide: https://developers.google.com/search/docs/fundamentals/seo-starter-guide