# Tapmy.link

> Every link, social and product on one fast page at yourname.tapmy.link. Ten templates, import from Linktree or any other service, as many sites as you need. Free.

Tapmy.link is a free link-in-bio service. Each page lives on its own subdomain,
`yourname.tapmy.link`, rather than as a path under the service's domain. One account
holds any number of such pages, each with its own address, template, links and statistics.

## What it does

- Ten templates, switchable at any time without losing links, photos or the address.
- Blocks: links with a note, a badge or a card image; social rows with brand marks for about
  thirty-five platforms; messenger buttons for Telegram, WhatsApp and Viber; embeds for
  YouTube, Spotify, Apple Music, SoundCloud and TikTok; text headings. Up to eighty per page.
- Import: paste the URL of a public link page on any service and pick which links to copy,
  or give an Instagram handle to fill in the photo, name and bio.
- Pages are rendered on the server, ship almost no JavaScript and work with scripts disabled,
  because most visitors arrive inside the Instagram or TikTok in-app browser on mobile data.
- Any link can carry a short path on the same subdomain — yourname.tapmy.link/shop — and
  per-platform destinations, so an iPhone goes to the App Store entry and an Android phone
  to Google Play. A page can also append UTM tags to its outgoing links.
- Statistics are page views and unique visitors over 7 and 30 days, plus taps on short links,
  all counted server-side with no cookie. A link that still points straight at its destination
  is not counted at all. Public pages set no cookies, so there is no consent banner.
- Links marked 18+ pass an age check and never appear in the page source.
- The interface exists in twenty languages; each page carries its own content language.

## What it does not do

No payments, store or checkout. No email marketing, booking system or media kit. No custom
domains, A/B testing or link scheduling. No mobile apps. Sign-in is e-mail and password, or an
API key for programs.
Statistics stop at a tap count: no referrer report per link, no funnels, no conversion
tracking. Stating these plainly is deliberate: the comparison pages below say the same thing.

## Price

Free, with no paid tier. One small promo block at the bottom of public pages funds the service.

## For agents

A program can register, build and publish a page for a person in one HTTP call, then hand over
a claim link that makes the account theirs. No browser, no account up front. Start at
[https://tapmy.link/documentation/agents.md](https://tapmy.link/documentation/agents.md) — a hub in Markdown linking every page below.
Also: [OpenAPI](https://tapmy.link/openapi.json), [MCP server](https://tapmy.link/mcp), [skill file](https://tapmy.link/skill.md),
[the whole documentation in one file](https://tapmy.link/llms-full.txt). Every public page is readable as Markdown at
`https://<name>.tapmy.link/page.md`.

- [Overview](https://tapmy.link/documentation/agents/overview.md): What Tapmy.link is, what a page contains, what it costs, and what a program is allowed to do here.
- [Quickstart: a page in three calls](https://tapmy.link/documentation/agents/quickstart.md): Check a name, create the page, verify it. Copy-paste curl for each step, with the exact response shape.
- [When you cannot call the API](https://tapmy.link/documentation/agents/no-network.md): What to do if you can only GET, or have no network at all: compose the page JSON and hand the person a one-click link to /new that creates it in their browser.
- [Accounts: provisional and claimed](https://tapmy.link/documentation/agents/accounts.md): The two kinds of account a program can create, what a claim link does, and what happens to pages nobody claims.
- [Authentication and API keys](https://tapmy.link/documentation/agents/authentication.md): Bearer keys: where they come from, how to send them, what they can and cannot do, how the owner revokes them.
- [The page model](https://tapmy.link/documentation/agents/page-model.md): Every field on a page, its type and limits, and which endpoint sets it.
- [Blocks reference](https://tapmy.link/documentation/agents/blocks.md): The six block types with the minimal JSON for each, every optional field, and what the templates do with them.
- [Social platforms](https://tapmy.link/documentation/agents/platforms.md): The 35 platform ids accepted in social and socialRow blocks, with the URL shape each expects. Generated from the code.
- [Templates](https://tapmy.link/documentation/agents/templates.md): The ten templates, what each looks like, and which kind of page it suits. Switching never loses content.
- [Images](https://tapmy.link/documentation/agents/images.md): How to put a photo on a page when all you have is a URL: the upload route, storage keys, kinds and size caps.
- [Short links and app links](https://tapmy.link/documentation/agents/short-links.md): Give a link a path on the owner's subdomain, count taps on it, and send iPhone and Android to different stores.
- [Adult links (18+)](https://tapmy.link/documentation/agents/adult-links.md): How links to OnlyFans, Fansly and similar are handled, what a program must set, and what never appears in the page.
- [Languages](https://tapmy.link/documentation/agents/languages.md): The twenty interface locales, how the account language and the page language differ, and which code to send where.
- [Import from another service](https://tapmy.link/documentation/agents/import.md): Copy the links from a Linktree, Taplink, Beacons or any public link page, or the photo, name and bio from Instagram.
- [Verify the result](https://tapmy.link/documentation/agents/verify.md): Read a public page back as Markdown, check what a visitor will see, and confirm the page is actually published.
- [Statistics](https://tapmy.link/documentation/agents/statistics.md): Views, unique visitors and taps for 7 and 30 days, with a daily series — what an agent can report back to its owner.
- [Handing over to the owner](https://tapmy.link/documentation/agents/handover.md): What to tell the person after the page exists: the two links, what the claim link does, and a message you can send verbatim.
- [Etiquette](https://tapmy.link/documentation/agents/etiquette.md): What a program should and should not do with a page it did not pay for and does not own.
- [Endpoints](https://tapmy.link/documentation/agents/endpoints.md): Every HTTP endpoint a program can call, with auth, purpose and a link to the page that explains it. The machine-readable form is /openapi.json.
- [Errors and hints](https://tapmy.link/documentation/agents/errors.md): The error envelope, every code the API can return, and the hint that accompanies each. Generated from the code.
- [Rate limits and housekeeping](https://tapmy.link/documentation/agents/rate-limits.md): Every limit a program can hit, how it is signalled, and the sweep that removes pages nobody claimed or visited.
- [MCP server](https://tapmy.link/documentation/agents/mcp.md): The Model Context Protocol endpoint, its tools, how to connect from Claude, Cursor and other clients, and the one rule about keys.
- [Skill file](https://tapmy.link/documentation/agents/skill.md): A ready procedure for coding agents (Claude Code, Codex, Cursor): when to use Tapmy, the steps, the guardrails.
- [Changelog](https://tapmy.link/documentation/agents/changelog.md): Dated changes to the agent-facing API, the MCP server and this documentation.
- [Recipe: a musician](https://tapmy.link/documentation/agents/recipe-musician.md): A complete request body for a musician: the newest release first, one row of streaming marks, dates, merch, press.
- [Recipe: a restaurant or café](https://tapmy.link/documentation/agents/recipe-restaurant.md): A complete request body for a place: reserve first, then menu, directions, hours, delivery, and a chat button.
- [Recipe: a photographer](https://tapmy.link/documentation/agents/recipe-photographer.md): A complete request body for a photographer: portfolio first, booking, the current offer, prints.
- [Recipe: a coach or consultant](https://tapmy.link/documentation/agents/recipe-coach.md): A complete request body for a coach: one clear offer, a booking link, proof, a way to talk.
- [Recipe: a small shop](https://tapmy.link/documentation/agents/recipe-shop.md): A complete request body for a shop: the current drop, categories as cards, delivery info, support chat.
- [Recipe: a launch](https://tapmy.link/documentation/agents/recipe-launch.md): A complete request body for a product or book launch: one page, one action, a countdown of steps, everything dated.

## Main pages

- [Home](https://tapmy.link): the product, ten template previews, and the import field.
- [Templates](https://tapmy.link/templates): all ten templates rendered with demo content.
- [For AI agents](https://tapmy.link/for-agents): for people — how to have an assistant build the page for you.
- [Blog](https://tapmy.link/blog): 73 articles on link-in-bio pages, in English, Russian and Ukrainian.
- [Comparisons](https://tapmy.link/vs): honest, dated comparisons with other services.
- [Privacy](https://tapmy.link/legal/privacy), [Terms](https://tapmy.link/legal/terms), [Report a page](https://tapmy.link/legal/report).

## Comparisons

- [Tapmy.link vs Linktree](https://tapmy.link/vs/linktree): The difference is shape and purpose, not quality. We are a subdomain and a page of links; Linktree is a path on a famous domain and a platform around it.
- [Tapmy.link vs Taplink](https://tapmy.link/vs/taplink): Taplink is built so a small business can take an order without the visitor leaving. Tapmy.link is built so a page of links loads fast at your own address.
- [Tapmy.link vs Beacons](https://tapmy.link/vs/beacons): Beacons sells a business, not a page: a storefront, a media kit and email campaigns, with the link page as the front door. Tapmy.link makes only the page, on your own subdomain, free.
- [Tapmy.link vs Bio.link](https://tapmy.link/vs/bio-link): Bio.link and Tapmy.link want the same thing: a link page that loads fast and costs nothing. What differs is the address, how many pages one account gets, and whether anything is left to upgrade to.
- [Tapmy.link vs Lnk.Bio](https://tapmy.link/vs/lnk-bio): Lnk.Bio is cheap, simple and unlimited, and you can pay once instead of subscribing. Tapmy.link is free with no paid tier, and gives you a subdomain rather than a path.

## Articles

- [A short link that carries your name](https://tapmy.link/blog/short-links-on-your-page): Give any link a short path on your own address — yourname.tapmy.link/shop — to print on a card, say out loud on a podcast, and count taps without a single cookie.
- [One button, two app stores](https://tapmy.link/blog/app-store-links): An iPhone should land in the App Store and an Android phone in Google Play, from the same button on your page. How per-platform destinations work and when not to use them.
- [Blocks that appear and disappear on their own](https://tapmy.link/blog/scheduled-blocks): A sale that ends, a date that passes, a launch that starts at midnight: give a block a window and the page keeps itself current without you opening the editor.
- [Campaign tags: seeing your page in someone else’s analytics](https://tapmy.link/blog/utm-tags-on-your-links): One switch appends utm_source, utm_medium and utm_campaign to every outgoing link, so your shop or your booking system can tell your bio page from everything else you post.
- [A button that calls you, and one that writes to you](https://tapmy.link/blog/phone-and-email-buttons): Not every visitor wants a chat app. Phone and e-mail blocks put a number or an address on your page, and a tap opens the dialler or a new message.
- [Where a photo gets cropped, and who decides](https://tapmy.link/blog/photo-crop-anchor): A round avatar, a full-bleed background and a card image all cut your picture differently. Drag one dot and the part that matters stays in the frame everywhere.
- [A background photo that does not eat your text](https://tapmy.link/blog/background-images): A picture behind a link page is the fastest way to make it yours and the fastest way to make it unreadable. What to choose, how the overlay works, and when to skip it.
- [When to run a second page, and when not to](https://tapmy.link/blog/more-than-one-page): One account can hold as many addresses as you need — you, the studio, the side project. The switch is easy; the reason to use it is the part worth thinking about.
- [The featured link: one card that does the work](https://tapmy.link/blog/featured-links): A featured block turns a row into a full-width card with an image. Used once it doubles taps on the thing that matters; used four times it is just a longer page.
- [Notes and badges: twenty characters that answer a question](https://tapmy.link/blog/notes-and-badges): A second line under a label and a small tag on the button are the cheapest way to remove doubt before a tap — and the easiest two fields to fill with noise.
- [One row of icons, or a row per platform?](https://tapmy.link/blog/social-row-or-rows): Thirty-five platforms, two ways to show them: a compact strip of brand marks, or a full-width row with a name and a follower count. When each one is right.
- [How the 18+ gate works, and why it exists](https://tapmy.link/blog/how-the-age-gate-works): Adult links are supported and never appear in your page source. Three steps, one separate domain, and a reason that has more to do with your address than with morals.
- [Taking your data out, and taking it away](https://tapmy.link/blog/export-and-delete-your-data): One button downloads everything we hold about you as JSON. Another deletes the account for real. What is in the file, what deletion removes, and what survives on purpose.
- [Why your page opens before the spinner appears](https://tapmy.link/blog/why-the-page-opens-fast): Most visitors arrive inside the Instagram or TikTok browser on mobile data. Everything about how these pages are built follows from that one fact.
- [Every page is also a text file](https://tapmy.link/blog/reading-a-page-as-markdown): Add page.md to any address and the page comes back as Markdown: the blocks, the destinations, the template. It is how a program checks its own work without a screenshot.
- [When your assistant has no internet: the one-click link](https://tapmy.link/blog/one-click-create-link): Some chat assistants can read a page but cannot send a request. They can still build your page: the JSON goes into a link, and you create it in your browser with one tap.
- [Rate limits, retries and the one header that makes them safe](https://tapmy.link/blog/rate-limits-and-retries): What a program may do per hour and per day on a free service, how a 429 tells you when to come back, and why an idempotency key matters more than a retry loop.
- [Errors written to be read by a model](https://tapmy.link/blog/reading-api-errors): Every failure comes back as a code, a hint in plain English and sometimes a suggestion. Why an API for agents needs all three, and how to branch on them.
- [Forty pages from one spreadsheet](https://tapmy.link/blog/pages-from-a-spreadsheet): A market with forty stalls, a festival with thirty acts, a school with twenty teachers: how one agent turns a table of names and links into a page each, and hands every owner the keys.
- [Building link pages for clients, with an agent doing the typing](https://tapmy.link/blog/agency-pages-with-agents): If you make pages for other people, the work is discovery and taste, not form-filling. What to automate, what never to, and who should own the account at the end.
- [The schema is generated from the code that validates](https://tapmy.link/blog/openapi-and-typed-clients): Our OpenAPI document is built from the same validators the server runs, so a generated client cannot be wrong about a field the server will reject. What that buys you.
- [Setting this up in Cursor, Claude Code and the rest](https://tapmy.link/blog/cursor-and-other-editors): Two ways to give a coding agent access: a skill file it reads as a procedure, or an MCP server it calls as tools. What each client needs, in one page.
- [A custom GPT that makes link pages](https://tapmy.link/blog/a-custom-gpt-that-makes-pages): Point a custom GPT action at our OpenAPI document and it can register an address, build a page and hand back a claim link. What to put in the instructions so it behaves.
- [A page that updates itself from your calendar](https://tapmy.link/blog/pages-that-update-themselves): Dates, releases, opening hours: the things that change weekly are exactly the things nobody remembers to edit. An agent with a key and a source can keep them true.
- [The handover is part of the job](https://tapmy.link/blog/handing-a-page-to-its-owner): A page an agent built and never handed over is a page with no owner. What to send, in what words, and how to tell when the person has actually taken it.
- [Putting a photo on a page when all you have is a URL](https://tapmy.link/blog/images-for-agents): Image fields accept storage keys, never addresses. Why that rule exists, how upload-by-URL works around it, and what happens to the bytes on the way through.
- [How an agent should choose a template](https://tapmy.link/blog/how-an-agent-picks-a-template): Ten templates, one decision, and a model with no eyes. The rules that make a machine pick sensibly, and the reason switching later costs nothing.
- [Six block types, on one page](https://tapmy.link/blog/the-block-json-cheatsheet): Everything a page can contain, with the fields each block needs and the fields it merely allows — the short version of the reference, for whoever is writing the JSON.
- [Testing an integration without leaving litter](https://tapmy.link/blog/testing-your-tapmy-integration): A dry run that creates nothing, a throwaway page you delete, and the sweep that catches what you forgot. How to develop against a live service responsibly.
- [What it takes to be usable by a program](https://tapmy.link/blog/built-to-be-used-by-programs): Machine-readable documentation, errors with hints, a text view of every page, no captcha and no paywall: the decisions that let an agent finish a job here without a human in the loop.
- [Create your link page from ChatGPT](https://tapmy.link/blog/page-from-chatgpt): One prompt, a few answers, and ChatGPT registers your address on tapmy.link, builds the page and hands you a link to take it over. What happens at each step.
- [Create your link page from Claude](https://tapmy.link/blog/page-from-claude): Claude can build your tapmy.link page in a chat, in Claude Desktop through MCP, or from the terminal with Claude Code. Which one to pick and what each needs.
- [Let Claude Code or Cursor set up your page](https://tapmy.link/blog/claude-code-builds-your-page): A skill file teaches a coding agent the whole procedure: ask, validate, create, verify, hand over. How to install it, what it does, and how to keep the agent maintaining the page.
- [What an assistant can and cannot do on your page](https://tapmy.link/blog/what-an-assistant-can-do): The exact boundaries of an agent working on a tapmy.link page: what the API allows, what needs a person, and what no key can reach. Written so you can decide how much to hand over.
- [The claim link: how you take over a page an agent built](https://tapmy.link/blog/the-claim-link): An assistant can build a page without your e-mail. The claim link is how the account becomes yours afterwards — what it is, how long it lasts, and what happens if nobody opens it.
- [Ten prompts that get a good page out of an assistant](https://tapmy.link/blog/ten-prompts-for-a-good-page): The page an assistant builds is only as good as what you tell it. Ten short prompts for the first build and the changes after it, and the one rule behind all of them.
- [API keys: giving an assistant access safely](https://tapmy.link/blog/api-keys-for-assistants): What a Tapmy API key is, where to make one, what it can and cannot do, how to hand it to Claude Code or a script, and when to revoke it.
- [Keep your page fresh with a weekly agent check](https://tapmy.link/blog/weekly-agent-checkup): A page goes stale one dead link at a time. Give an assistant the key and one standing instruction, and the monthly checkup becomes a weekly one you never do yourself.
- [MCP, explained for people who make pages, not software](https://tapmy.link/blog/mcp-explained-for-creators): The Model Context Protocol is how an assistant gets buttons for a service instead of reading its manual. What that means for a link page, and the one setting you need.
- [Agent-built pages and privacy: what we store, what we do not](https://tapmy.link/blog/agent-built-pages-and-privacy): When a program creates a page, what ends up in our database, what the program learns about you, what your visitors see, and what disappears if nobody claims the page.
- [Your link in bio opens inside Instagram, not in Chrome](https://tapmy.link/blog/link-in-bio-inside-instagram): The in-app browser is a stripped-down WebView on a mobile connection. Here is what it breaks on a link-in-bio page, and how to build one that survives it.
- [A subdomain or a folder: what changes when your name comes first](https://tapmy.link/blog/subdomain-or-folder): name.service.com and service.com/name look similar and behave very differently — for how the address reads, how it is shared, and what happens if you ever leave.
- [Marking 18+ links so the page stays safe for everyone](https://tapmy.link/blog/labelling-adult-links): An age gate that only warns the visitor is theatre. Here is what an adult link on a link-in-bio page has to do to be honest, compliant and safe for the domain.
- [What to put on your page in the first week](https://tapmy.link/blog/first-week-of-a-link-page): A practical starting structure for a new link page: one thing at the top, three to six links, socials, and nothing else until you have seen a week of traffic.
- [How many links belong on a bio page](https://tapmy.link/blog/how-many-links): What happens to attention as a link list grows, when grouping beats adding, when a grid beats a list, and a rule of thumb you can apply to your own page today.
- [Setting the link in your Instagram bio](https://tapmy.link/blog/instagram-bio-link): Where the link field lives, how many links fit there, what to write above it, and why a tap opens Instagram’s own browser instead of Chrome or Safari.
- [The TikTok bio link and its rules](https://tapmy.link/blog/tiktok-bio-link): TikTok gates the clickable bio link behind account conditions that keep changing. What to do before you qualify, and how to build a page its browser can open.
- [Moving to a new link page without losing traffic](https://tapmy.link/blog/moving-off-linktree): What breaks when you change link-in-bio services, the order to swap addresses in, what transfers and what stays behind, and how long the old tail lasts.
- [Where a QR code to your page earns its place](https://tapmy.link/blog/qr-code-for-your-page): When a QR code beats a typed address and when it is decoration, plus size, quiet zone and contrast rules, and the checks to run before anything is printed.
- [What statistics without cookies can tell you](https://tapmy.link/blog/cookieless-statistics): A server-side count sees that a request arrived, roughly from where, on what kind of device. It does not see who you are, and a page view is never a click.
- [Preparing images so a bio page stays fast](https://tapmy.link/blog/images-that-load-fast): Almost all the weight of a link page is pictures. Resizing, re-encoding, a little blur and stripped EXIF do more for speed than any other change you can make.
- [A link page for a business people walk into](https://tapmy.link/blog/link-page-for-local-business): A barber shop, a café or a clinic needs a different page from a creator. Contact and directions come first; here is what belongs under them, and in what order.
- [Choosing the name people will type](https://tapmy.link/blog/choosing-your-address): Your address gets read aloud, written on a card and typed from memory. What makes a name survive all three, and what changing it later actually costs you.
- [Writing labels people actually tap](https://tapmy.link/blog/writing-link-labels): Microcopy for the link row: name the destination instead of the action, use the note line for prices and dates, and keep a badge rare enough to mean something.
- [The one line under your name](https://tapmy.link/blog/bio-line-that-works): What a bio line is for, why concrete nouns outlive adjectives about yourself, and how to write a line that still reads true when a search result cuts it short.
- [A link page for a musician](https://tapmy.link/blog/page-for-musicians): Structure a page around releases: the newest one as a card on top, streaming as a single row of icons, dates and merch below, and press material for writers.
- [A link page for a photographer](https://tapmy.link/blog/page-for-photographers): How to build a bio page that sends people to the portfolio instead of replacing it: three entry points, card images that show the work, and a starting price.
- [A link page for a café or restaurant](https://tapmy.link/blog/page-for-restaurants): The menu and the way in come first, delivery services get named rows, hours stay as text, and the seasonal offer is hidden rather than deleted when it ends.
- [A link page for a coach or consultant](https://tapmy.link/blog/page-for-coaches): A coaching bio page: say what you do and for whom, give one first step instead of five, keep the proof checkable, and put something free before the paid work.
- [When a link page is enough, and when it is not](https://tapmy.link/blog/link-page-vs-website): A link page is a junction, not a destination. Here is the honest line between the jobs it does well and the ones that really do need a site behind them.
- [The ten-minute checkup your page needs once a month](https://tapmy.link/blog/monthly-page-checkup): A short monthly routine for a link page: open it on a phone, tap every link, check what sits at the top, hide what is out of season, read the numbers honestly.
- [Why links die, and how to catch it before your visitors do](https://tapmy.link/blog/broken-links): Items sell out, events end, addresses move, handles change hands. Links break quietly, nobody reports them, and the fix is a habit rather than a tool.
- [Telegram, WhatsApp, Viber: which to offer](https://tapmy.link/blog/messenger-buttons): How to pick the messengers your audience already uses, why two buttons beat four, which link forms survive in-app browsers, and what to write on the button.
- [A player on the page, or a link to it](https://tapmy.link/blog/embeds-or-links): What an embedded player costs in weight, speed and privacy, what it buys in convenience, and a rule of thumb for deciding block by block on a bio page.
- [Colours that stay readable](https://tapmy.link/blog/colour-and-contrast): How to spend an accent colour, keep text legible over a photograph, judge contrast without jargon, and avoid the brand colours that fail as backgrounds.
- [Choosing a template that matches what you post](https://tapmy.link/blog/choosing-a-template): How to pick a template by the content you actually have, when a dark one works against you, why the newest is not the default, and why switching costs nothing.
- [A grid of cards or a list of rows](https://tapmy.link/blog/grid-or-list): When a grid of cards helps and when it turns a page into wallpaper, why a list wins as soon as links need words, and a three-second test that settles it.
- [Choosing the photo at the top of your page](https://tapmy.link/blog/profile-photo): The picture at the top is recognition, not art: what reads at eighty pixels, when a logo fails, why consistency beats quality, and checks before you upload.
- [When your audience reads two languages](https://tapmy.link/blog/two-language-audience): Three honest ways to handle a bilingual audience on a link page, why doubling every label backfires, and which few lines actually need translating at all.
- [What to leave off a link page](https://tapmy.link/blog/what-not-to-put-on-a-link-page): The links, blocks and details worth deleting from a bio page: dead destinations, loops back to the profile, expired notices and data you never meant to publish.
- [A page for a launch or an event](https://tapmy.link/blog/page-for-a-launch): How a link page works before, during and after a launch: which link belongs at the top, where the date goes, what to hide, and the checks to run the day before.
- [What a public page reveals without you meaning to](https://tapmy.link/blog/privacy-on-a-public-page): Metadata in photographs, an address that suits one page and not another, phone numbers, share previews and working names — what to check before a page is live.
- [Saying your address out loud and printing it](https://tapmy.link/blog/sharing-your-address-offline): The telephone test, how an address reads on a card, a van and a shop window, the case question, when a QR code earns its space, and what print cannot undo.

## Languages

The interface is available in 20 languages; English lives at the root and the
others under a code, for example https://tapmy.link/ru. Long-form content — the blog and
the comparisons — exists in 3 languages only (en, ru, uk),
because twenty machine translations of one article would be near-duplicates of each other.

## Notes for whoever is reading this

- Facts about other services on the comparison pages carry the date they were checked. Prices
  are quoted only where we verified them ourselves; everything else points at the other
  service's own pricing page, because a price copied into prose goes stale into a false claim.
- User pages live on subdomains and are not listed here. Each one serves its own robots.txt.