To find the contact form on a website, follow the site's own links first (a Contact, Contact us or Get in touch link in the menu or footer), then check the sitemap for URLs containing "contact" or "enquiry", and only then try two or three common paths such as /contact, /contact-us or /pages/contact. On the page, confirm it is a contact form by looking for a message box plus name and email fields, and set aside search, newsletter, login and booking forms.
This guide is part of the contact form outreach series and covers the bulk method for a list of websites.
Step 1: links in the menu and footer
The contact page is almost always linked from every page. Fetch the homepage, collect all links, and score them.
| Link text or URL contains | Score | Notes |
|---|---|---|
| "Contact", "Contact us", "Get in touch" | High | Standard wording |
| "Enquire", "Enquiries", "Make an enquiry", "Talk to us" | High | Common on UK service sites |
| "Request a quote", "Get a quote" | Medium | A quote form; may be the only form |
| "Book", "Book now", "Appointments" | Low | A booking form, usually wrong for outreach |
| "Support", "Help centre" | Low | A support desk |
mailto: link | Note | Record the address; there may be no form at all |
Check the footer separately from the main menu. Some sites hide "Contact" behind a menu button on mobile layouts, but the footer link is usually still present in the HTML.
For non-English sites, add local words: kontakt (German, Polish, Scandinavian languages), contacto (Spanish), contato (Portuguese), nous-contacter or contact (French), contatti (Italian).
Step 2: the sitemap
If no link is found, the sitemap is the next best evidence.
- Read robots.txt. It lives at
/robots.txtat the root of the site (RFC 9309 says it "MUST be accessible in a file named "/robots.txt""). Sites often list their sitemap on aSitemap:line. While you are there, note anyDisallowrules that apply to your crawler and respect them. The RFC is clear that these rules "are not a form of access authorization", but they are the site's published preference about automated access. - Try the usual sitemap locations if robots.txt does not list one:
/sitemap.xml,/sitemap_index.xml(common with WordPress SEO plugins) and/wp-sitemap.xml(WordPress's built-in sitemap). - Follow sitemap indexes. Large sitemaps are split; the pages sitemap is where the contact page will be.
- Search the URLs for
contact,enquir,get-in-touch,quoteand local-language equivalents.
Step 3: a few common paths
Only if links and sitemap fail, try a short list of paths. Each guess is a request to someone else's server, so keep the list short.
| Path | Where it is common |
|---|---|
/contact | Many site builders and custom sites |
/contact-us | WordPress sites (page slug from the title "Contact us") |
/pages/contact | Shopify stores |
/contact.html, /contact.php | Older hand-built sites |
/get-in-touch | Agencies and service businesses |
Try two or three per site, at a polite pace. Treat a redirect to the homepage or a "page not found" template returned with a 200 status as a miss; compare the page title with the homepage title to catch these soft 404s.
Step 4: detect the form
A page called "Contact" does not always contain a form. Some show only an address and phone number; others embed a form that only appears after scripts run.
What a contact form looks like
- A
<form>element containing atextarea(the message), an email input, usually a name input, and a submit button. - Common WordPress form plugins leave recognisable class names:
wpcf7-form(Contact Form 7),gform_wrapper(Gravity Forms),wpforms-form(WPForms). - Form builders often embed an
iframeor load a script that inserts the form, so you may see only an empty container in the raw HTML.
Forms that are not contact forms
| Form | Tell-tale signs | Use for outreach? |
|---|---|---|
| Search | One text input named q, s or search; role="search" | No |
| Newsletter signup | One email field, often in the footer | No |
| Login or account | A password field | No |
| Blog comments | Name, email, website and comment fields under a post | No |
| Booking or appointment | Date and time pickers, service selectors | No |
| Job application | File upload for a CV | No |
| Quote request | Project details, budget, postcode | Only if it is the site's only enquiry form, and be honest in the fields |
| General enquiry | Name, email, phone, message | Yes |
Rendered pages
If the raw HTML has a form container but no fields, load the page in a real browser engine and let its scripts run. Do not attempt to bypass anything that appears: if the page shows a CAPTCHA, a login wall or a block page, record that and move on. Google describes reCAPTCHA as protecting sites "from spam and abuse" by telling humans and bots apart; a CAPTCHA on a form is the owner's decision to keep automated submissions out, so those sites are for manual handling or for leaving out.
Step 5: handle multiple forms
Larger sites often have several forms. Choose in this order:
- General enquiry form on the main contact page.
- Department form that matches your message (for example "Suppliers" or "Partnerships").
- Quote form, only when it is the only enquiry route and you can fill it honestly.
Record all forms found, not just the chosen one, with their URLs and purpose. If a site has separate forms per branch, decide whether you are contacting the business as a whole (use the head office form) or a branch.
Step 6: record the outcome per site
| Outcome | Meaning | Next step |
|---|---|---|
| Form found | One clear contact form | Map fields; see the field table in the contact form outreach guide |
| Multiple forms | Several candidates | Choose by the order above |
| Email only | No form, a business address shown | Consider email instead; see the contact form outreach guide |
| CAPTCHA | Form protected by a challenge | Manual handling or skip; see the CAPTCHA section of the contact form outreach guide |
| Blocked | Access refused, rate limit or block page | Stop; do not retry automatically |
| No contact route | No form, no email | Try post or another channel |
| Site dead or parked | No live business site | Remove from the list |
Worked example (fictional)
| Site | Menu link | Sitemap | Form | Outcome |
|---|---|---|---|---|
| northfield-plumbing.example | "Contact us" to /contact-us/ | Not needed | Contact Form 7, name, email, phone, message | Form found |
| kite-studio.example | None | /sitemap.xml lists /get-in-touch | Script-inserted form, visible after rendering | Form found (rendered) |
| ashby-catering.example | "Contact" to /contact | Form with reCAPTCHA checkbox | CAPTCHA, manual handling | |
| oakroofing.example | None | None | /contact returns the homepage | No contact route, mailto: in footer |
How Map Extract helps
Map Extract's contact form submitter does this search for each website in your list. It finds contact pages from site links and sitemaps, reads the rendered form, maps your details into the visible fields (leaving hidden, password and file fields untouched), detects reCAPTCHA v2, v3 and hCaptcha and marks those sites for manual handling, and records an outcome for every site, including not found. Live submission is off until you enable it.
If you only want to find contact pages without submitting anything, the website data extractor prioritises contact, about and services pages during its crawl, reads sitemaps, respects robots.txt, falls back to a rendered browser for script-only sites, and records the contact page URL along with public business emails and phone numbers. Blocked, CAPTCHA-protected, parked and dead sites are recorded, not treated as data.
What it does not do: a found form does not mean the site will accept a submission, and the email permission check in Map Extract does not cover contact forms, so check your own suppression list before any run.
Public business and social results the app collects are uploaded automatically to Map Extract's servers while it is licensed and running; the privacy notice explains this.
Key takeaways
- Follow the site's links first, then the sitemap, then a very short list of common paths.
- Respect robots.txt and keep guessed requests to two or three per site.
- Confirm a contact form by its fields: message, email, name, submit.
- Set aside search, newsletter, login, comment, booking and job forms.
- Render script-built pages, but treat CAPTCHAs and blocks as a stop, not an obstacle.
- Record an outcome for every site so nothing is silently skipped or double counted.
Frequently asked questions
How do I find the contact page URL of a website?
Look for a Contact, Contact us or Get in touch link in the main menu and footer first. If there is none, check the sitemap, which robots.txt often lists on a Sitemap line, for URLs containing contact or enquiry. As a last resort, try a few common paths such as /contact, /contact-us and, on Shopify stores, /pages/contact.
How can I tell a contact form from other forms on a page?
A contact form usually has a message textarea plus name and email fields, and a submit button. A form with one email field is usually a newsletter signup, a single text box named q or s is a search form, and a form with a password field is a login. Comment forms on blog posts and booking or quote forms are for other purposes.
Why can't a scraper see the contact form on some sites?
Many forms are added by JavaScript after the page loads, or sit inside an iframe from a form builder. A simple HTTP fetch sees only the empty container. You need a rendered browser to load the page and run its scripts. Some sites also block automated visitors or protect the form with a CAPTCHA; record those cases rather than working around them.
Should I guess URLs like /contact-us in bulk?
Only a few, and only after checking links and the sitemap. Each guess is a request to someone else's server and most return a 404 page. Try two or three common paths per site at a polite pace, respect robots.txt, and stop if a site returns errors or rate limit responses. Links on the site are always better evidence than a guessed URL.
Sources
Written by the Map Extract editorial team. Found an error? Email [email protected] and we will check and correct it. How we research guides: editorial policy.