Publishing

Choose the export you actually need

In the saved article editor, open Export. For a standard finished article, the available actions are:

Save Markdown edits before exporting, or cancel those edits to use the last saved version. The application blocks export while Markdown changes are unsaved. If copying or downloading reports a failure, check the result and retry; do not treat a loading message as a completed file. Image download is shown only when an image exists. Refresh work can show additional patch-related actions; those are not needed for this standard article example.

Worked handoff: a HarborDesk rollout article

1. 1. Review the saved result

   Open the finished article from its existing Rankvia topic. Read the complete body and verify the proposed permissions workflow, product limitations, links and approved language/market. Confirm which claims are real before approving the article. Save your edits. Review is still necessary even if export is available.

2. 2. Transfer one body format

   Choose Copy HTML or Download HTML (.html) if the destination accepts HTML. Use the Markdown alternatives if that editor supports them. Start a CMS draft and import or paste into the appropriate mode. Keep a single body version rather than pasting both formats.

3. 3. Map fields and media separately

   Set the page title and proposed slug in the CMS. Copy SEO metadata separately, then place its available SEO title and description into the destination’s relevant fields. Upload the downloaded hero image if required, set useful alt text and replace the exported image reference with the CMS-hosted URL.

4. 4. Adapt and preview the draft

   Check heading hierarchy and avoid two main titles if the CMS already renders one. Review paragraphs, ordered lists, tables, emphasis and links in the actual theme. Confirm internal destinations and image display on mobile and desktop. Adjust CMS blocks, CSS, categories, author and publication date yourself.

5. 5. Publish in the destination

   Use the CMS’s own review, permissions and publish controls. Exporting from Rankvia does not grant this authorization or perform this step. Confirm the intended URL, publication status and public access before calling the work complete.

6. 6. Check and record the result

   Open the public page and inspect text, images, alt text, links and metadata. If the article editor offers the manual-publishing panel after approval, you can record the published URL and mark it published manually after checking the CMS. That records your action; it is not an independent automatic verification of the external page.

Illustrative body excerpt

Before assigning local appointment responsibilities, list who may change a booking, who handles exceptions and which records the central team needs. Confirm those boundaries against the current product documentation before rollout. A clear responsibility map is a planning aid, not evidence that a particular security control exists.

What happens to metadata and images

SEO metadata can include title, SEO title, meta description, slug, publishing language, market, a schema suggestion and image details where available. Optional values can be absent. A schema suggestion is not automatically installed markup or a promise of rich results; review it against the final visible page.

Markdown and HTML body exports can reference the available hero image URL and alt text. They do not bundle all image files or upload them to the destination. The image download is separate. Do not assume a referenced URL will be accessible forever or that a CMS imports remote media automatically.

The HTML conversion supports common article structures such as headings, paragraphs, lists, links, images and Markdown tables. It does not reproduce every Markdown extension, custom block, embed, theme style or CMS layout. The destination preview is the place to catch conversion and formatting differences.

Manual transfer and connected publishing are different

Connected WordPress and Shopify publishing use their supported destination, permission, readiness and review or opt-in automatic-publishing flows. Manual export does not create those connections or register another CMS integration. Keep any existing publication mapping and avoid publishing a duplicate article while testing a different route.

• WordPress publishing instructions
• Shopify publishing instructions
• Review generation and saved articles