Carrd form not working on a one-page site

A form has two halves: the fields a visitor fills in, and the place the entries go. A builder lets you design the first half in full, so the form looks finished even when the second half is empty, mistyped, or pointed at a service you have not connected. When the destination is missing, the visitor presses Send, sees the button change, and gets no confirmation. Layout adds a second break. A one-page site stacks its sections, and a form in a section with a set height can clip its bottom field and button, so a visitor cannot finish even when the destination works.

• Open the form's settings in the builder and confirm an entry destination is set and saved.
• Submit the form on the live address, not in the editor, and read the message the visitor sees.
• Check the destination's inbox or list for the test entry after you submit.
• At phone width, scroll to the Send button and confirm it sits inside its section, not below the edge.
• Open the console after submit and look for a failed request to the destination address.

The visitor scrolls down the one page, reaches the contact section, fills in the fields, and presses Send. The button may flash, change its label, and return to normal. The fields may clear. Nothing else appears, because the page has no message set for a successful send, or the send failed before the page could show one. The visitor cannot tell a sent message from a lost one, so they write to the photographer somewhere else, or they do not write at all.

The destination is checked first, because nothing else matters without it. Open the form's settings in the builder and confirm an entry destination is saved, then send one test entry and check that it arrived at that address or list. A destination that was saved once and later disconnected, or an address typed with a small mistake, looks exactly like a working form in the editor. Only a test entry from the live page shows which one you have.

The layout is the second check, and it is easy to miss on a one-page site. A section can be given a set height, and a form inside it can have its bottom field and Send button clipped at phone width. The visitor then cannot reach Send, even though the destination works. Scroll the live page on a phone and make sure the button sits inside its section.

The editor is often set to the width you designed for, not the width a phone gives a visitor. The simulated visitor loads the live page, scrolls down to the form the way a stranger would, fills it in, and presses Send. The report records whether the Send button responded, any console error or failed request on that step, and a screenshot of the screen after the press. It does not read your destination, so you still check the inbox or list yourself.

A one-page site changes as you add offers, sections and a domain. A moved destination, a changed domain or a disconnected service can stop entries, and a new section can clip the Send button again. After each edit, submit the form on the live address from a phone and a laptop, and check the destination for the test entry before you send traffic to the page.