AI Search
Getting Your Website Ready for AI Agents: Forms and Data
Updated 7 November 2026·8 min read·MeraSEO, Mumbai
People already ask assistants to find a dentist near Andheri, compare quotes or fill in an enquiry form. Whether an assistant can finish that task on your site depends on things that have little to do with ranking: does the Book Now button actually lead somewhere, can a form field be identified, is your price written as text or locked inside an image.
This post is a checklist for making those tasks completable. It sits next to our other guides rather than replacing them: crawling and indexing are in the technical SEO checklist, and being quoted in answers is in the citations guide. Here the question is narrower: can something other than a human with a mouse complete an action on your site?
Whatever the product, a browsing assistant has to do roughly the same things a person does. It loads the page, reads the text and the page structure, decides which element answers the request, and then clicks or types. It may use the page’s HTML, its accessibility tree (the structure screen readers read) or a screenshot. Where those disagree, or where an element has no label, it guesses, and guesses fail.
That tells you where to look. An agent fails at the same places a keyboard-only user, a slow mobile connection or a screen reader fails. If you have never tested your key journeys with just the Tab key, start there.
A button that runs JavaScript and goes nowhere is invisible as a destination. Every card, menu item and call to action that should open a page needs a genuine anchor with an href pointing at a real URL. In a crawl of about 230 pages on our own site, we found 286 links pointing to “#” or “javascript:void(0)”, mostly from page-builder widgets whose link field had been left at its default. Our guide to finding and fixing dead buttons shows how to locate them.
Each input needs a visible label connected to it, not just placeholder text that disappears when you type. Name fields sensibly (name, phone, email, city), mark which are required, and use the right input type so the phone field accepts a phone number. Add standard autocomplete values (name, email, tel, postal-code) so browsers, password managers and assistants can fill the form correctly. For Indian numbers, accept +91, a leading 0 and spaces rather than rejecting them; strip them on the server instead. The W3C has a good set of form tutorials showing correct markup.
“Invalid input” helps nobody. Say what went wrong and where: “Phone number must have 10 digits.” Keep the user’s entries when an error appears, and move focus to the first problem field. Avoid a form that clears itself on failure.
Image puzzles and aggressive bot filters stop real visitors as well as spam. Prefer invisible measures such as a honeypot field, server-side rate limits and email validation, and test the form after switching protection on. If a legitimate visitor on a phone cannot submit your form, assume an assistant cannot either. Offer a WhatsApp or phone alternative beside the form for people who get stuck.
If your price list is a JPEG, nobody can read it except a person looking at it. Write services as headings and lists, and state “starting from” figures or availability in text where you are willing to publish them. If you prefer not to show prices, say what the price depends on and how to get a quote. For our own costs we point to a calculator and a pricing page rather than burying numbers in graphics.
An assistant that finds your booking page once may try to return to it. Keep a dedicated, descriptive URL such as /book-appointment/ or /contact-us/, do not change it casually, and 301-redirect it if you must. On WordPress, note that renaming a post’s slug creates an automatic redirect but renaming a page’s slug does not, and booking and contact pages are almost always pages, so add that 301 yourself. Avoid putting the only booking form inside a pop-up that has no address of its own.
Structured data (JSON-LD) tells machines what the page is about in a fixed format. For most local businesses, useful types are LocalBusiness, Service, Product and Offer, plus opening hours and the area you serve. The rule is simple: it must describe what a visitor can see on the page. Marking up a price or review that is not visible is a policy problem, not an advantage. Not every schema.org type produces a rich result in Google (Service, for example, does not), but accurate markup still describes the page to any machine that reads it. Google’s structured data documentation lists the types it supports and its rules. Google’s Rich Results Test checks markup against those types, and the Schema Markup Validator checks general schema.org syntax.
Put opening hours, full address, phone, WhatsApp number and the neighborhoods you serve in the page body or footer as ordinary text, and keep them identical to your Google Business Profile. “Open 10 to 7, closed Sunday” in text beats a screenshot of a timetable.
Pop-ups that cover the whole screen, cookie banners that cannot be dismissed and sticky bars that hide the submit button all get in the way of whoever is using the page. If you are not sure how bad it is, our free SEO audit reports your real mobile performance from Google PageSpeed Insights.
Descriptive link text, alt text on meaningful images, headings in order and visible focus states help every kind of user. We list them in the website accessibility checklist, so we will not repeat them. Many agent-readiness fixes come free once those are done.
Write down each failure with the page URL. You will usually find that three or four fixes remove most of the friction.
Announcements about new agent standards and protocols appear regularly, and some will matter. Do not rebuild your site around one until it is well documented and you can see real use. The basics above work with whatever arrives, because they make the site understandable to machines and people alike. If you want an assistant of your own on the site, that is a separate project; see our AI chatbot integration page.
It means making sure an automated assistant can find information and complete actions on your site. In practice that is real links, labeled forms, clear error messages, text-based prices and hours, stable booking URLs and accurate structured data. Most of it is ordinary good web practice.
No. Start with standard HTML, accessible forms and valid structured data. Only adopt a specific protocol if it is well documented, supported by the tools your customers use and relevant to your business. Fixing the basics gives you the larger gain first.
It helps machines understand what a page offers, such as a business, a service or a product with its price, as long as the markup matches visible content. It does not fix a broken form or a dead button, so treat it as one part of the checklist.
Open the page on a laptop and complete the form using only Tab, Shift+Tab, Enter and Space. If you cannot reach a field, cannot tell which field you are in or cannot submit, an assistant or keyboard user will struggle too. Fix the order, labels and focus styles.
We audit your key journeys, fix dead links and forms, and add structured data that matches your pages.
See AI search optimization →WhatsApp us