/ uses · personal · one page, your design, your url

a bio link that looks like you.

every link-in-bio service hands you the same page as everyone else, with their logo at the bottom and their name in your url.

the alternative used to be building it yourself, which is an afternoon of html and a hosting decision for what is, honestly, a list of links.

now you describe it — colors, order, the one thing at the top you actually want clicked — an agent writes the page, and htmlshare gives it a url. changing it later is another sentence, not another afternoon.

publish one now

free · one page · no templates

/ example

what it looks like.whatever you want it to.

there’s no template, no preset layout, no handful of themes to choose from. describe the page you want and your agent builds it. yours can look nothing like the example — that’s the point.

open the example

/ starting prompt

copy this.it asks before it builds.

there is nothing to fill in. paste it and your agent interviews you first — who you are, what you want clicked, where you are putting the link — then designs the page around those answers.

already have a design, a mockup, or a screenshot of something you like? bring it. the prompt asks for it up front and treats it as the direction rather than guessing at one.

starting prompt · 138 lines

Create a polished, custom link-in-bio page for me that will be published with HTMLShare.

Do not start building immediately. First, ask me a short set of questions so you have the information and creative direction you need.

DISCOVERY

Ask me about:

- Whether I already have a design, mockup, or concept from another tool that you should recreate or build from.
- Whether I have screenshots, websites, or other visual references that show styles I like.
- Who I am and how I want to be described.
- Who is likely to visit this page and what I want those visitors to do.
- The links I want to include and their priority.
- Whether there is anything I especially want visitors to notice, visit, buy, watch, read, or sign up for.
- How people should contact me, if applicable.
- Any photos, logos, icons, illustrations, or other assets I have available.
- Any additional visual preferences such as colors, typography, mood, personality, or things I specifically want to avoid.
- Where I plan to share this link, such as Instagram, TikTok, X, YouTube, LinkedIn, or multiple platforms, so tracking can be configured appropriately.

Keep the interview concise and conversational.

Ask only questions that will materially affect the finished page. If one of my answers makes another question unnecessary, skip it. If you need clarification about something important, ask rather than making an assumption.

Do not make me fill out a template or replace placeholder values.

If I provide an existing design or mockup, treat it as the primary visual direction unless I tell you otherwise.

If I provide screenshots, websites, or other references as inspiration, determine what qualities I like about them and use those qualities to create an original design rather than blindly copying them.

If I provide no visual direction, make appropriate design decisions based on what you learn about me, my audience, and my content.

DESIGN

Do not start from a predetermined link-in-bio template.

There is no required layout, set of blocks, button style, featured card, or visual structure.

Design the page specifically around my content and goals.

It does not need to look like a traditional stack of link buttons. Choose the hierarchy, typography, layout, imagery, components, and interactions that make the most sense.

Give more visual importance to the things I most want visitors to do instead of treating every link equally.

Design mobile-first. Assume most visitors will arrive from a social profile on their phone, while still making the page look polished on larger screens.

Make it:

- responsive
- accessible
- fast
- visually polished
- easy to scan
- easy to use with a thumb
- appropriate for the personality or brand I describe

Use semantic HTML, sufficient color contrast, visible keyboard focus states, appropriate alt text, large touch targets, and respect reduced-motion preferences.

Avoid unnecessary frameworks, dependencies, scripts, and heavy assets.

PAGE DETAILS

Treat this as a real public webpage, not a visual mockup.

Include the details expected from a polished production page, including where appropriate:

- descriptive page title
- meta description
- canonical URL
- Open Graph title
- Open Graph description
- Open Graph image
- Open Graph URL
- Open Graph type
- appropriate Twitter/X card metadata
- favicon
- relevant icon metadata
- theme color
- appropriate structured data when it genuinely applies

If you have the ability to create a custom favicon or social sharing / Open Graph image that fits the design, do so.

If an asset is needed that you cannot create, tell me what is needed rather than silently omitting it or substituting something inappropriate.

Do not invent identity details, URLs, claims, follower counts, testimonials, projects, credentials, images, or other facts I have not provided.

LINKS & TRACKING

Make sure every link works and goes to the intended destination.

Use clean destination URLs.

Based on where I tell you the page will be shared, determine whether UTM tracking would be useful.

If tracking would be useful, explain the proposed tracking convention briefly and confirm it with me before adding it.

Use meaningful and consistent UTM parameters rather than arbitrary values.

If the same HTMLShare page will be shared across several platforms, do not incorrectly attribute all traffic to a single platform. Recommend an appropriate approach based on how I intend to distribute the page.

Do not add tracking parameters where they are unnecessary or where they could interfere with the destination.

Use appropriate attributes for external links.

Before delivery, check for broken links, placeholder URLs, and malformed tracking parameters.

QUALITY CHECK

Before considering the page finished:

- Review it at common mobile and desktop sizes.
- Check that the visual hierarchy reflects my priorities.
- Check accessibility basics.
- Check metadata and social sharing tags.
- Check favicon and icon setup.
- Check every link.
- Check any UTM parameters.
- Check for placeholder or invented content.
- Check that images have appropriate dimensions and alt text.
- Check that the page does not require a build step or server.
- Check that there are no unnecessary dependencies.
- Remove unused or unnecessary code.
- Make sure the final result feels finished enough to use as my real public link-in-bio page.

DELIVERY

Produce the page as one self-contained HTML file wherever practical, with its CSS and JavaScript included.

Do not require a framework, build step, database, or server.

If something cannot reasonably be embedded in the HTML file, keep additional assets to a minimum and clearly identify them.

When the page is finished, publish it with HTMLShare if an HTMLShare integration is available.

After publishing, use the final HTMLShare URL for canonical and Open Graph URL metadata wherever appropriate. If necessary and supported, update the published artifact after the final URL is known so this metadata is correct.

If an HTMLShare integration is not available, save the finished HTML file and any required assets ready to upload to HTMLShare.

The finished result should feel like a custom personal website that happens to serve the purpose of a link-in-bio page — not a generic link-in-bio template.

show it what you like.: already have a design? use it. have screenshots of sites you like? send those. don’t know what you want? that’s fine too — let the agent ask questions and propose a direction.
tell it what matters most.: not every link needs to look the same. tell the agent what you want people to notice right now and let the design reflect that.
change anything by asking.: “make it more minimal.” “put my new project first.” “use this photo instead.” “the type feels too serious.” you don’t need to find the right setting or edit a block.
keep the same page as it changes.: your link-in-bio isn’t finished forever when you publish it. come back next week, tell your agent what’s changed, and update the page without starting over.

/ by agent

publishing it.connect it once.

every agent below talks to the same endpoint with the same api key, so setup is one connector and one header. the exact fields for claude.ai, claude code, claude desktop and chatgpt are on the docs page.

how to connect your agent

claude: paste the prompt and answer the questions in the same thread — changing your mind halfway ("actually put the newsletter first") lands before it has built anything. with an api key on the connector, claude publishes straight to the slug you picked and returns a siteId. there is no manage token to keep: the key authorizes every later edit, and the favicon and social image the prompt asks for go up alongside the page as assets.
chatgpt: the same connector and the same key work here, so chatgpt publishes the page itself rather than handing you a file to download and re-upload. without a key it still publishes, but anonymously — and an anonymous bio link is deleted after 7 days, which is the wrong shape for a url you have already put in a profile.
cursor: worth it if you like keeping the page in a repo: the file lives in the project and the same endpoint publishes from the editor, so the live url tracks the file instead of drifting from it. the setup fields are the ones on /docs — cursor just is not written up there yet.

/ why an account helps here

what changes when it’s yours.

custom url: your prefix and page slug give you a url that’s actually yours — something you can comfortably put in every profile, post, email signature, or qr code.
keep it around: anonymous shares expire after 7 days. your bio link shouldn’t. publishing from your account gives this page a permanent home.
stable updates: the page can change without the url changing. add a project, swap a link, change the design, or rewrite the whole thing — the link you already shared stays put.

what’s behind the link changes. the link doesn’t.

/ questions

the ones people actually ask.

how is this different from linktree or bio.link?: they give you a hosted page inside their product, with their branding and their url shape, edited through their form. this is a page you own the html of, on a url you choose, changed by describing the change. the trade is that nothing is pre-built for you — the agent writes it each time.
can i use my own domain?: not yet. pages live under htmlshare.net, and with an account you choose the path. custom domains are on the roadmap and not built.
how do i change a link later?: ask the agent for the change and republish to the same url with the manage token. the page updates in place; anywhere you pasted the link keeps working.
will it work on a phone?: that is most of what the prompt asks for — thumb-sized tap targets, real contrast, no heavy assets. check it at 375px before you publish it.

/ related