Use case
You have written the thing. It is an HTML file, or a folder with an index.html and some assets, and it needs to reach one person without becoming a 40 MB attachment that their mail server rejects. Upload it, choose who can open it, and send the link.
The page renders as you built it, because it is your own HTML being served rather than a converted preview of it. Charts stay interactive. Fonts stay yours. And when the numbers change you replace the file, and the link you already sent keeps pointing at the current version.
This is the setting that matters, and it is worth getting right before you press send. A link is only as private as the mode you chose. A slug nobody could guess is still readable by anyone it gets forwarded to.
Named people only
Access is granted per person by email. Anyone else, including someone forwarded the link, gets a not-found, not a login wall that confirms the page exists.
Share a private link with named people →One shared secret
The reader enters a password and gets a short-lived pass for that site. No account, and you can send the password down a different channel from the link.
Password-protect a static site →You find out who opened it
The reader gives an email address and confirms a six-digit code before the report loads, and you keep the list. Right for a benchmark or a teaser; wrong for one named client, who should not have to identify themselves to read their own numbers.
Require an email to view a link →Anyone with the URL
Open to whoever holds the link, and indexable unless you also mark the site hidden from search. Right for a case study, wrong for a client's numbers.
Share a public link →A password is set after the site exists rather than during the upload, so the usual order is: upload the file, switch visibility to password, then share. Any of these can be changed later without the URL changing.
The reason to send a link rather than a PDF is what comes back. A reader selects a passage on the rendered page and leaves a note against that selection, so “this figure looks wrong” arrives attached to the figure instead of as an email that says “page 4, second chart, third bar”. The whole round, from inviting reviewers to resolving what they raise, is walked through in how to collect feedback on a report.
Each anchor stores the selected text plus a short run either side of it, which is what lets a comment survive an edit: upload a corrected version and the note finds its place again wherever the surrounding wording still matches. Threads resolve and reopen. Give one person commenter and another viewer if only one of them is meant to be marking it up, or turn commenting off entirely for a page that is simply being delivered.
Reading and commenting are free. Reviewers never need a paid plan, and there are no seats to buy for someone who will open one document once.
Upload the HTML file, or a ZIP containing an index.html plus its CSS, JS and images, and Pagegoat returns a link at pagegoat.com/sites/your-slug. Before you send it, set the visibility. Private restricts the page to people you name by email, so anyone else gets a not-found rather than a login prompt. Password protection gives you one shared secret you can put in a separate message from the link. Capture emails asks for an email address before the report loads, so you find out who actually opened it. Public means anyone holding the URL can read it, and search engines may index it unless you also mark the site hidden from search. The client opens the link in an ordinary browser: nothing to download, no account to create, no plugin, and the page renders exactly as you built it because it is your own HTML being served, not a converted preview of it.
Not for a public or password-protected page. They click the link, enter the password if there is one, and read it. Pagegoat issues a short-lived pass for that site so they are not asked again on every page load. An account is only required for a private site, because private means access is granted to specific people and there has to be an identity to grant it to. Reading and commenting are free in every case; the paid plan is what lets you publish, not what lets them read. That means you can invite as many reviewers as a piece of work needs without any of them being charged, and without buying seats for people who will look at one document once and never return.
Yes, and it attaches to the passage rather than floating beside the document. A reader selects text on the rendered page and leaves a note against that selection, the way commenting works in a shared document. The anchor stores the selected text plus a short run of characters either side, so when you upload a corrected version the comment can find its place again instead of collapsing to the top of the page. Threads can be resolved and reopened. You control who may do this per person: viewer can read only, commenter can read and comment, admin can also replace the file and change who has access. If you would rather collect no comments at all, commenting can be switched off for the site.
Only if you publish it publicly and leave it indexable. A private or password-protected site is never served to a crawler in the first place, and a public site can additionally be marked hidden from search, which makes Pagegoat serve a noindex instruction on that page so search engines are told not to list it. The important detail is that a public link is genuinely public: anyone who has the URL can open it, whether you sent it to them or it was forwarded. If the contents are confidential, the visibility setting is the control that matters, not the obscurity of the slug. Pick private or password before you send anything you would not want read by a stranger.
You replace the file and the link stays the same. Re-uploading writes a new version to the same slug, so the URL you already emailed keeps working and points at the current document. There is no v2 link to chase, and nobody is left reading last week's numbers because they bookmarked the first one. Existing comments re-anchor to their passages where the surrounding text still matches. Only the current version's bytes are stored, so revisions do not quietly consume your allowance. If a report is genuinely finished and you want it gone, deleting the site removes it and the link stops resolving.
Publishing starts at $2.99/month. Your reader needs nothing but a browser.
pagegoat.com/sites/your-report
See plans