Create
Exporting content
Download a generated post as HTML, Markdown or a ZIP bundle, or copy its HTML, Markdown or JSON-LD, and copy the changes from an optimization.
Everything Ranqo writes for you can leave Ranqo. A generated post exports as a file or to your clipboard, in the shape your site needs. To send a post straight to WordPress instead, see Publishing to WordPress.
Where to export from
- On a post: open it from the Blog library and use Download in the top bar. It holds every option below.
- From the Blog library: a card's menu has Download HTML and Download Markdown without opening the post.
Downloaded files are named after the post's title in lowercase, with hyphens in place of spaces and punctuation, for example how-to-choose-a-crm.html.
The options
| Option | What you get | Use it for |
|---|---|---|
| Complete HTML page | A standalone .html document | Hosting the post as-is, or previewing it exactly as generated |
| Markdown (.md) | The post in Markdown with a frontmatter block | Static-site generators and Markdown-based CMSs |
| Bundle (.zip) | The HTML page, the Markdown file and, when the post has schema, schema.json | Handing the whole post to a developer |
| Copy HTML | The post body as HTML, no page wrapper | Pasting into a CMS editor's HTML view |
| Copy Markdown | The post body in Markdown, no frontmatter | Pasting into a Markdown editor |
| Copy JSON-LD | The post's schema as formatted JSON | Adding structured data to the page head |
Complete HTML page
A full document with the title, a meta description (from the post's schema), the JSON-LD schema in a <script type="application/ld+json"> tag in the head, and basic styling. Charts are drawn as inline SVG, and stat callouts and pull-quotes as plain HTML. Every colour is written directly into the file, so it looks right opened on its own, with no stylesheet or connection to Ranqo.
Markdown
The file starts with a YAML frontmatter block holding title and date (the day the post was generated), plus description and schema (the full JSON-LD) when the post has them. The post body follows.
This mostly matters for the Rich format. A Standard post has at most one chart.
Bundle
A .zip, named after the title, holding the HTML page and the Markdown file, both also named after the title, and schema.json with the JSON-LD on its own when the post has schema.
Copy HTML
The body only, with charts and callouts drawn as HTML, and without the page head, so without the meta description and schema. Publishing to WordPress sends a body built with the same conversion. Add the schema separately with Copy JSON-LD.
Schema
Every post comes with JSON-LD: an Article, plus an FAQ page when the post has an FAQ. It is in the HTML page's head, the Markdown frontmatter and the bundle's schema.json, and Copy JSON-LD copies it. It is never inside the body, which is why Copy HTML and WordPress publishing do not carry it.
Optimization results
A Content Optimizer result is a set of changes to a page you already publish, so there is no file to download. Copy what you need from the result page:
- Copy on each change copies its After text.
- Copy JSON-LD on the Schema markup card copies the schema, ready for the page head.
- The Generated FAQ is shown in full for you to copy into the page.
Page audit PDFs and the dashboard's own exports are covered in Reports and exports.