For a SaaS site without supported automated publishing, treat Markdown publication as a controlled transfer: move the article into your established CMS or repository, configure page-level settings separately, preview it, then inspect the public page. Ranks provides Markdown and a copyable prompt for manual publishing on website technologies outside its supported automatic setup path.
What Manual Markdown Publishing Means
Manual publishing means a team member transfers supplied article content into the site’s normal CMS, repository, or editor, then checks the rendered result before it becomes public. Ranks currently supports automatic setup and publishing for TypeScript Next.js App Router sites. Other stacks can use its manual Markdown integration path.
Your destination platform determines the import method and its field names. Markdown is the content source, while the CMS or repository turns that source into a public page. Articles can be inspected and edited before publishing, and generated articles remain drafts for review when Autopilot is off, according to the Ranks product reference.
- Collect the Markdown article, associated image assets, and approved production domain.
- Choose the established destination: a CMS draft, repository content file, or internal publishing workflow.
- Keep the page unpublished until body content, page settings, and destinations have been checked.
Transfer Markdown Without Breaking Structure
Transfer content in document order. Set the article title as the page’s single visible H1, then recreate lower-level headings at their intended levels. Add paragraphs, ordered lists, unordered lists, quotations, and code blocks as distinct blocks rather than flattening them into plain text.
Convert links deliberately. The CommonMark specification defines a link as link text paired with a destination URI and documents inline and reference-style forms. In the destination editor, retain meaningful anchor text and confirm that each destination is unchanged unless you deliberately replace it with a production URL.
Handle every image as a separate asset. The CommonMark image tutorial documents image syntax and explains that alt text is available when an image cannot display or for visually impaired users. Upload the intended file through the normal site workflow and add useful alternative text describing its content or function.
Set Metadata, Internal Links, and the CTA
The article body and page settings are separate tasks. Set the slug, SEO title, meta description and canonical URL through your platform's supported fields or configuration. Treat the cover displayed on the page and the social-sharing image as separate settings, even if they use the same file. A visible cover does not establish that a sharing preview has an image. Verify the rendered page's social metadata, including an explicit og:image with the intended public image URL. The Open Graph protocol defines that property.
Do a final destination pass for internal links and the CTA. A link can look correct in a draft but still point to a staging domain, outdated route, or unsuitable relative path. Do not publish until every internal link and CTA uses a production absolute URL or your team’s intentional relative-URL convention.
Ranks describes its articles as containing relevant internal links and a product call to action. Its publishing controls let teams inspect and edit articles before publishing. Use that editorial control to replace placeholders and validate every destination against the production site.
Worked Example: Transfer a Supplied Markdown Article
This hypothetical transfer uses a team's policy of absolute production URLs; it is not a required CMS schema. The table maps the source snippets to their destination fields. Every example.com address is illustrative and must be replaced with your own public URL.
The accompanying page settings are slug soc-2-automation-tools-for-startups, SEO title 'Best SOC 2 Automation Tools for Startups', description 'Compare SOC 2 automation considerations for startup teams.' and canonical URL https://example.com/blog/soc-2-automation-tools-for-startups. Preserve the source H2 'What Startups Should Compare' beneath the title. Body headings and page metadata are separate fields.
Test the table's expected results in preview, then repeat them on the deployed page. If the body link still points to a staging site or the social image is absent from metadata, correct that field rather than retransferring the whole article.
| Supplied input | CMS or repository result | What to verify |
|---|---|---|
| # Best SOC 2 Automation Tools for Startups | Visible page H1 with identical text | One H1 appears |
[security questionnaire workflow](/security-questionnaires) | Link to https://example.com/security-questionnaires | Anchor and destination are correct |
[Start a free trial](/signup) | CTA to https://example.com/signup | CTA reaches signup |
| Cover alt text supplied with image | Alt text entered with uploaded cover | Cover appears with useful alternative text |
| Social image approved separately | Social-image setting uses https://example.com/images/soc-2-social.png (illustrative) | Rendered og:image names the intended public asset; inspect a sharing preview |
| Slug and metadata approved separately | Page settings use the listed illustrative values | Public URL and settings match the draft |
Preview, Publish, and Verify the Live Page
Preview on desktop and a narrow mobile viewport before publication. Check heading order, paragraph and list spacing, code readability, image placement, and CTA visibility. Correct the relevant source or editor block, then preview again.
Publish through your established CMS or deployment process. After deployment, open the final public URL in a normal browser session and confirm visible text, headings, links, cover, and CTA. Ranks’ publishing guidance distinguishes a generated draft from a live deployment and recommends checking the live URL, text, links, and cover after publication.
Record the final URL and observation time in your publishing record. This confirms current public availability and rendered-page correctness, not search indexing. For post-publication search exposure and visitor checks, use the Search Console and Vercel validation guide.
