Turn a list of bare domains into full URLs in one paste. Set the protocol, add or remove www, append a path, or use a custom prefix — with live preview, lowercasing, trimming, and dedup.
Who it’s for
- SEOs turning a domain export into checkable URLs for an index or status check.
- Link builders converting a prospect domain list into homepage URLs to review.
- Analysts wrapping domains in a prefix (e.g. an archive or checker URL) in bulk.
- Anyone who has a column of domains but needs real, clickable URLs.
How it works
Paste your domains
Drop in bare domains or messy hosts — with or without protocol, www, or paths.
Set the URL shape
Choose protocol, www handling, an optional path, or a custom prefix. A live rule shows domain.com → your result.
Copy the URLs
The full URL list appears instantly, optionally deduplicated. Copy all or download as TXT.
Example: what goes in, what comes out
Rule: https + add www. Input → output:
| Domain | Generated URL |
|---|---|
| example.com | https://www.example.com |
| blog.example.org | https://www.blog.example.org |
| shop.example.co.uk/deals | https://www.shop.example.co.uk/deals |
Features
Protocol, www & path control
Prepend https or http, add or strip www, and append a path so every domain becomes exactly the URL shape you need.
Custom prefix support
Use an advanced custom prefix (for example a web.archive.org wrapper) that overrides protocol and www when you need something specific.
Live preview & dedup
A rule line previews domain.com → result as you tweak options, and you can lowercase, trim, and deduplicate the output.
Which URL form actually resolves?
A bare domain isn’t a checkable URL — and the form you build changes what a checker sees. Pick the wrong shape and every “result” is really a redirect:
- Protocol — most sites force
https; generatinghttp://just adds a 301 hop to every check. - www vs non-www — a site resolves canonically to one. Build the other and you’re checking a redirect, not the page.
- Trailing slash / path — append a path only if you actually want that page, not the homepage.
Match the form to how the site really resolves and your downstream index check or status check reads the destination directly — no redirect noise, cleaner data.
Limitations & privacy
- It builds URLs from the rule you set; it doesn’t detect each site’s true canonical form, so choose the protocol/www that matches your targets.
- A custom prefix is used verbatim and overrides protocol/www — double-check it before running a large batch.
- Generation runs live in your browser; your list isn’t uploaded.
FAQ
How do I convert domains to full URLs?
Paste your domains, choose a protocol, www handling, and optional path, and IndexVero builds a full URL for each line, with a live preview of the rule.
Can I add www or a path to every domain?
Yes. You can add or remove www and append a path such as /blog to every domain in the list in one run.
What is the custom prefix for?
The custom prefix is an advanced override used verbatim in front of each host — handy for wrappers like an archive URL — and it takes priority over the protocol and www settings.
Does it deduplicate the output?
Yes. Enable deduplicate output to collapse identical generated URLs, and you can also lowercase, trim, and drop empty lines.