Autocomplete Checker
Paste your page HTML and find missing HTML autocomplete tokens, invalid values and off switches on identity fields.
What this tool gives you
Check autocomplete
Paste your page HTML. Analysis runs locally in your browser — nothing is sent anywhere.
Email, name, tel and address fields need a catalog token such as email or given-name — not fname or off.
What this checker looks for
WCAG 1.3.5 fails when the purpose of a personal-data field is visible but never programmatically named.
Catalog tokens
Use email, given-name, tel, postal-code — not fname, phone or custom strings.
Input purpose
Name, email, tel and address fields need a matching autocomplete token.
Do not disable
autocomplete=off on identity fields blocks browsers and AT.
Prefixes ok
shipping, billing, home, work and section-* prefixes stay valid.
Checkout forms
Card and address tokens let engines quote a recoverable lead form.
0–100 score
Track autocomplete hygiene across templates, not just the homepage.
How to name an input purpose
Three rules cover almost every silent lead form in the wild.
Use a catalog token
email, given-name, tel, postal-code. fname and phone are ignored.
Match the field
type=email still needs autocomplete=email so AT can name the purpose.
Do not set off
autocomplete=off on identity fields blocks browsers and password managers.
Why answer engines care about autocomplete
Named input purposes are a cheap-to-parse signal that the form can autofill, not a custom nickname trap.
| Signal | What engines infer | Why it helps |
|---|---|---|
| autocomplete=email | The field collects an email. | Extractors can quote Email, not a custom name=mail. |
| given-name / family-name | The form splits identity. | Password managers fill faster; lower bounce. |
| No off on identity | Browsers may autofill. | AI-referred checkout visits complete more often. |
| WCAG 1.3.5 pass | Input purpose is programmatically determined. | Citable, trustworthy pages get quoted more often. |
| Catalog tokens | The page uses the platform API. | email/tel beat custom fname/phone flags. |
Related GEO pages
Autocomplete pairs with required fields and labels so identity forms can complete.
Aria Required Checker
Find bad aria-required tokens, asterisk-only fields and missing HTML required.
Form Label Checker
Find form fields missing labels, aria names or for-targets.
Aria Invalid Checker
Find form fields with bad aria-invalid tokens or unwired error text.
Tools Lab
More generators, calculators and GEO workflows.
Autocomplete FAQs
Which autocomplete tokens are valid?
The HTML catalog: email, given-name, family-name, tel, postal-code, street-address, cc-number and similar. Custom strings like fname or phone are ignored.
Is autocomplete=off a fail?
It warns on identity fields. Browsers and AT cannot fill or name the purpose. Use a catalog token instead unless the field is a one-time code you must not store.
Does type=email count without autocomplete?
No. type=email is a format hint. WCAG 1.3.5 wants autocomplete=email so password managers and AT can identify the purpose across languages.