Sharing your map: subdomains, embeds, and direct links explained

A map you can’t hand to somebody is a map nobody sees. There are three reasonable ways to put an interactive map in front of an audience — a public subdomain, an embedded iframe inside an existing site, or a direct link you paste into a chat. They’re not interchangeable, and picking the wrong one for the wrong audience is the difference between a map that catches on and one that quietly dies after launch day.

The three options at a glance

• Public subdomain — your map lives at yourname.turf-map.io (or your own domain) as a standalone site. This is the canonical home; everything else points back here.
• Embedded iframe — the map is rendered inside a page on a site you already control. The viewer never leaves your site, but the map is fully interactive.
• Direct link — the same URL as the subdomain, pasted into Discord, a tweet, or wherever your audience lives.

The subdomain is the source of truth

The mistake we see most often is treating the embed and the subdomain as independent things, then slowly letting them drift. That ends with two versions of the map, two configs, two places people can report bugs about, and a maintenance tax that nobody signed up for.

Treat the subdomain as the single source of truth. The embed is just a window into it. The direct link is just a shortcut to it. Every change you make should be made on the subdomain, and propagate to the others automatically — which is how the system is designed to work, but only if you commit to using it that way.

When to choose the subdomain only

• You don’t already run a website and don’t plan to.
• The map is the destination — there’s no surrounding content to wrap it in.
• You want unambiguous link previews on Discord/Twitter/Slack.
• Search-engine discovery matters: the subdomain is the page Google indexes.

When to add an embed on top

• You already run a community site, server hub, or wiki and the map fits naturally into a page that already has visitors.
• You want the map surrounded by context (a paragraph, a table, navigation links) without rebuilding that context inside the map itself.
• You want analytics rolled up alongside the rest of your site.

Pick a subdomain you won’t outgrow

Subdomains are easy to set up and painful to migrate. Search engines remember the old URL. Discord link previews cache the old URL. Anyone who bookmarked the map last year is on the old URL. Renaming is doable, but it’s a real cost; it’s worth getting it right the first time.

Three rules of thumb:

• Avoid year numbers. turfmap2026 ages badly the moment 2027 starts.
• Avoid platform names. If you ever migrate to a different host, your subdomain tells the world about a tool you no longer use.
• Keep it short. Long subdomains get truncated in link previews and look fragile.

Make the link preview do the work

When somebody pastes your map into Discord, Slack, or a tweet, the platform fetches a snapshot of the page and renders a card. That card is your first impression — sometimes your only impression. A map with a strong preview gets clicked. A map with a generic preview gets scrolled past.

Three things to check before you start sharing:

• Title. Should describe the map, not the tool. “Northside Territory Map” reads better than “Map · turf-map.io”.
• Description. One sentence, no marketing voice. What it shows, who it’s for.
• Image. A cropped, recognisable view of the map itself, with the name baked in if possible. Tool logos are forgettable; a real map is not.

Custom domains: when they’re worth it

A custom domain (maps.yoursite.com) is worth the small setup cost when:

• You already own the surrounding domain and have an audience that recognises it.
• You want analytics consolidated under one domain.
• You want the option to migrate the map between platforms in the future without breaking links.

They’re overkill if you’re just looking to share with one community and don’t plan to grow beyond it. The default subdomain works fine for that case and removes a moving part.

Embedding cleanly inside an existing page

Three rules for embeds that don’t feel like embeds:

• Width: 100% of the container, not a fixed pixel value. Fixed widths break on phones the moment your design changes.
• Height: at least 600px on desktop, 480px on mobile. Smaller and the map feels cramped; people don’t bother panning.
• No surrounding border or shadow. The map already has its own visual frame. Adding a second one inside your design language fights with it.

The boring win: pick one channel and pin it

The single biggest distribution mistake is sharing the map link in a busy channel one time and never again. The link scrolls off the screen and the map effectively disappears. Pick one channel — the welcome channel, the announcements, a sticky thread — and pin the link there with a one-line description. That single pin will out-perform every casual share you ever post.