Skip to content
Best Magazine Ever

Topic

Online Magazine Publishing

From finished issue to online edition: a screen-ready PDF, hosting and a viewer, embedding and distribution, search, privacy-aware statistics, private editions and an archive that lasts.

An online edition works when readers can find it, read it on a phone and still open it years later. Here are the steps in order; digital magazines compares the formats, and how to publish a magazine online walks through the launch of one issue.

Prepare a PDF for screens

Export a reader version alongside the press file:

  • No printer's marks or bleed, and images compressed for screens.
  • Working links: a clickable contents page, live URLs and email addresses, and "see page 34" references that still match if pages are dropped.
  • Real, tagged text: PDF/UA-1 requires content tagged in a logical reading order, alternative text on figures and a declared document language [1].
  • A descriptive title in the document properties, set to show in the viewer's title bar [2].
Diagram of a tagged PDF page: content tagged in reading order as 1 H1 headline, 2 P paragraph, 3 Figure with alt text, 4 P paragraph; the running head, a separator rule and the folio marked as artifacts; the document title and language set.
A reader PDF: text tagged in reading order, a text alternative on each figure, a title and a language.

The magazine publishing checklist and the accessibility checklist cover each step.

Choose hosting and a viewer

Link a PDF from your website, or use a platform that shows each issue in a browser viewer, often with embedding, an archive page and statistics. Test a real issue on the plan you would pay for:

CheckWhat to look for
Phone readingA scroll mode or text version, not just pinch-and-zoom
Next to your issueAds, other publishers' documents, provider branding
Reader dataHosting location; whether the provider signs a data processing agreement
EmbeddingEmbeds on your own pages, with your logo and colours
MediaVideo and galleries that play on phones and in the embed
StatisticsWhich numbers, and whether they need cookies
Access controlUnlisted links, passwords or per-recipient access
Moving outYour files back; issue addresses on your own domain

Embed issues on your own site

Embedding keeps readers on your domain. Give each issue its own page with the cover, a short introduction, the contents and the viewer. Name the magazine and issue in the frame's title attribute, which labels the frame for users [3], and link to the full-screen edition for small screens.

Diagram: newsletter, social posts, QR codes in print, partners and search all lead to one issue page on your own domain, which shows the cover, the contents and the viewer embedded from a platform that is easy to replace.
Every channel leads to the issue page on your own domain; the platform's viewer is only embedded there.

Distribute every issue

  • Newsletter on release day: the cover and two or three highlights, linking to the issue page.
  • Social posts that lead with one story, not "the new issue is out"; give contributors the cover and link to share.
  • QR codes in print that point to an address you can redirect, with a short URL beside them, tested at printed size.
  • Tagged links with utm_source, utm_medium and utm_campaign, as Google's Analytics Help advises [4].

More channels: how to get more readers for your digital magazine.

Make issues findable

Google can index PDF files [5], but a bare viewer page gives search engines little text. The issue page does the work: a unique, descriptive title and meta description [6], the contents and short summaries of the main stories. Schema.org's PublicationIssue type marks up a single issue, including its number [7]. If your print edition has an ISSN, the online version needs its own [8].

Put transcripts of video and audio on the issue page or link them from it; W3C counts better search indexing among the benefits of accessible media [9].

Measure readers without overreaching

Decide first which numbers you will act on: visits per issue, reading time per page, link clicks, referring channels. Tracking cookies for analytics need consent before they are set; cookies strictly necessary for a service the reader requested are exempt, says the EU's Your Europe portal [10]. To count readers who decline too, ask how a platform measures without cookies and have your data protection adviser check it.

Count media plays and clicks against the readers who reached that page, and drop what few use. Players that load straight away cost data even if nobody presses play: lazy-loading YouTube embeds saves around 500 KB on initial page load, says web.dev [11].

Protect private publications

Match the protection to the risk:

  • Unlisted link: anyone who has it can read and forward it.
  • Password: one shared secret for a group such as members or a board; change it when the group changes.
  • Per-recipient access with an expiry date: for confidential reports.
Diagram of three access levels with more protection from left to right: an unlisted link, which anyone who has it can read and forward; a password, one shared secret for a group; per-recipient access with an expiry date.
Match the protection to the risk: unlisted link, password or access per recipient.

robots.txt does not keep a page out of Google, which recommends noindex or password protection instead [12]. For PDFs, send noindex as an X-Robots-Tag HTTP header and do not block the URL in robots.txt, or the crawler never sees the rule [13].

Anything readers can view, they can screenshot.

Keep an archive that lasts

  • One permanent URL per issue, ideally on your own domain, and an archive page listing every issue, newest first.
  • Redirects when you move, possible only for addresses you control: permanent ones such as 301, kept as long as possible, generally at least a year [14].
  • A PDF/A copy: PDF/A keeps a document's static appearance and does not permit encryption, and PDF/A-1 to PDF/A-3 forbid audio and video [15]. Archive media files separately, with captions, transcripts and the page each belongs to.
  • Rights: check that contributor and image licences cover online publication and a permanent archive.

In this section

Sources

  1. PDF/UA-1, PDF Enhancement for Accessibility, Use of ISO 32000-1 - Library of Congress
  2. PDF18: Specifying the document title using the Title entry in the document information dictionary of a PDF document | WAI | W3C
  3. H64: Using the title attribute of the iframe element | WAI | W3C
  4. URL builders: Collect campaign data with custom URLs - Analytics Help
  5. File types indexable by Google - Google Search Central
  6. SEO Starter Guide: The Basics - Google Search Central
  7. PublicationIssue - Schema.org Type
  8. The ISSN for electronic media - ISSN International Centre
  9. User Experiences and Benefits to Organizations | Web Accessibility Initiative (WAI) | W3C
  10. Online privacy: How to use cookies on your website - Your Europe
  11. It's time to lazy-load offscreen iframes! | web.dev
  12. Robots.txt Introduction and Guide - Google Search Central
  13. Block Search Indexing with noindex - Google Search Central
  14. Site Moves and Migrations - Google Search Central
  15. PDF/A Family, PDF for Long-term Preservation - Library of Congress