HTML Element: Reference and Examples

You might see <geolocation> Element reference while reading someone else’s HTML, or need it while building a page of your own. Instead of memorizing a definition, look at a working example and see when the element makes sense.

The Idea in Plain English

An experimental interface for user-approved location access. Support is limited; do not rely on it for a public site.

For a reference page, pay attention to where the element is allowed, whether it needs a closing tag, and what other elements it can contain.

A Working Example

Read the sample once before copying it. Notice the element names and attribute values, then compare them with the explanation below.

<form action="/nearby" method="get">
    <label for="city">Enter a city</label>
    <input id="city" name="city">
    <button type="submit">Search</button>
</form>

What Each Part Does

The form collects and submits named fields to the destination specified by action.
The label tells visitors and assistive tools what a control is for.
The input creates a field; its type changes the editing controls and the name identifies submitted data.
action sets the URL that receives a submitted form.
method chooses GET or POST for form submission.
for connects a visible label to the control with the same ID.

The fallback asks for a city rather than requiring an experimental location UI.

Try It Yourself

Try replacing the example content with your own while keeping the valid HTML structure.

Common Beginner Mistakes

Requesting location without consent or hiding a usable manual alternative.
Changing several parts of the example at once, making it difficult to see which part caused a different result.
Choosing a tag only because its default appearance looks right, without checking whether it describes the content correctly.

Key Takeaways

An experimental interface for user-approved location access. Support is limited; do not rely on it for a public site.
The fallback asks for a city rather than requiring an experimental location UI.
Test the markup in a browser, and check accessibility and real-world behavior where relevant.