Sharing & exporting.
A read-only public link for client review — no login, and revocable. Plus HTML, Markdown, plain text and print-to-PDF, each with an SEO Pack appendix. All of it free.
Two different jobs, both in the editor's action bar. A share link gives someone a read-only web page they can open without an account — the right way to get a client's sign-off. An export gives you a file. Both are free, and neither costs a credit.
The public share link
Open the ⋮ overflow menu in the action bar and choose Create public link. You get a URL like this:
https://user.scoutrival.com/share/Kq7fZ2xN9pLmA3vT8bWc
Send it to a client, paste it in Slack, embed it in Notion. What they see:
- The article, cleanly rendered in your brand's colours.
- No login prompt, no ScoutRival account, no sidebar, no editor, no Content Score.
- A small ScoutRival footer at the bottom.
They cannot edit it. There's nothing to click. It's a document.
The menu tracks the link once it exists — the same overflow menu then offers Copy public link and Revoke public link, and the share dialog shows how many times it's been viewed. Asking for a second link on the same article just hands you the existing one back rather than minting a duplicate.
The token is the permission
There's no password on a share link and no expiry date. That random string in the URL is the access control — anyone holding it can read the article, and anyone they forward it to can read it too. It's the same model as an unlisted video.
The token is 24 characters of cryptographic randomness, so it can't be guessed. But it can be forwarded.
The share page is a public web page. It carries no login wall, and it's deliberately embeddable in other sites. Don't share a link to anything you wouldn't be comfortable seeing on the open internet — if a client forwards it on, there is nothing stopping the next person reading it. Revoke the link when the review is done.
Revoking a link
⋮ → Revoke public link. The token is dead: any new request for that URL returns a “not available” page.
The share page is cached at the edge for five minutes so it loads fast. That cache doesn't know you revoked anything. So for up to five minutes after a revoke, someone who already has the URL — or a network that already fetched it — may still be served the cached copy. The app's confirmation dialog says “immediately”; the honest answer is within five minutes. Revoke a link before it becomes urgent, not after.
Archiving revokes links for you
Archiving an article (⋮ → Delete article) is a soft delete — the article stays in your archive, and it isn't gone forever. But it revokes every active share link on that article automatically, so nothing you've archived stays readable on the public web.
The same five-minute cache caveat applies.
The four export formats
Export in the action bar. All four are free, unlimited, and always the current state of the article.
| Format | You get | Use it for |
|---|---|---|
| HTML | A standalone .html file — the article, your brand's CSS, and the JSON-LD schema, in one document that works offline. | Handing the whole thing to a developer. |
| Markdown | A .md file with YAML frontmatter — title, slug, description, date, author — then the body. | Ghost, Hugo, Astro, Jekyll, Notion, or pasting into WordPress's block editor. |
| Text | A plain .txt file with a brand letterhead at the top. | Email, a doc, anywhere formatting gets in the way. |
| Opens a print-ready page and triggers your browser's own print dialog. Choose Save as PDF. | Client deliverables. |
The frontmatter on the Markdown export looks like this — standard YAML, so any static-site generator will read it:
--- title: "7 Warning Signs Your Boiler Is About to Fail" slug: "boiler-warning-signs" description: "The noises, smells and bills that mean a callout is coming." author: "Northgate Heating" --- # the article body follows
Choosing PDF opens a new tab and fires the print dialog after a moment. Pick Save as PDF as the destination. It's the same pipeline Notion and Linear use — the output is clean A4 with your letterhead, and it means there's no server-side renderer to go wrong.
The SEO Pack appendix
The Markdown, Text, HTML and PDF exports don't stop at the article. They append an SEO Pack — everything you need to actually publish the piece somewhere else:
- Meta title and meta description
- Every FAQ pair
- Primary and secondary keywords
- Every external citation in the body, with its URL
- The raw FAQ / Article JSON-LD, ready to paste into a page head
This matters because publishing to WordPress sends only the title and the HTML. If you want the schema and the meta on your live page, an export is how you carry them across.