Questions people ask before they build one

Upload the PDF and let a tool draft the page from it, then fix the ordering yourself. Your resume already contains the work history, the projects you decided were worth mentioning and a description of yourself that survived a real job application, which is the expensive part of a personal site. What is left is mostly translation.

The translation is not a copy and paste. A resume is skimmed in seconds so it is compressed to shorthand; a site is opened by someone who has already decided you are worth looking up, so density should drop and specificity should rise. A few things should not make the trip at all: your postal address is a resume convention that becomes a privacy problem on a public URL, and skill bar charts claiming you are 87% good at something are unfalsifiable.

DebutPage does the first pass automatically. It reads the PDF, writes the connective copy and picks a layout, which takes about two minutes rather than a weekend, and you then adjust it by describing what you want in plain language.

No. Publishing on DebutPage is free on a yourname.debutpage.com subdomain, and free hosting for a personal site is normal across the whole category rather than a trick.

What free costs you is usually one of four things: your URL is a subdomain of the host, the host puts a badge on your page, some capability is held back for paid plans, or your time is the payment because you are assembling the site yourself. On the free plan here it is the first two. Paid plans remove the badge and add a custom domain, either one you already own or one registered for you.

The limit most people actually hit is the URL rather than any feature. A free subdomain is completely fine while you are testing an idea and starts to matter the moment the link goes on an application, so the useful question when comparing free tiers is how much work it is to move to your own domain later, not which has the longest feature list.

For plenty of roles, no, and it is fair to say so. If you are applying through a large company's process for a job where the work is not visual and not public, LinkedIn plus a resume is often enough and a personal site is a nice-to-have.

The difference bites where the work needs showing rather than listing. Anything visual, obviously. Writing of any kind, where a sample beats a description of your writing. Freelance and contract work, where a proposal with a link converts and one without it does not. Career changes, where your history argues for the job you are leaving. And senior roles, where the interesting content is judgement and tradeoffs, which is exactly what does not survive a bullet point.

The version that works is not choosing between them. LinkedIn is a directory entry that makes you findable and verifiable; a site is where the actual argument lives. Link them in both directions.

No, and you do not need to learn a design tool either. On DebutPage you describe what you want in plain language, so "dark mode with a teal accent" or "make my name bigger" is the whole interaction.

Coding is still the better answer in one case: if you are comfortable in HTML and CSS, static hosting from a repository gives you total control and costs nothing but your time. It is a poor answer otherwise, because free there quietly means a weekend.

Starting from your resume, about two minutes to a published page. Starting from a blank canvas in a general site builder, most people lose a weekend to it, and a meaningful share never finish at all.

The reason for the gap is not the software. A blank builder asks you to be a designer, a copywriter and an information architect before you have written a sentence, which is three jobs, and none of them is the one you were trying to do. Your resume already resolved most of that.

Budget a little more than the two minutes for the part software cannot do: deciding which two projects you actually want to be asked about, and putting whatever you most want to be hired for at the top even when it is not the most recent thing you did. That edit takes a minute and is most of the difference between a page that reads as generated and one that reads as yours.

Yes, on a paid plan. You can point a domain you already own at your site, or have one registered and configured for you inside the app if you would rather not touch DNS.

It is worth doing sooner than feels necessary. If your link is yourname.com pointed at whatever tool you currently like, the next migration costs you an afternoon and nobody else notices. If your link is your-tool.com/yourname, the next migration costs you every place that link is written down, which for anyone who had a read.cv profile is not a hypothetical.

Put work you did rather than work you were paid for, and be specific about what you decided. Coursework you took further than the assignment required, a small analysis of a public dataset, something you built because it annoyed you, volunteer or club work with a real deadline and a real audience: all of these show the same things a job would, which is framing a problem, choosing an approach and stating a conclusion you can defend.

What does not work is padding. Three things you can talk about in detail beat nine you listed, and a reader's impression is set by the weakest item you included rather than the strongest.

Be straightforward about the context. Labelling something as a course project or a personal experiment costs you nothing, and a reader who discovers the framing themselves will discount everything else on the page.

It will if you publish the first draft unchanged, and that is a real risk worth naming rather than talking around. Anything that generates a starting point from a template produces a recognisable house style, and readers who have seen a few of them notice.

The parts that make a page look like yours are the parts you control anyway: the ordering, the selection, and the sentences in your own voice. Restyling is a conversation rather than a template picker, so a page that reads as generic is usually a page nobody spent five minutes on.

If you want maximum control over the markup and the layout, hand-built and statically hosted is still the ceiling. The tradeoff is the one it has always been, which is your time against your control.

No. You can upload your resume, see the drafted page and restyle it without signing up, and you only make an account at the point of publishing.

This is deliberate. You should be able to see the result on your own resume before deciding whether it is worth an email address, and if it is not for you, you will know inside a couple of minutes without having handed anything over to find out.

Yes. Editing the content and restyling the page both work the same way after publishing as before, and the changes go live on your existing URL rather than a new one.

You can also take the page down. Unpublishing is one click and reversible, and deleting a site is available too, so the decision to publish is not one you have to be certain about in advance.

Yes, and there is nothing you need to configure. Every published site is a real HTML page on its own hostname, with a sitemap, a canonical URL and structured data describing you as a person, which is what a crawler needs to index it and show it properly.

Being indexed is not the same as ranking, and it would be dishonest to imply otherwise. A personal site competes for your own name and very little else, which is the point: it is the page you want someone to find when they look you up after reading your application, not a page you are trying to rank for a generic search.

Decide which half of read.cv you are replacing first, because the two halves have very different answers. If you want the page back, that is solvable, and starting from the resume that says nearly the same thing makes the rebuild much smaller than it feels.

If you want the community back, nothing will restore it, and any tool that promises otherwise is selling you something. That audience was made of the people who were there.

What a personal site does give you is the thing that survives platform decisions: an address you control, with content you can export, that does not stop existing because a company was acquired. That is a smaller promise than a network and it is one that is actually in your hands.