A practical guide for agencies and developers. <\/p>\n\n\n\n
<\/p>\n\n\n\n
We’ll set up four things: Step 1: Use a native WordPress form, not Typeform<\/p>\n\n\n\n Step 2: Reliable email delivery (Microsoft 365 + OAuth)<\/p>\n\n\n\n Step 3: The llms.txt<\/strong><\/code>, an agent-card.json<\/strong><\/code>, JSON-LD schema, and a contact form an AI agent can actually submit.<\/p>\n\n\n\nMore traffic to your site is going to come from AI agents acting on behalf of humans \u2014 ChatGPT browse mode, Perplexity, Claude for Chrome, custom-built agents. If your site is built purely for human eyeballs, you're becoming invisible to them.
At MoyaHost we build AI chatbots, voice agents, and workflow automations \u2014 so running a site that isn't agent-ready wasn't an option. This post is the exact setup we deployed, including the mistake that cost me a rewrite.
Starting point:<\/strong> a working WordPress site with a functioning contact form that sends email notifications. If you don't have that, fix it first.
Our stack:<\/strong> WordPress on cPanel, Elementor, Fluent Forms (free), Fluent SMTP (free) \u2192 Microsoft 365, Code Snippets, Cloudflare DNS.<\/pre>\n\n\n\nTypeform embeds are iframes from `typeform.com<\/strong>`. For an agent to submit one, it has to drive a browser \u2014 slow, flaky, and not documentable in a standard.\n\nA native form lives on your own domain with a submission endpoint you control and can describe.\n\nWe picked Fluent Forms. WPForms, Gravity Forms, or Contact Form 7 all work too; the endpoint details below will differ.\n\nBuild the form, replace your Typeform embed with the shortcode (`[ fluentform id= \"1\" ]<\/strong>`), and confirm it renders.<\/pre>\n\n\n\n
WordPress's default `wp_mail()` is notoriously unreliable on shared hosts. You need SMTP.\n\nCloudflare is not an SMTP provider.<\/strong> This catches people out. Cloudflare does inbound Email *Routing* (forwards incoming mail to your inbox), and has an Email *Sending* product in private beta \u2014 but nothing usable for a WordPress form today.\n\nIf you already pay for Microsoft 365, use it. No extra service, no extra cost, emails come from the real mailbox.\n\nCritical 2026 timing note:<\/strong> Microsoft has deprecated Basic Authentication for SMTP. After April 30, 2026, username-and-password SMTP to Office 365 stops working. You must use OAuth 2.0 via Microsoft Graph.\n\nFluent SMTP handles this natively. The setup:\n\n1. In Microsoft Entra \u2192 App registrations \u2192 New registration<\/strong> \u2014 multi-tenant, use the callback URL Fluent SMTP shows you.\n2. API permissions<\/strong> \u2014 add Microsoft Graph delegated permissions: `SMTP.Send`, `Mail.Send`, and `offline_access`. Without `offline_access`, tokens expire after an hour.\n3. Grant admin consent<\/strong> for all three.\n4. Certificates & secrets \u2192 New client secret<\/strong> \u2014 set to 24 months (the max) and calendar-reminder the renewal.\n5. 'Web' redirect URI<\/strong> : https:\/\/moyahost.ai\/wp-json\/fluent-smtp\/outlook_callback\n6. Plug the Application ID and Client Secret Value into Fluent SMTP and authenticate.\n\nIn Fluent Forms' notification settings, set `From Email` to the mailbox your app has access to (e.g. `info@moyahost.ai`), and `Reply-To` to `{inputs.email}`. Without Reply-To, hitting Reply in Outlook sends back to yourself.<\/pre>\n\n\n\nllms.txt<\/strong><\/code> and llms-full.txt<\/strong><\/code> files (the AI-SEO layer)<\/p>\n\n\n\n`llms.txt<\/strong>` is a 2024 proposal by Jeremy Howard (Answer.AI): a curated, markdown-formatted list of your site's important pages at the domain root, so LLMs can understand your site without crawling full HTML.
Example:
<\/pre>\n\n\n\n